How to leverage marketing SMS messages to increase return visits

Welcome to the Purple technical briefing series. Today we're covering something that every venue operator should have sorted by now, but most haven't: how to use marketing SMS messages to drive measurable return visits. I'm talking about the full picture - data capture, consent architecture, campaign automation, and the metrics that actually matter to your board. Let's get into it. [short pause] First, the context. Your venue already has a WiFi network. Every day, guests connect to it. Most operators treat that connection event as a cost - bandwidth consumed, nothing gained. That's a missed opportunity worth talking about seriously. When a guest connects to your Guest WiFi through a captive portal, you have a brief, high-intent moment. They're physically present. They want access. And if you design the login flow correctly, they'll willingly share a verified phone number and tick an SMS opt-in box. That's not a lead. That's a first-party, consent-documented contact - the kind that GDPR actually likes, and that your CRM team has been asking for. Purple Engage captures that data at the point of connection, across 80,000 venues worldwide. The platform has processed 440 million logins in 2024 alone. That's the scale we're operating at. [short pause] Now let's talk about why SMS specifically. The numbers are stark. SMS carries a 98% open rate. Email sits at around 20%. SMS response rates average 45%, compared to roughly 6% for email. And 90% of SMS messages are read within three minutes of delivery. If you need to move someone from consideration to action - a flash offer, a re-engagement nudge, a post-visit thank you with a return incentive - there is no faster channel. The ROI case is equally clear. Conservative estimates put SMS marketing returns between 21 and 41 pounds for every pound spent. In hospitality and retail, that climbs higher during peak periods. Avanti West Coast, using Purple's Engage platform, achieved a 463% ROI by promoting upsells through the WiFi journey alone. That's not a hypothetical. That's a named customer with a documented outcome. [short pause] So let's get into the architecture. How does this actually work end to end? Stage one is the captive portal. When a guest connects to your WiFi - whether you're running Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, or any of the other hardware Purple integrates with - they hit a branded splash page. That page collects their name, email address, and phone number. Critically, it presents a clear, granular SMS opt-in checkbox. Not buried in terms and conditions. Explicit. Separate. Time-stamped. That consent record is stored and auditable. Stage two is the data pipeline. Purple Engage syncs that verified contact data to your CRM - whether that's Salesforce, HubSpot, or a loyalty platform - via one of over 400 available connectors. The phone number arrives with consent metadata attached. Your marketing team doesn't need to chase data hygiene. It arrives clean. Stage three is campaign automation. This is where the return visit lift happens. Purple Engage triggers SMS campaigns based on behaviour. A welcome message fires within minutes of the first connection. A re-engagement message fires at day 30 if the guest hasn't returned. A flash offer triggers when footfall data shows a quiet Tuesday afternoon. A post-visit message fires 24 hours after departure with a reason to come back. Each of these triggers is configurable. You set the rules. The platform executes them at scale, across every venue in your estate simultaneously. Let me give you two concrete scenarios. Scenario one: a 350-room hotel group. They deploy Purple Engage across 12 properties. Within six months, they've captured 48,000 verified phone numbers with SMS consent. Their re-engagement campaign - a simple message at day 45 offering a 15% discount on the next stay - drives a 34% lift in return bookings among the SMS cohort versus a control group. The cost per recovered booking is under three pounds. The average booking value is 180 pounds. That's the kind of ratio that gets a marketing director a budget increase. Scenario two: a retail chain with 60 stores. They use Purple Engage to build a segmented SMS list by store location and visit frequency. High-frequency shoppers receive early access to sales. Lapsed shoppers - those who haven't visited in 60 days - receive a personalised re-engagement offer. The lapsed-shopper campaign alone drives a 22% reactivation rate. McDonald's Belgium used Purple to collect over 2.5 million unique visitor records to improve their customer experience. The data infrastructure is the same. [short pause] Now, implementation pitfalls. I'll be direct about the things that go wrong. The first failure mode is poor opt-in design. If your captive portal buries the SMS checkbox or pre-ticks it, you're collecting non-compliant consent. Under UK GDPR and the Privacy and Electronic Communications Regulations - PECR - that exposes you to enforcement action. The ICO has issued fines for exactly this. Design the opt-in to be explicit, unambiguous, and separate from the WiFi access grant. Purple's portal templates are built to this standard by default. The second failure mode is frequency abuse. Sending more than one or two messages per week without a clear value exchange drives opt-out rates above 3.5%. Once someone unsubscribes, you cannot contact them again. That contact is gone. Treat your SMS list as a high-value asset, not a broadcast channel. Every message needs a reason to exist. The third failure mode is poor segmentation. Sending the same message to a first-time visitor and a 20-visit loyal guest is a waste of both. Purple Engage segments by visit frequency, location, dwell time, and demographic data collected at login. Use it. A segmented campaign consistently outperforms a broadcast campaign by a factor of three to five on conversion rate. The fourth failure mode is ignoring attribution. If you can't measure return visit lift against a control group, you can't justify the programme to your CFO. Purple's analytics dashboard tracks return visit rates for SMS recipients versus non-recipients. Set that up before you launch the first campaign. [short pause] Let me run through the rapid-fire questions I get most often from IT and marketing teams. Does Purple work with our existing hardware? Yes. Purple is hardware-agnostic. It works as a cloud overlay on Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme, and Fortinet. You don't replace your network. You add Purple on top. Is the data GDPR compliant? Purple is ISO 27001 certified, GDPR and CCPA compliant, and Cyber Essentials certified. Consent records are time-stamped and exportable for audit. The platform operates at 99.999% uptime. How quickly can we go live? A standard deployment across an existing network takes between two and four weeks, including portal design, CRM integration, and campaign configuration. Larger multi-site estates take longer, but Purple's professional services team handles the rollout. What's the minimum viable campaign? Start with three automated journeys: a welcome message on day one, a re-engagement message at day 30, and a loyalty reward at visit five. Those three alone will generate measurable return visit lift within 90 days. [short pause] To summarise. Your Guest WiFi is already collecting connection events. The question is whether you're converting those events into verified, consented first-party contacts. SMS marketing is the highest-engagement channel available for re-engaging those contacts and driving return visits. The architecture is straightforward: captive portal capture, Purple Engage automation, CRM sync, and behaviour-triggered campaigns. The compliance framework is well-defined under GDPR and PECR. The ROI is documented across hospitality, retail, and events verticals. The next step is an audit of your current captive portal. Does it capture phone numbers? Does it present a compliant SMS opt-in? If the answer to either question is no, that's where you start. Purple's team can walk you through a portal assessment and show you what a compliant, high-converting login flow looks like in practice. Thanks for listening. You'll find the full written guide, architecture diagrams, and worked examples at purple.ai. We'll see you in the next briefing.