How to leverage SMS marketing tools to increase return visits

Speak in British English with a confident, authoritative, conversational tone - like a senior consultant briefing a client in a boardroom. Measured pace, clear diction, calm authority. Not a lecture. Not a sales pitch. Just a smart professional sharing what works: Welcome to the Purple technical briefing series. Today we are talking about SMS marketing tools - specifically how venue operators can use their existing guest WiFi infrastructure to build a high-performing SMS channel that drives measurable return visits. [short pause] Let me set the scene. You are running a hotel, a retail chain, a stadium, or a conference centre. You have guest WiFi already deployed. Guests connect every day. And right now, most of those connections are just connectivity. The guest gets online, you get nothing back. No data, no contact, no way to bring them back next week or next month. That is the problem we are solving today. [medium pause] Section one. Why SMS outperforms every other re-engagement channel. Here is the headline number. SMS delivers a 98% open rate. Email sits at around 21%. Paid social is worse. Display advertising is worse still. When you send an SMS, it gets read - typically within three minutes of delivery, according to Sakari's 2025 SMS Marketing Statistics report. The ROI data is equally compelling. Conservative industry estimates put SMS returns at between 21 and 41 dollars in revenue for every dollar spent. Some peak seasonal campaigns report up to 71 dollars per dollar. For context, email marketing - already a strong channel - returns between 10 and 36 dollars per dollar. SMS consistently beats it. Click-through rates on SMS campaigns average around 26%, compared to roughly 3% for email. Response rates hit 45%, versus 6% for email. These are not marginal differences. They are structural advantages of a channel where the message lands directly in the notification tray of a device people check over 150 times a day. Now, here is the critical question for venue operators. Where do you get the phone numbers? And how do you get them compliantly? This is where your guest WiFi infrastructure becomes a genuine competitive asset. [medium pause] Section two. The technical architecture - from WiFi login to SMS campaign. The flow has five stages. Stage one is the physical layer. Your access points - whether that is Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, or Ubiquiti UniFi - are already deployed. They handle the radio frequency layer. Purple sits as a cloud overlay on top of that hardware, which means you do not need to rip and replace anything. Hardware-agnostic deployment is the starting point. Stage two is the captive portal. When a guest connects to your Guest WiFi network, they hit a branded splash page. This is where data capture happens. The portal presents a phone number field alongside a standalone SMS marketing opt-in checkbox. That checkbox is separate from the WiFi terms and conditions. That separation is not a user experience nicety - it is a legal requirement under GDPR Article 7 and TCPA prior express written consent rules. The consent must be granular, specific, and documented with a timestamp. Purple's Engage plan handles this automatically. The portal captures the phone number, records the consent event with a timestamp, and writes the record directly to the guest profile in the platform. Stage three is the data layer. Purple Engage builds a unified guest profile from every WiFi login. That profile includes the phone number, the consent status, the visit timestamp, the venue location, and the visit frequency. Over time, you accumulate behavioural signals - first-time visitor, repeat visitor, lapsed visitor - that drive segmentation. Stage four is the campaign engine. Purple Engage connects to your SMS gateway via API. You define automated journeys: a welcome message on first connection, a re-engagement message after 30 days of absence, a promotional message tied to a specific venue event. The platform handles delivery, tracks open rates and click-throughs, and feeds performance data back into the analytics dashboard. Stage five is SMS delivery itself. The message hits the guest's handset within seconds of the trigger firing. The guest sees a personalised offer, clicks through, and books a return visit. That is the full loop. [medium pause] Let me give you a concrete architecture example. A 200-room hotel running Cisco Meraki access points deploys Purple Engage as a cloud overlay. The captive portal is branded to the hotel. Guests log in with their mobile number and tick the SMS opt-in box. Purple writes the consent record to the guest profile. After check-out, an automated journey triggers a message 48 hours later with a loyalty offer. Guests who have not returned within 60 days receive a re-engagement message with a discounted rate. The hotel's CRM receives all profile data via one of Purple's 400-plus connector integrations. WiFi login to verified phone number to automated SMS campaign to return visit. [medium pause] Section three. Implementation - the four configuration stages. Stage one is network setup. Confirm your access points are on the supported hardware list - Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme, or Fortinet. Purple deploys as a cloud overlay, so the configuration change is at the SSID level. You create a dedicated Guest WiFi SSID and point it at Purple's captive portal URL. This takes under an hour on most enterprise hardware. Stage two is portal design. Build your branded splash page in Purple's portal editor. The phone number field and SMS opt-in checkbox are standard components. The consent language must be plain English - something like: I agree to receive promotional SMS messages from this venue. Message frequency varies. Reply STOP to unsubscribe. That language satisfies both GDPR and TCPA requirements. Stage three is consent architecture. This is where most operators make mistakes. The SMS opt-in must be a standalone checkbox. It cannot be pre-ticked. It cannot be bundled with the WiFi terms. Purple's portal builder enforces this by default, but you should verify it before going live. Your legal team should sign off on the consent copy. Stage four is campaign automation. In Purple Engage, you build automated journeys using visit behaviour as triggers. Define your segments - first-time visitors, repeat visitors, lapsed visitors. Set your message cadence. A typical starting configuration is a welcome message on first connection, a follow-up offer at seven days, and a re-engagement message at 30 days. Keep message frequency to two or three per month maximum. Higher frequency drives unsubscribe rates up sharply. [medium pause] Section four. Real-world results - two case studies. Case study one: rail travel. Avanti West Coast deployed Purple Engage across their train network. By surfacing upsell offers through the WiFi journey - including SMS-triggered promotions - they achieved 3,744 purchases and a 463% return on investment. The key was timing: messages were triggered by presence on the network, not by a generic broadcast schedule. Case study two: retail. McDonald's used Purple to collect over 2.5 million unique visitor records. That data foundation enabled targeted SMS and email campaigns that drove measurable improvements in visit frequency and average spend. The data quality was high because it was captured at the point of physical presence - not from a third-party list. Both cases share the same pattern: verified first-party data captured at the moment of physical engagement, then activated through automated campaigns. The WiFi login is the data collection event. Everything else follows from it. [medium pause] Section five. Pitfalls and how to avoid them. Pitfall one: bundled consent. If your SMS opt-in is embedded in the WiFi terms, your consent is invalid under GDPR. Regulators have fined organisations for exactly this. Use a standalone checkbox. Pitfall two: no suppression list. Every SMS campaign must honour opt-outs instantly. If a guest replies STOP and receives another message, you are in breach of TCPA. Purple Engage manages suppression lists automatically, but if you are using a separate SMS gateway, ensure the suppression sync is real-time. Pitfall three: over-messaging. The fastest way to destroy an SMS list is to send too many messages. Two to three per month is the industry standard. More than that and unsubscribe rates climb sharply. Pitfall four: ignoring delivery rates. Monitor your delivery rate - anything below 95% signals a list quality problem. Purple's analytics dashboard surfaces delivery metrics in real time. Pitfall five: no attribution model. If you cannot connect an SMS send to a return visit, you cannot prove ROI. Purple's WiFi Analytics platform tracks return visit rates for SMS recipients versus non-recipients. Set this up before your first campaign, not after. [medium pause] Now, rapid-fire questions. Do I need a separate SMS platform, or does Purple handle it end to end? Purple Engage handles data capture, segmentation, journey automation, and analytics. For SMS delivery, it connects to your chosen SMS gateway via API. Most operators use an existing gateway - Twilio, MessageBird, or similar. Purple is the intelligence layer; the gateway is the delivery layer. How long does it take to build an SMS list from scratch? At a venue with 500 daily WiFi logins and a 30% opt-in rate, you build a list of 150 new contacts per day. Within 90 days, you have 13,500 opted-in contacts. That is a meaningful campaign audience built entirely from first-party data. What is a realistic return visit lift from SMS campaigns? Industry data shows SMS recipients visit three times more frequently than non-recipients. Purple's own data across 80,000-plus live venues shows that venues running automated re-engagement campaigns see measurable return visit increases within the first 60 days of activation. [medium pause] Summary and next steps. The core argument is straightforward. Guest WiFi is already deployed. It generates verified phone numbers at the point of physical presence. Those numbers, captured with proper consent, feed an SMS channel that outperforms every other re-engagement channel by open rate, click-through rate, and ROI. The implementation path is four stages: network setup, portal design, consent architecture, and campaign automation. The compliance requirements are clear: standalone opt-in, plain language consent, instant opt-out processing, timestamped records. If you are running Purple Engage, you have the infrastructure to do this today. If you are on the Connect or Capture plan, upgrading to Engage unlocks the full automation and SMS integration capability. The next step is to audit your current captive portal. Does it capture phone numbers? Does it have a standalone SMS opt-in? If not, that is the first thing to fix. Everything else - the campaigns, the journeys, the ROI - follows from having the data. Thank you for listening to the Purple technical briefing series. For more on Guest WiFi analytics and SMS marketing implementation, visit purple.ai.