SMS

CaptiFi supports SMS in three ways: SMS Marketing (campaigns and automations to your opted-in guests, powered by prepaid credits), guest welcome SMS (a welcome text to guests who share their number, via the Twilio integration) and staff SMS alerts (infrastructure notifications to your own phone).

SMS Marketing

Send one-off campaigns ("This weekend only...") or automated texts (welcome messages, review requests, win-back offers) to guests who have shared their mobile number and opted in to SMS. Find it under Marketing then SMS Marketing in the my.captifi.io sidebar.

Who receives your messages

A guest is reachable by SMS when all of these are true:

• They provided a phone number through your splash page or a contact import
• They gave permission to be texted (see below)
• They have not replied STOP or been manually opted out

Permission works in one of two ways, per venue:

• Without the SMS opt-in checkbox (the default): guests who accepted marketing when connecting, and imported contacts with marketing permission, can be texted. One consent covers your marketing, email and SMS alike.
• With the SMS opt-in checkbox enabled on your splash page: texting becomes strictly opt-in at that venue. Only guests who tick the SMS box can be texted, and leaving it unticked is treated as a "no" that CaptiFi respects even if the guest accepted email marketing.

To collect explicit SMS opt-ins, add a Phone number question and turn on the SMS opt-in checkbox in your splash page builder - see Collecting numbers for SMS Marketing.

As you build a campaign, the audience panel next to the composer shows you exactly who you are about to text before you send anything:

• Estimated recipients in total, and per venue
• A by-country breakdown based on each guest's phone country code, so you can see where your messages are going
• Excluded numbers: how many opted-out numbers were removed, and how many duplicates were removed when the same guest appears at more than one of your venues (each person is only texted once per campaign)

Credits and message cost

SMS Marketing uses prepaid credits: 1 credit = 1 SMS segment per recipient. Every destination currently costs the same. A segment is up to 160 characters for a plain-text message; longer messages are split into segments of 153 characters. Messages containing special characters or emoji are sent as unicode, which reduces each segment to 70 characters (67 when split), so plain text goes much further.

A short opt-out footer ("Reply STOP to opt out") is added to every marketing message automatically and is included in the character count you see in the composer.

The audience panel shows the full cost before you send: recipients x segments = credits required, alongside your current balance. If you do not have enough credits the send is blocked until you top up, and your campaign is kept as a draft so nothing is lost.

Buy credits on the Credits and billing tab: packs of 500, 2,000 or 10,000 credits, paid by card. Your balance is shared across all of your venues, and every top-up, send and refund appears in the transaction history on the same tab.

Auto top-up keeps campaigns and automations running unattended: save a card, pick a threshold and a pack, and CaptiFi tops your balance up automatically whenever it drops below the threshold. Every automatic purchase appears in the transaction history like any other top-up.

Sending rules

• Quiet hours: marketing texts are not sent overnight (by default between 21:00 and 09:00 in the venue's local time); messages queued during quiet hours go out afterwards
• Opt-outs are instant: a guest replying STOP is suppressed across all your venues immediately, and failed messages are refunded to your balance
• Campaigns can be sent immediately, saved as drafts, or scheduled for later
• Test it first: send any draft to your own phone from the composer before texting guests; a test costs the same credits as one real message
• Change your mind: drafts can be edited or deleted, and a scheduled campaign can be cancelled any time before it goes out
• Delivery is tracked: the Delivered stat reflects real carrier receipts, and failures are refunded

Opt-outs

The Opt-outs tab lists every number that cannot be texted: guests who replied STOP, numbers you added manually, and carrier-level blocks. Add a number there to opt someone out on the spot (for example a guest who asks in person). Removing a manual entry lets that number receive texts again, but guests who replied STOP stay unsubscribed until they opt in again themselves.

Automations

On the Automations tab, set up texts that send themselves: welcome a guest after sign-up, ask for a review after a visit, wish them a happy birthday, or win back guests who have not been in for a while. Picking a trigger starts you off with a ready-made message you can edit, and each automation has its own venue targeting and audience rules (everyone, marketing consent only, first-time or repeat visitors).

Triggers only appear once the data behind them exists, so you are never offered an automation that cannot send:

• Birthday appears once you have birthdays on file (collected on your splash page, or included in a contact import). It only ever sends to guests with a birthday set, once a year, on the day.
• Review request appears once Google Reviews is connected with a review link, so guests are never sent somewhere they cannot leave a review.
• We miss you (lapsed guest) asks for a number of days: a guest who has not visited for that many days gets the text once, not every day after.
• Welcome and welcome back send after a first visit or a return visit, with an optional delay.

Compliance

Marketing texts need valid consent under GDPR and PECR, and the consent a guest gave must cover texting. If you rely on the default single marketing consent, make sure your splash page consent wording mentions texts as well as emails; if you want unambiguous, channel-specific consent, enable the SMS opt-in checkbox. CaptiFi adds the STOP opt-out footer for you and honours opt-outs automatically. See GDPR Best Practices.

Guest Welcome SMS (Twilio Integration)

Send an automatic welcome SMS to every WiFi guest who provides a phone number and opts in.

Setup

1. Log in to my.captifi.io
2. Go to Integrations and click Configure on the Twilio card
3. For each venue you want to enable, enter your Twilio credentials (Account SID, auth token, and the Twilio phone number messages send from)
4. Use Test connection — you'll be asked for a number to send a test message to
5. Toggle the venue to Enabled and click Save

You'll need a Twilio account; message costs are billed by Twilio at their standard rates — CaptiFi adds no markup.

How It Works

• A guest connects and provides their phone number on your splash page (enable the phone field in the sign-in form section)
• They receive your welcome SMS automatically
• Messages are de-duplicated over 24 hours, so a guest reconnecting won't be texted twice
• Only guests who opted in are messaged

Staff SMS Alerts

Get a text when something needs attention — an access point going offline, or a portal issue at your venue.

Staff alert preferences are currently managed in the classic dashboard: log in at app.captifi.io and go to Account Settings → the Notifications tab. You'll need an account with a supported SMS gateway (we use ClickSend — contact support and we'll help you get set up), your gateway API credentials, and the phone number alerts should go to (with country code, e.g. +447700900000).

Alert types include server/infrastructure alerts, access point up/down alerts, and portal URL monitoring.

Email alerts

The same events can alert you by email at no cost — configured on the same Notifications tab. Start there, and add SMS for the venues where you need to know immediately.

Troubleshooting

Issue	Possible Cause	Solution
Welcome SMS not sending	Twilio not enabled for the venue	Check the venue toggle in the Twilio integration config
Welcome SMS not sending	Guest didn't provide a number or opt in	Enable the phone field on your splash page; consent is required
Test message fails	Wrong Twilio credentials	Re-check the SID/token/from-number against your Twilio console
Guest texted only once	24-hour de-duplication	Expected behaviour — prevents spam on reconnects
Staff alerts not arriving	Number format or gateway credentials	Include the country code; verify credentials with your SMS gateway

Related Features

• Integrations Hub — where Twilio is configured
• Splash Page Builder — enable phone number collection
• Access Points — the hardware behind AP alerts