Skip to main content

How to leverage lic marketing SMS to increase return visits

This technical reference guide details how venue operators and IT managers can implement Login Identity Capture (LIC) via Guest WiFi to drive high-converting SMS marketing campaigns. It covers deployment architecture, GDPR/TCPA compliance frameworks, and real-world implementation strategies to increase return visits.

📖 4 min read📝 932 words🔧 2 worked examples3 practice questions📚 8 key definitions

Listen to this guide

View podcast transcript
You are a senior consultant delivering a confident, authoritative technical briefing to enterprise clients. Speak in British English with a clear, measured pace. Professional, direct, and conversational. Slight gravitas throughout. No filler words. UK English accent: Welcome to the Purple technical briefing. Today we are looking at LIC marketing SMS - Login Identity Capture combined with SMS campaigns - and specifically how venue operators can use this approach to drive measurable return visits. If you manage IT or venue operations for a hotel chain, a retail estate, a stadium, or a conference centre, you already have the infrastructure you need. The question is whether you are using it. [medium pause] Let me start with the fundamentals. LIC marketing SMS is a three-part system. First, you capture a verified mobile number at the point of WiFi login. Second, you build a behavioural profile from the visitor's physical presence data. Third, you use that profile to trigger automated, targeted SMS campaigns that bring the visitor back. The channel performance data is unambiguous. SMS achieves a 98% open rate. 90% of messages are read within three minutes of delivery. Compare that to email, which sits at around 20 to 28% open rate. When you need a guest to take action - book a return visit, redeem an offer, respond to a flash sale - SMS is the channel that delivers. The ROI benchmarks support this: conservative estimates put SMS returns at between 21 and 71 pounds for every pound spent, according to Sakari's 2025 data and Attentive's 2024 seasonal campaign analysis. [medium pause] Now, the architecture. This is where the technical detail matters, so let me walk you through it precisely. The data capture pipeline begins at the access point. Whether you are running Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme, or Fortinet hardware, the mechanism is the same. Purple deploys as a cloud overlay - no firmware changes, no hardware replacement. You configure a dedicated Guest WiFi SSID and point it at Purple's captive portal. When a visitor connects, they hit a branded splash page. This is the Login Identity Capture event. 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 critical technical component here is the double opt-in OTP flow. When the visitor enters their number and ticks the opt-in box, Purple Engage triggers a POST request to the SMS gateway API - Twilio or Infobip are the most common integrations. The gateway sends a one-time password to the device. The visitor enters the OTP on the portal. A successful entry confirms the device is in their possession. Purple then logs the consent record: timestamp, IP address, portal version, and the exact consent text displayed. The RADIUS server authenticates the session and grants network access. The visitor is now a verified, consented contact in your SMS subscriber list. [medium pause] From that point, Purple Engage builds a unified guest profile. Every subsequent WiFi login adds data: visit frequency, dwell time, zones visited, time of day. Over time, you accumulate the behavioural signals that drive intelligent segmentation. The segmentation logic is where most operators underinvest. You have three primary segments: first-time visitors, repeat visitors, and lapsed visitors. Each requires a different message strategy. For first-time visitors, send a welcome message within 24 hours. Keep it brief. Acknowledge the visit, offer a reason to return. For repeat visitors, use their visit history. If a guest has visited your hotel restaurant three times but never booked a room, send them a discounted weekend rate. If a shopper spends 45 minutes in the sports section of your retail store, send a 10% discount code for athletic wear. For lapsed visitors - those who have not returned within 30 to 60 days - send a re-engagement message with a time-bound offer. The urgency of SMS makes it the right channel for this. [medium pause] Let me give you two real-world examples that illustrate this in practice. Avanti West Coast deployed Purple Engage across their train network. By triggering upsell offers through the WiFi journey - including SMS-triggered promotions tied to physical presence on the network - 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. McDonald's Belgium 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] Now, implementation recommendations and the pitfalls to avoid. The four configuration stages are straightforward. Stage one: confirm your access points are on the supported hardware list and configure the Guest WiFi SSID to redirect to Purple's captive portal. This takes under an hour on most enterprise hardware. Stage two: 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 your venue. Message frequency varies. Reply STOP to unsubscribe. That language satisfies both GDPR and TCPA requirements. Stage three: 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 verify it before going live and get your legal team to sign off on the consent copy. Stage four: campaign automation. Define your segments and 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] The pitfalls. There are five I see repeatedly. First: bundled consent. If your SMS opt-in is embedded in the WiFi terms, your consent is invalid under GDPR. The ICO can issue fines of up to 17.5 million pounds or 4% of global annual turnover. Use a standalone checkbox. Second: no suppression list synchronisation. 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. Third: over-messaging. Two to three messages per month is the industry standard. More than that and unsubscribe rates climb sharply. An opt-out rate above 2% per campaign is a reliable signal that frequency is too high or the segment is too broad. Fourth: 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. Fifth: 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. [medium pause] Now, a rapid-fire question and answer based on common queries from enterprise clients. Does SMS marketing replace the email strategy? No. They serve different functions. Use email for newsletters, detailed updates, and brand building. Use SMS for urgent, time-bound offers and operational alerts. SMS plus email produces roughly 56% higher ROI than email alone, according to Sakari's 2025 analysis. How do you handle international visitors? Your captive portal must capture the country code. Ensure your SMS gateway supports international routing, but be aware of the cost implications. You may choose to restrict SMS marketing to domestic numbers and use email for international guests. 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 built entirely from first-party data. What is a realistic return visit lift? Purple's own data across 80,000 plus live venues shows that SMS recipients visit three times more frequently than non-recipients. Venues running automated re-engagement campaigns see measurable return visit increases within the first 60 days of activation. [medium pause] To summarise. LIC marketing SMS is a high-impact channel for driving return visits. The infrastructure - your Guest WiFi network - is already deployed. The data capture mechanism - the captive portal - is already in place. The missing step is configuring it to capture verified phone numbers via a double opt-in flow, building behavioural segments from visit data, and activating those segments through automated SMS journeys. The compliance requirements are clear: standalone opt-in, plain language consent, instant opt-out processing, timestamped records. Purple Engage handles the consent record management, suppression list synchronisation, and analytics attribution automatically. If you are on Purple's 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 joining this Purple technical briefing. For more on Guest WiFi analytics and SMS marketing implementation, visit purple.ai.

