Restaurant email marketing examples that earn return visits
Use this guide to choose which restaurant emails to automate first, set the trigger and measure for each, and capture valid GDPR consent at guest WiFi sign-in.
Part of the guide topicVenue email campaigns: what to send and when
Video overview
{{asset:header_image.png}}
Restaurant email marketing examples are proven campaign patterns that a restaurant sends to diners who consented under GDPR. The common ones are welcome, win-back, birthday and quiet-night emails, and each is built to earn another visit. With Purple WiFi, that consent is captured at guest WiFi sign-in and flows into Purple Engage. Branded login pages deliver opt-in rates around 50% higher than other channels, according to Purple's own data.
What counts as a restaurant email marketing example?
A restaurant email marketing example is a repeatable pattern, not a one-off design. Each one has three parts: a trigger, a message and a measure.
- The trigger decides when the email sends.
- The message decides what the diner sees.
- The measure shows whether the email earned a visit.
The measure separates useful restaurant email ideas from pretty ones. An open rate only tells you an inbox loaded an image. A return visit tells you a diner came back and spent money.
Judge every example on four outcomes:
- Repeat visits: how many recipients come back within a set window.
- Opt-in rate: the share of diners who agree to hear from you at all.
- Revenue per send: spend linked to an email, divided by emails delivered.
- Lifetime value: what a diner spends with you across every visit.
Restaurant newsletter examples fit this definition, but they are the weakest form. A newsletter goes to everyone on one date. A triggered email goes to one diner at the moment their behaviour makes it relevant.
{"tone":"note","title":"Scope of this guide","text":"This guide covers email to diners who opted in at your venue, mainly under UK and EU GDPR. It is not legal advice, so check your consent wording with your data protection lead."}
How do restaurant emails turn a WiFi login into a return visit?
The mechanism runs in a loop. A diner joins your guest WiFi, agrees to marketing and starts a profile. Every later login adds a visit to that profile. Rules watch those visits and send the right email at the right moment. The next login shows whether the email worked.
{"kind":"flow","direction":"lr","caption":"How a guest WiFi login becomes a return visit","alt":"Flow from a diner joining guest WiFi, through recorded consent, a visit profile and a triggered email, to a measured return visit that feeds back into the profile.","nodes":[{"id":"a","label":"Diner joins guest WiFi","sub":"Branded login page asks for email and a separate marketing opt-in","tone":"brand"},{"id":"b","label":"Consent recorded","sub":"Unticked opt-in stored with date, venue and wording (GDPR Art. 7)","tone":"neutral"},{"id":"c","label":"Visit profile grows","sub":"Each later login adds a visit date and venue","tone":"neutral"},{"id":"d","label":"Trigger matches","sub":"First visit, lapsed window or birthday month","tone":"brand"},{"id":"e","label":"Email sends","sub":"Welcome, nudge, win-back or birthday invitation","tone":"brand"},{"id":"f","label":"Return visit measured","sub":"The next WiFi login shows the diner came back","tone":"success"}],"edges":[{"from":"a","to":"b","label":"opts in","style":"solid"},{"from":"b","to":"c","label":"logs in again","style":"solid"},{"from":"c","to":"d","label":"rule met","style":"solid"},{"from":"d","to":"e","label":"automation","style":"solid"},{"from":"e","to":"f","label":"diner returns","style":"solid"},{"from":"f","to":"c","label":"visit added","style":"dashed"}]}
Consent comes first
GDPR Article 4(11) defines consent as freely given, specific, informed and unambiguous. Article 7 then requires you to show that each person consented.
In practice, valid consent needs three things:
- an unticked box
- plain wording
- a stored record of what the diner agreed to
A branded login page handles all three at the moment of sign-in.
Visits become data
Most email platforms know a diner only through their inbox. A WiFi login adds what the inbox cannot see: which venue, which day and how often. That is first-party data, collected by you, from your own diners, with their agreement. It turns a generic send into a visit-based trigger.
Triggers replace the calendar
A calendar campaign asks, "What should we send on Thursday?" A trigger asks, "Who just did something that makes an email relevant?"
- A first visit triggers a welcome.
- A 60-day gap without a login triggers a win-back.
- A birthday month triggers an invitation.
Each rule runs on its own once you set it.
The list builds itself
This is where the model differs from Mailchimp, Klaviyo or HubSpot. Those platforms send campaigns, but you have to bring the list. With Purple Engage, every consenting WiFi sign-in adds a diner to your list. Your list grows with your covers, not with your sign-up forms.
Which restaurant email terms do people confuse?
A handful of term pairs cause most planning mistakes. Each one changes what you send, who receives it and how you judge the result.
{"caption":"Restaurant email terms that get confused","asOf":"2026-06-10","columns":[{"key":"term","label":"Term"},{"key":"means","label":"What it means"},{"key":"not","label":"What it is not"},{"key":"why","label":"Why it matters for return visits"}],"rows":[["Newsletter vs triggered email vs campaign","Newsletter: whole list, set date. Triggered email: one diner, behaviour-based. Campaign: any planned send","Interchangeable labels","Triggered emails reach a diner when a visit is most likely"],["Explicit consent vs soft opt-in vs legitimate interest","Explicit consent: clear GDPR opt-in. Soft opt-in: narrow PECR exception for details taken during a sale. Legitimate interest: a GDPR basis that cannot replace PECR consent for email","Three routes to the same permission","Explicit consent is the safe basis for WiFi sign-ups"],["Open rate vs click rate vs return-visit rate","Opens count loaded images. Clicks count taps on a link. Return-visit rate counts recipients who come back","Equal measures of success","Only return visits show the email earned a visit"],["First-party vs third-party data","First-party: collected by you from your own diners. Third-party: bought or rented from someone else","A size comparison","First-party data carries consent you can prove"],["List vs segment","A list is everyone who opted in. A segment is a subset by visits, venue or timing","The same audience","Segments let you send fewer, more relevant emails"],["Unsubscribe vs suppression","Unsubscribe: the diner withdraws consent. Suppression: the record that blocks future sends","One step","Without suppression, a re-imported contact can be emailed again"]],"footnote":"Consent definitions: GDPR Articles 4(11) and 7. Soft opt-in: UK PECR regulation 22.","download":{"filename":"restaurant-email-terms.csv"}}
The consent row matters most for venues that collect email at WiFi sign-in. The section on mistakes below explains why the soft opt-in rarely applies.
Where do you see these restaurant email examples in practice?
Seven examples cover most of what a restaurant needs. Build them in roughly this order, because each one depends on the list the previous one grew.
| Example | Trigger | What it offers | Measure |
|---|---|---|---|
| Welcome | First WiFi login with opt-in | A reason to return soon | Second visits |
| Second-visit nudge | One visit, no return after two weeks | A different occasion to try | Second visits |
| Win-back | No login for 60 days | Something new, before any discount | Lapsed diners who return |
| Birthday | Birthday month, if collected | A booking prompt for a group | Group bookings |
| Quiet-night filler | A slow service you choose | A reason to visit that day | Covers on that day |
| Menu or event launch | New menu, chef night or screening | First look for regulars | Bookings in launch week |
| Newsletter | Monthly date | One story, one date, one link | Clicks to booking |
The windows above are illustrations. Set your own from your venue's visit rhythm.
Welcome email
The welcome email is the send most restaurants never automate. It goes out after a diner's first login, while the visit is fresh. Thank them by venue name and show them one thing they missed. Give them a reason to come back soon, then measure the email on second visits, not opens.
Second-visit nudge
Many diners drift away between a first and second visit. A nudge reaches someone who visited once and has not returned. Point them to a different occasion. Suggest weekday lunch if they came for Saturday dinner, or brunch if they came for drinks.
Win-back for lapsed diners
A win-back targets diners whose logins have stopped. Match the window to your trade, because a neighbourhood café and a special-occasion restaurant lapse at different rates. Lead with something new, such as a menu change, before you reach for a discount.
Birthday emails
Birthdays work because they bring groups, not single diners. Send early in the birthday month with a booking link, so the diner plans the occasion around you. Collect the date only if you will use it. GDPR Article 5(1)(c) requires data minimisation.
Quiet-night fillers
Pick your slowest service and send to regulars of the venue with spare capacity. Tie the offer to that day only. That way it fills tables without discounting your busy nights.
Menu and event launches
Launches give regulars a reason to feel first. Send to your most frequent diners before the general announcement. Chef nights, seasonal menus and live sport screenings all fit this pattern.
The monthly newsletter
Most restaurant newsletter examples fail because they try to say everything. Keep yours to one story, one date and one link. Use it for news that suits everyone, and let the triggered emails do the selling. If you run pubs, pub email newsletter ideas covers formats built around quizzes, sport and seasonal events.
What this looks like in a real deployment
Picture a restaurant group with 20 sites on Purple Engage. Each venue runs its own branded login page, so every site grows its own list. The welcome, nudge and win-back emails run as automations across the estate, with the venue name and menu swapped per site. Head office compares which venues earn second visits and which lose diners after one. Local managers write the quiet-night and launch emails for their own trade.
Where do restaurant email campaigns go wrong?
Most failures come from five places: consent, measurement, discounting, coverage and frequency. You can fix each one before your first send.
Bundled or pre-ticked consent
GDPR Recital 32 is clear that a pre-ticked box is not consent. Marketing consent bundled into the WiFi terms fails the "specific" test in Article 4(11). Keep the marketing opt-in separate, unticked and in plain words. Store the wording that applied when each diner signed up.
{"tone":"warning","title":"Do not rely on the soft opt-in","text":"UK PECR regulation 22 allows the soft opt-in only for details collected during a sale or negotiations for a sale. A free WiFi sign-in is unlikely to meet that test, so take explicit consent at the login page."}
You can read the full text of PECR regulation 22 on legislation.gov.uk. If you also email diners in the US, the CAN-SPAM Act sets separate rules on sender identity and opt-out. Treat it as its own checklist, not a substitute for GDPR.
Measuring opens instead of visits
Apple's Mail Privacy Protection preloads email images, which inflates open rates. An inflated open rate can hide an email that earns nothing. Judge restaurant emails on return visits and revenue per send instead.
Discounting diners who would come anyway
A blanket discount to your most loyal regulars gives away margin on visits you already had. Save offers for lapsed and first-time diners. Give regulars recognition instead, such as early booking, a chef's table or a first look.
Forgetting who your WiFi does not see
Not every diner joins your WiFi, and some tables share one phone. Your list therefore over-represents diners who log in. Treat WiFi visit data as a strong signal, not a full headcount. Compare it with bookings and till data before you set targets.
Sending too often
Frequency fatigue shows up as unsubscribes. Let triggers decide most sends, so each diner gets emails tied to their own visits rather than a weekly blast.
How does Purple Engage fit restaurant email marketing?
Purple Engage runs these examples on WiFi visit data. The stack has six layers, and each one feeds the next.
{"kind":"layers","direction":"tb","caption":"The layers behind a visit-based restaurant email","alt":"Six stacked layers from the guest WiFi login page at the top, through consent and profiles, segments, automations and the email channel, to reporting on return visits.","nodes":[{"id":"s1","label":"Guest WiFi login page","sub":"Branded sign-in on your existing access points","tone":"brand"},{"id":"s2","label":"Consent and profile","sub":"First-party data stored with the opt-in wording that applied","tone":"neutral"},{"id":"s3","label":"Segments","sub":"First-timers, regulars and lapsed diners, by venue","tone":"neutral"},{"id":"s4","label":"Automations","sub":"Visit-based triggers in Purple Engage","tone":"brand"},{"id":"s5","label":"Email channel","sub":"Templates, sends and unsubscribes","tone":"neutral"},{"id":"s6","label":"Reporting","sub":"Return visits measured from later WiFi logins","tone":"success"}],"edges":[{"from":"s1","to":"s2","label":"captures","style":"solid"},{"from":"s2","to":"s3","label":"groups","style":"solid"},{"from":"s3","to":"s4","label":"targets","style":"solid"},{"from":"s4","to":"s5","label":"sends","style":"solid"},{"from":"s5","to":"s6","label":"measures","style":"solid"}]}
Purple is hardware-agnostic, so the login page runs as a cloud overlay on the access points you already own. Supported hardware includes Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet. There is no rip and replace.
{"items":[{"value":"80,000+","label":"live venues","note":"Purple data"},{"value":"90","label":"countries","note":"Purple data"},{"value":"500 million","label":"logins a year","note":"Purple data"},{"value":"Around 50%","label":"higher opt-in on branded login pages than other channels","note":"Purple data"}]}
Purple WiFi runs at Harrods, PizzaExpress and McDonald's, and Purple is ISO 27001 certified and GDPR compliant. See how the email channel in Purple Engage handles templates and automations. The WiFi marketing guide covers the login page side in more depth.
The concept matters most at the second visit. A restaurant that automates only the welcome and the win-back already covers the two moments when diners decide whether to return. For the full plan of what to send and when, read venue email campaigns: what to send and when.
Frequently asked questions
How much does restaurant email marketing with Purple Engage cost?
Purple Engage is priced on credits, one per email. A single venue can start on the free plan, listed at 500 credits a month with no card, and groups with two or more venues get a price from Purple's team. Purple Engage covers the campaigns and automations in this guide. Because the list builds itself from consenting guest WiFi logins, you do not pay to acquire contacts. Ask Purple to price against your estate and your current WiFi set-up.
Does Purple Engage work with the WiFi hardware we already have?
Yes. Purple WiFi runs the branded login page as a cloud overlay on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme and Fortinet, and each sign-in flows into Purple Engage. You keep your access points, and your network team keeps control. The branded login page and consent capture sit on top, so marketing can start without a hardware project.
Can we bring our existing email list into Purple Engage?
You can bring contacts across, as long as each one comes with consent you can prove. GDPR Article 7 puts the burden of proof on you. Bring the opt-in date and wording with every contact, and do not market to contacts that lack them. Purple integrates with CRM and marketing platforms, so you do not need a hard cutover.
Is collecting emails at WiFi login GDPR compliant?
Yes, when consent is separate, unticked, specific and recorded. GDPR Article 4(11) sets the standard for valid consent, and Article 7 requires you to prove it. Purple is GDPR compliant and ISO 27001 certified, and its login pages use conscious-choice opt-ins. You still own your privacy notice, so review the wording with your data protection lead.
How is Purple Engage different from Mailchimp or Klaviyo?
With Purple WiFi connected, Purple Engage builds the list from guest WiFi sign-ins, while Mailchimp and Klaviyo send to a list you already have. Every consenting guest WiFi login adds a diner, and every later login adds a visit. You can then trigger emails from real visits. You also measure success by return visits, not only by opens or clicks.
How much effort does the first automated email take?
The first automation needs a live branded login page and one well-written email. Once the login page captures consent, the welcome email is a template plus a first-visit trigger. Most of the work is the writing: a clear reason to return, the venue name and one link. Build the win-back next, then add the rest.
How often should a restaurant send marketing email?
Let triggers set most of your frequency. Each diner should receive emails tied to their own visits, plus one monthly newsletter at most. If unsubscribes rise after a send, cut the volume to that segment rather than to the whole list. Fewer, relevant emails protect the consent you worked to earn.