Guest WiFi and Data Collection — Legal, Useful, and Underused

Every guest who sits down in your restaurant represents a potential long-term customer relationship. Most restaurants let them leave without capturing anything — not a name, not an email, not even a preference. Then they wonder why repeat visits are unpredictable and marketing feels like shouting into a void.

Guest WiFi is one of the cleanest, most underused data collection tools in hospitality. Done right, it is legal under GDPR, valuable to guests, and valuable to you.

Why guest WiFi works for data collection

The value exchange is clear. Guests want WiFi. You want their contact information. A captive portal — the page that appears before WiFi access is granted — is the mechanism that makes this exchange happen. Guests enter their email, accept your terms, and get online. You get a contact record. The difference from asking guests to sign up for a newsletter: WiFi access is a basic expectation, so guests are already going to ask for the password. The captive portal intercepts that request and converts it into a data capture event.

GDPR compliance: what you must do

In Germany and across the EU, collecting personal data requires explicit consent and a clear privacy statement. The captive portal must state what data you are collecting, explain how it will be used, include a marketing consent checkbox that is unchecked by default, link to your privacy policy, and give the guest the option to connect without providing marketing consent — they still get WiFi, just without the marketing opt-in. WiFi access cannot be conditional on marketing consent under GDPR. Plattr's CRM tags contacts by consent status.

What to do with the data

A list of email addresses is only valuable if you use it. Within an hour of WiFi connection, send an automated welcome email: "Thanks for visiting today. Here is our menu for next time. We would love to see you again." Include a link to join your loyalty programme.

After 14 days, if the guest has not returned, send a nudge — a seasonal dish, a new menu item. After 60 days without a return, send a win-back message. This is the same logic that works for loyalty programme members who stop visiting.

Combining WiFi data with other channels

The most useful thing about CRM-connected WiFi data is how it combines with other contact sources. A guest might first appear in your Plattr account as a booking guest from a Guide listing reservation, then return and connect to WiFi. Plattr matches on email and merges the records — you now have a unified profile showing that this person books and visits, with timestamps for both. That unified profile is where Insights Hub analytics get interesting.

Setting up your captive portal

Most modern WiFi routers support captive portal configuration out of the box. The setup typically takes 30-60 minutes and involves three things: configuring the router to redirect new connections to your portal page, designing the portal page with your branding and consent fields, and connecting the form submission to your CRM. You do not need a developer. Services like Linkyfi, Beambox, and similar hospitality WiFi providers handle the technical layer. Once connected to Plattr via email sync, contacts flow in automatically tagged with source: WiFi.

For smaller restaurants just starting out, a simpler version works fine: a password-protected network where guests get the password by providing their email at the counter. It is lower-friction technically but relies on staff consistency. The automated captive portal scales better.

Segmenting WiFi guests differently

WiFi guests are a specific segment worth treating differently from booking guests or loyalty members. They came in without a reservation. They may be new to the neighbourhood. They had an experience you know nothing about yet. Your first email to a WiFi guest should reflect that uncertainty — it is a first impression, not a follow-up.

Compare this to a booking guest, where you already know their name, party size, and whether they indicated a special occasion. The data you have shapes the message. WiFi-sourced contacts respond better to messages that acknowledge the spontaneous nature of their visit and invite them back with something specific: a dish you think they might like, or your current seasonal menu.

WiFi data and your loyalty programme

The highest-value action after capturing a WiFi contact is converting them into a loyalty member. Someone who is already in your restaurant, connected to your WiFi, is about as engaged as they will ever be remotely. Your welcome email should include a clear call to action: join your Bonus Card programme. Link directly to the sign-up QR from your QR code setup.

WiFi guests who become loyalty members have materially better return rates. The WiFi capture is step one. The loyalty enrolment is step two. The repeat visit is the result.

Analysing your WiFi contact quality

After three months, pull your WiFi-sourced contacts in Plattr and look at their return behaviour. What percentage came back within 30 days? What is the average visit frequency? How does their lifetime value compare to booking-sourced guests? These comparisons are visible in your Insights Hub by contact source segment. The data usually shows that WiFi guests who also join loyalty return at a rate similar to booking guests. WiFi guests who do not join loyalty return at a much lower rate — which tells you exactly where to focus your onboarding flow.

The long-term payoff

A restaurant with 30 covers and moderate turnover can realistically capture 20-40 new guest email addresses per week through WiFi. Over a year, that is 1,000-2,000 contacts who have all visited your restaurant and consented to marketing. Each guest on that list who returns once brings you roughly 40-100 EUR in additional revenue. A 10% reactivation rate from a 1,000-person list is 100 covers — potentially 5,000-10,000 EUR from three automated emails. Start with the free Plattr account and build your contact database. Whether contacts come via WiFi, loyalty sign-up, or QR code, they all flow into the same CRM.