How to leverage SMS marketing restaurants to increase return visits

Welcome to the Purple Intelligence Briefing. I'm your host, and today we're getting into something that every restaurant operator with more than one site should be thinking about right now: SMS marketing, and specifically how to use your guest WiFi infrastructure to build the data pipeline that makes it work. Let's start with the context. Restaurants are operating in a market where third-party delivery platforms own the guest relationship, social media reach is declining without paid spend, and email open rates in hospitality sit around 20%. That's one in five people actually seeing your message. Meanwhile, SMS messages achieve a 98% open rate, with most read within three minutes of delivery. That gap is not marginal. It changes the economics of re-engagement entirely. But here's the thing most operators miss. SMS marketing is only as good as the data feeding it. And the single best source of verified, consented guest data in a restaurant environment is your guest WiFi network. When a diner connects to your WiFi through a captive portal, they provide their name, email address, and phone number. They confirm marketing consent. That data is first-party, meaning you own it. It doesn't disappear when a platform changes its algorithm or its terms of service. Purple's Engage plan captures that data at login and automates campaigns directly from it. Across 80,000 live venues and 440 million logins in 2024, we've seen consistently that venues using WiFi-captured phone data for SMS outperform those relying on manually collected lists by a significant margin. The data is cleaner, the consent is explicit, and the guest profile is enriched with behavioural signals like visit frequency and dwell time. Now let's get into the technical architecture, because this is where the implementation decisions matter. The data capture layer sits at the captive portal. When a guest connects to your WiFi, the portal presents a branded login page. The guest authenticates, typically via email or phone number, and in doing so provides explicit consent to receive marketing communications. Under GDPR in the UK and EU, this consent must be freely given, specific, informed, and unambiguous. That means you cannot make WiFi access conditional on marketing opt-in. Purple's portal architecture separates network access from marketing consent, presenting them as distinct choices. This is the correct implementation. Any vendor that bundles them together is creating compliance exposure for you. Once captured, the phone number and consent record are stored in the guest profile within Purple's platform. That profile is enriched over time with visit data: how often the guest comes in, which site they visit, how long they stay. This behavioural layer is what enables segmentation. You're not sending the same message to a first-time visitor and a guest who's been in twelve times. Those are fundamentally different relationships, and your SMS strategy should reflect that. The segmentation framework we recommend has four tiers. First, new guests: people who've visited once in the last 30 days. Second, returning guests: two to four visits in 90 days. Third, regulars: five or more visits in 90 days. Fourth, lapsed guests: no visit in 60 days or more. Each tier gets a different message, a different offer, and a different send cadence. For new guests, the goal is a second visit. A welcome message sent 24 to 48 hours after their first visit, with a modest incentive, drives return rates. Pizza Express, for example, uses post-visit automation to send a personalised thank-you with a loyalty reward link. The timing matters: send too soon and it feels intrusive, send too late and the visit memory has faded. For returning guests, the goal is habit formation. Messages at this stage should reinforce the relationship rather than rely on discounts. Highlight new menu items, invite them to an event, acknowledge their loyalty. Stonegate Pubs uses visit-frequency data from WiFi sessions to trigger milestone messages. A simple acknowledgement that a guest has been in ten times, with no discount attached, generates measurable uplift in return visits. For lapsed guests, the goal is reactivation. A win-back message sent at the 60-day mark, with a clear, time-limited offer, is the standard playbook. The offer needs to be compelling enough to overcome inertia, but not so generous that you're training guests to wait for discounts. A free starter or a percentage off the next visit, valid for 14 days, is a reasonable benchmark. Now let me walk through a real implementation scenario. A 12-site casual dining chain deploys Purple on Cisco Meraki hardware across all sites. The Captive Portal is configured with a phone-number login option alongside email. Within 90 days, they've built a consented SMS list of 18,000 contacts across the estate. They configure four automated journeys: a welcome sequence for new guests, a loyalty milestone trigger at five visits, a slow-shift promo that fires on Tuesday and Wednesday afternoons to their returning guest segment, and a 60-day win-back for lapsed contacts. The slow-shift campaign alone, targeting 3,200 contacts with a same-day offer, drives an average of 140 additional covers per week across the estate. At an average spend of 22 pounds per cover, that's over 3,000 pounds in incremental weekly revenue from a single automated campaign. The second scenario worth discussing is a quick-service restaurant chain. QSR operators face a different challenge: high transaction volume, low dwell time, and guests who may not connect to WiFi at all. In this environment, the WiFi data capture rate is lower, but the guests who do connect are disproportionately your regulars. A QSR chain with 40 sites, running Purple on HPE Aruba hardware, captures phone numbers from roughly 15% of daily covers. That sounds modest, but at 800 covers per site per day, it's 120 contacts per site per day. Over 90 days, that's a list of over 400,000 consented contacts. The economics of SMS at that scale are significant. Let me address the compliance questions, because they come up in every client conversation. Under GDPR, you need a lawful basis for processing personal data. For SMS marketing, that basis is consent. The consent must be granular: a guest consenting to WiFi access is not automatically consenting to SMS marketing. Purple's portal architecture handles this correctly by presenting separate consent checkboxes for network access and marketing communications. The consent record, including timestamp and the specific wording presented, is stored against the guest profile. That audit trail is your defence in a regulatory inquiry. Under the Privacy and Electronic Communications Regulations, or PECR, in the UK, you also need prior consent for direct marketing by electronic means, which includes SMS. The rules align closely with GDPR consent requirements, but PECR applies even where GDPR's legitimate interests basis might otherwise apply. In practice, this means explicit opt-in is non-negotiable for SMS. Do not rely on soft opt-in for text messages. Now for the implementation pitfalls. The most common one is list decay. A phone number captured 18 months ago may belong to someone who's changed their number, moved away, or simply lost interest. Sending to a stale list drives up unsubscribe rates and damages your sender reputation with carriers. Scrub your list quarterly. Remove contacts who haven't opened or responded in six months. A smaller, engaged list outperforms a large, disengaged one every time. The second pitfall is frequency. Two to four messages per month is the ceiling for most restaurant audiences. Above that, unsubscribe rates climb sharply. The exception is highly segmented, highly relevant messages: a reservation reminder, a birthday offer, a response to a specific behaviour. Relevance earns frequency tolerance. Generic broadcast messages do not. The third pitfall is timing. Restaurant SMS campaigns perform best when sent at decision-making moments: Tuesday and Wednesday mornings for midweek dinner plans, Friday mornings for weekend bookings, and 30 to 60 minutes after a visit for feedback requests. Avoid sending after 9pm or before 9am. Carriers and regulators both frown on it, and your guests certainly do. Now, the rapid-fire questions I get most often in client briefings. Can I use SMS for reservation reminders without marketing consent? Yes, transactional messages, including booking confirmations and reminders, fall outside the marketing consent requirement. You need a lawful basis for processing the data, but not explicit marketing consent for the message itself. How do I handle opt-outs? Every SMS must include a clear opt-out mechanism, typically a reply keyword like STOP. Purple's platform handles unsubscribe processing automatically and updates the consent record in the guest profile. Do not send to contacts who have opted out. The fines for doing so are substantial. What's the right SMS platform to integrate with Purple? Purple's Engage plan integrates with major SMS providers and CRM platforms via webhook and native connectors. The specific platform matters less than the integration architecture: you want bidirectional sync so that opt-outs, delivery failures, and engagement data flow back into the guest profile and inform future segmentation. To summarise the key points from today's briefing. Guest WiFi is the most reliable source of verified, consented phone data in a restaurant environment. Segment your SMS list by visit behaviour, not just demographics. Automate the four core journeys: welcome, loyalty milestone, slow-shift promo, and win-back. Keep frequency at two to four messages per month unless the message is highly relevant. Ensure your captive portal separates network access consent from marketing consent. Scrub your list quarterly to maintain deliverability. And measure return visit rate, not just open rate, as your primary success metric. If you want to see how Purple's Engage plan maps to your specific estate, the next step is a technical scoping call with one of our solutions architects. We'll review your current hardware, your CRM setup, and your existing data capture workflow, and give you a clear picture of what's achievable in the first 90 days. Thanks for listening. I'll see you in the next briefing.