header_image.png

Executive Summary

SMS marketing delivers a 98% open rate, with 90% of messages read within three minutes of delivery. For venue operators running Guest WiFi across hotels, retail estates, or stadiums, the data capture infrastructure already exists. The missing step is converting that anonymous network traffic into a verified, consented SMS subscriber list. Purple Engage captures phone numbers at the captive portal, enforces a double opt-in verification flow, and automates campaign dispatch based on physical presence analytics. The result: conversion rates between 21% and 30%, and an ROI of £21 to £71 for every £1 spent on SMS. This guide covers the end-to-end architecture, from access point to SMS gateway, the compliance requirements under GDPR and TCPA, and the segmentation strategies that separate relevant offers from spam.

Technical Deep-Dive: Architecture and Integration

The data pipeline for an SMS marketing service begins at the wireless controller. Whether you deploy Cisco Meraki, HPE Aruba, Ruckus, Juniper Mist, Ubiquiti UniFi, Cambium, Extreme, or Fortinet access points, the mechanism is consistent: the controller intercepts unauthenticated HTTP traffic and redirects the device to the captive portal hosted by Purple. Purple operates as a cloud overlay on top of your existing hardware, meaning no firmware changes are required. You configure the captive portal redirect at the wireless controller level using standard RADIUS change of authorisation (CoA) messages.

The Double Opt-In Verification Flow

To build an SMS subscriber list, you configure the Guest WiFi portal to present a phone number field alongside the standard email or social login options. A single opt-in is insufficient. It allows users to enter fictitious numbers, polluting your CRM, and it does not satisfy the "prior express written consent" standard required by the TCPA for US venues, nor the "unambiguous indication" standard under GDPR for UK and European venues.

