How to leverage marketing automation SMS to increase return visits

Welcome to the Purple technical series. Today we are talking about marketing automation SMS - specifically how venue operators can use it to drive measurable return visits. Whether you run a hotel group, a retail chain, a stadium, or a conference centre, the principle is the same. You have people walking through your doors every day. Most of them connect to your Guest WiFi. And most of them leave without you having any reliable way to bring them back. That is the problem we are solving today. Let me start with the numbers, because they make the case better than any argument I could construct. SMS messages carry a 98% open rate. Email sits at around 20 to 30%. 80% of text messages are read within five minutes of delivery. Response rates for SMS campaigns average around 45%, compared to roughly 6% for email. And ROI estimates from multiple industry studies place SMS returns between 21 and 41 pounds for every pound spent - with some seasonal campaigns hitting 71 to one. Those are not projections. Those are benchmarks from 2025 and 2026 data compiled by Infobip and Sakari. So the channel works. The question is how you get the data to use it properly. This is where Guest WiFi becomes the foundation. When a guest, a shopper, or a fan connects to your WiFi network through a captive portal, they authenticate. They provide a verified phone number. And critically, at the point of login, they give explicit consent to receive marketing communications. That is a conscious-choice opt-in - not a pre-ticked box, not an assumed permission. It is a GDPR-compliant, documented consent event tied to a real, verified mobile number. Purple Engage captures that data at login across 80,000-plus live venues. We have collected 29 billion data points and processed 440 million logins in 2024 alone. Every one of those logins is a potential entry point into an SMS automation workflow. Now let us talk architecture - because this is where IT teams need to pay attention. The data flow has five stages. Stage one: the visitor connects to your Guest WiFi through a captive portal hosted on hardware from Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, or any of the other platforms we support. Stage two: the captive portal collects the phone number and records the consent event with a timestamp, consent text version, and IP address - all stored in line with GDPR Article 7 requirements. Stage three: that data feeds into Purple Engage, where it builds a first-party profile enriched with visit frequency, dwell time, location within the venue, and behavioural segments. Stage four: the SMS automation engine evaluates trigger rules. Did this person visit for the first time? Did they return after 30 days of absence? Did they hit a loyalty threshold? Each trigger fires a pre-configured SMS workflow. Stage five: the personalised message lands on their phone. Within five minutes, 80% of them have read it. The return visit data from stage five then feeds back into stage three, continuously enriching the profile. That is the loop that compounds over time. Let me give you two concrete implementation scenarios. Premier Inn operates across hundreds of UK locations. The challenge in hospitality is that guests stay once, enjoy the experience, and then book their next trip through an OTA - an online travel agency - which captures the relationship and the data. Guest WiFi login at check-in captures the phone number directly. An automated SMS fires 48 hours after checkout: a personalised message with a direct booking incentive. No OTA commission. No intermediary. The guest books direct. The hotel measures the incremental revenue against the campaign cost and calculates a clear ROI. That is the model. In retail, consider a fashion chain with 200 stores. A shopper connects to in-store WiFi. The automation engine detects they have not visited in 45 days. An SMS fires with a time-limited offer - valid for the next seven days in-store only. The message drives a physical return visit that an email campaign would have missed entirely, because the email would have sat unread in a promotional folder. The SMS was read within three minutes. Now for implementation. Here are the five steps you need to execute. Step one: audit your captive portal for phone number capture. If your current splash page only collects email, you need to add a phone field with explicit SMS opt-in consent language. The consent text must be specific - it cannot be bundled with general terms. GDPR Article 7 requires granular, informed consent. Step two: validate your data pipeline. Phone numbers collected at login must be formatted to E.164 international standard before they enter your SMS platform. A UK mobile number must be stored as plus-44 followed by the number without the leading zero. Bad formatting is the single most common cause of delivery failure. Step three: define your trigger logic. Start with three triggers: first visit welcome, lapsed visitor win-back at 30 days, and loyalty milestone. Do not try to automate 20 scenarios on day one. Get those three working, measure them, then expand. Step four: configure your send windows. SMS sent between 9am and 8pm local time performs significantly better than messages sent outside those hours. Most SMS platforms allow timezone-aware scheduling. Use it. Step five: set frequency caps. The data is clear - 53% of SMS unsubscribes are caused by over-frequency. Cap at two messages per month per contact as a starting point. You can increase this for segments that demonstrate high engagement, but start conservative. Let me address the pitfalls, because there are several that derail implementations. The first is consent drift. You collect consent at login, but then your CRM team imports that list into a third-party platform without verifying that the consent record travels with it. Under GDPR, consent must be demonstrable at the point of use, not just at the point of collection. Your data architecture must carry the consent metadata - timestamp, version, channel - through every system that touches that record. The second pitfall is message content that reads like spam. A message that says 'Hi, click here for a deal' will get ignored or reported. A message that says 'Hi Sarah, your 10% loyalty discount is ready to use at our Manchester store until Sunday' gets acted on. Personalisation is not optional - it is the difference between a 2% click rate and a 25% click rate. The third pitfall is ignoring opt-out mechanics. Every SMS must include a clear opt-out instruction - typically 'Reply STOP to unsubscribe.' Your platform must process those opt-outs in real time and suppress that number across all future campaigns. Failure to do this is not just a compliance risk - it is a brand risk. Rapid-fire questions now. Can SMS automation work for public-sector venues? Yes. Consent-based SMS is used effectively in transport hubs, libraries, and leisure centres - the compliance requirements are the same, the mechanics are identical. Does SMS replace email? No. The two channels are complementary. SMS handles urgency and time-sensitive offers. Email handles depth and longer-form content. The combination produces roughly 56% higher ROI than email alone, according to Sakari's 2025 data. What is a realistic opt-in rate from WiFi login? In well-configured deployments, between 40% and 60% of WiFi users who provide a phone number for authentication will also opt in to marketing SMS. The key variable is how the consent question is framed on the splash page. To summarise. Marketing automation SMS is the highest-engagement channel available to venue operators today. The 98% open rate is not a marketing claim - it is a documented benchmark. The data foundation is Guest WiFi login, which provides verified phone numbers with documented consent. The architecture is a five-stage loop: WiFi login, captive portal capture, first-party profile, automation engine, personalised SMS delivery, and return visit data feeding back into the profile. Start with three triggers - welcome, win-back, and loyalty milestone. Cap frequency at two messages per month. Carry consent metadata through every system. Personalise every message. If you want to see how Purple Engage implements this across Cisco Meraki, HPE Aruba, Ruckus, and Juniper Mist deployments, visit purple dot ai. The platform is hardware-agnostic, GDPR and ISO 27001 certified, and live in 80,000-plus venues today. Thank you for listening.