The double opt-in flow resolves both problems:

  1. The visitor enters their mobile number and selects the SMS marketing opt-in checkbox (unchecked by default).
  2. Purple Engage triggers a POST request to the SMS gateway API.
  3. The gateway sends a one-time password (OTP) to the device via SMS.
  4. The visitor enters the OTP on the portal. A successful entry confirms the device is in the visitor's possession.
  5. Purple logs the consent record, including the timestamp, IP address, portal version, and the exact consent text displayed.
  6. The RADIUS server authenticates the session and grants network access.

sms_compliance_architecture.png

This flow ensures every phone number in your database is reachable, verified, and accompanied by an auditable consent record.

Implementation Guide: Segmentation and Automation

Once the capture architecture is running, the focus shifts to WiFi Analytics . Purple Engage builds a unified guest profile from every WiFi login. Over time, you accumulate behavioural signals - first-time visitor, repeat visitor, lapsed visitor - that drive segmentation.

Define Your Segments

Segment your audience based on their physical behaviour. Because Purple tracks device MAC addresses, you know exactly how many times a user has visited, how long they stayed, and which zones they spent time in. Use this data. If a guest visits your hotel restaurant three times but has never booked a room, send them an SMS offer for a discounted weekend stay. If a shopper spends 45 minutes in the sports section of your Retail store, send them a 10% discount code for athletic wear.

Automate the Journeys

In Purple Engage, you build automated journeys using visit behaviour as triggers. A typical starting configuration is:

  • Welcome message: Sent 24 hours after first connection.
  • Follow-up offer: Sent at seven days.
  • Re-engagement message: Sent at 30 to 60 days to lapsed visitors.

Keep message frequency to two or three per month maximum. Higher frequency drives unsubscribe rates up sharply.

Best Practices and Compliance

Running an SMS marketing service without a well-structured compliance architecture exposes your organisation to substantial fines. The Information Commissioner's Office (ICO) can issue fines of up to £17.5 million or 4% of global annual turnover under UK GDPR. In the US, TCPA violations carry statutory damages of $500 to $1,500 per unsolicited text.

Under GDPR, consent for SMS marketing must be freely given, specific, informed, and unambiguous. The opt-in cannot be a condition of accessing the WiFi. The checkbox must be optional and un-ticked by default.

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, ensuring compliance.

Troubleshooting & Risk Mitigation

Failure Mode: High Unsubscribe Rates

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. An opt-out rate above 2% per campaign is a reliable signal that frequency is too high or the segment is too broad; diagnose before sending the next campaign.

Failure Mode: Poor List Quality

Monitor your delivery rate. Anything below 95% signals a list quality problem, often caused by failing to implement double opt-in verification. Purple's analytics dashboard surfaces delivery metrics in real time.

ROI & Business Impact

Industry benchmarks show a return of £21 to £71 for every £1 spent on SMS marketing. When you use first-party data captured via WiFi, the acquisition cost is near zero, pushing the ROI even higher.

sms_vs_email_comparison.png

To prove ROI, you must connect an SMS send to a return visit. Purple's WiFi Analytics platform tracks return visit rates for SMS recipients versus non-recipients. Set this attribution model up before your first campaign, not after.

Listen to the Briefing

Key Definitions

Login Identity Capture (LIC)

The process of collecting verified user data (like a phone number) at the point of authentication, typically via a Guest WiFi captive portal.

This is the foundational step for building a first-party database without relying on third-party cookies or paid acquisition.

Double Opt-In Verification

A two-step consent process where a user submits their phone number and must then verify it by entering a One-Time Password (OTP) sent to that device.

Essential for maintaining database hygiene and proving 'prior express written consent' under TCPA regulations.

Captive Portal

A web page that a user of a public access network is obliged to view and interact with before access is granted.

The primary interface where venue operators capture visitor data and secure marketing consent.

RADIUS CoA (Change of Authorisation)

A mechanism that allows a RADIUS server to dynamically change the access permissions of an active client session.

Used by Purple to move a device from the restricted captive portal VLAN to the internet-access VLAN once the OTP is verified.

TCPA (Telephone Consumer Protection Act)

US legislation restricting telemarketing calls and the use of automated telephone equipment, including SMS text messages.

Requires businesses to obtain prior express written consent before sending marketing texts; failure to comply results in severe financial penalties.

First-Party Data

Information a company collects directly from its customers and owns entirely.

Phone numbers captured via Guest WiFi are high-value first-party data, reducing reliance on expensive third-party ad networks.

Suppression List

A database of contacts who have opted out of receiving communications (e.g., by replying STOP).

Real-time synchronisation of the suppression list between the WiFi platform and the SMS gateway is legally mandatory.

Dwell Time

The duration a visitor spends connected to the network within a specific physical zone.

A key behavioural metric used to segment audiences; e.g., targeting shoppers who dwell for over 45 minutes in a specific retail department.

Worked Examples

A national transport operator needs to increase ancillary revenue across its network of 40 stations while complying with strict UK GDPR regulations.

The operator deployed Purple Engage across their train network's existing hardware. They configured the captive portal with a standalone, un-ticked SMS opt-in checkbox and implemented a double opt-in OTP flow to verify numbers. They then built automated journeys triggered by presence on the network, rather than generic broadcast schedules. For example, surfacing upsell offers to passengers waiting in the station.

Examiner's Commentary: This approach works because it captures verified first-party data at the moment of physical engagement. By tying promotions to physical presence (e.g., waiting for a train) rather than arbitrary times, the relevance of the message increases significantly. This strategy achieved 3,744 purchases and a 463% ROI.

A fast-food retail chain wants to build a database of customer phone numbers to drive repeat visits, but is concerned about fake numbers polluting their CRM.

The retail chain implemented Login Identity Capture (LIC) via their Guest WiFi. Crucially, they enforced OTP verification via SMS before granting network access. Once verified, they collected over 2.5 million unique visitor records. They then segmented this audience based on visit frequency to deliver targeted SMS campaigns.

Examiner's Commentary: The mandatory OTP step eliminates the risk of fake numbers, ensuring a high-quality database. By using Purple as the intelligence layer to track visit frequency, the chain could send relevant offers (e.g., a win-back offer to a customer who hasn't visited in 30 days) rather than spamming their entire list.

Practice Questions

Q1. Your marketing team wants to increase the SMS subscriber list quickly. They propose making the SMS opt-in checkbox pre-ticked on the Guest WiFi captive portal. Do you approve this change?

Hint: Consider the GDPR requirements for valid consent.

View model answer

No. Under GDPR, consent must be an 'unambiguous indication' and an active, conscious choice. Pre-ticked boxes are explicitly invalid. Implementing this would expose the venue to substantial ICO fines.

Q2. A stadium venue experiences a 4% unsubscribe rate following a recent SMS campaign. The campaign was sent to all 50,000 verified contacts in the database. What is the most likely cause, and how should you adjust the strategy?

Hint: An opt-out rate above 2% indicates a structural problem with the campaign.

View model answer

The most likely cause is a lack of segmentation; sending a generic broadcast to the entire database means the offer was irrelevant to many recipients. The strategy should be adjusted to trigger smaller, targeted campaigns based on visit history (e.g., targeting only fans who attended the previous match).

Q3. You are deploying Purple Engage across a hotel chain using Cisco Meraki access points. The IT Director asks if they need to schedule downtime to upgrade the AP firmware to support the new SMS OTP flow. What is your response?

Hint: Consider how Purple integrates with existing enterprise hardware.

View model answer

No downtime or firmware upgrades are required. Purple operates as a cloud overlay. The integration is handled at the wireless controller level by configuring a dedicated SSID to redirect to the Purple captive portal, using standard RADIUS CoA messages.