How recognition actually works, and why it is visit-based
When a returning guest connects, the portal matches them against an existing guest record and adds a visit rather than creating a new contact. VoqadoWiFi counts one visit per guest per venue per day, so a phone that drops off and rejoins does not count twice. The portal shows a returning guest a welcome back card instead of the form, and on Growth the guest list shows each guest's visits and sorts guests into segments such as returning, regular and VIP that a campaign can be sent to. VoqadoWiFi does not run a points ledger or issue rewards by itself: you decide the reward and send the message. Because the matching happens at connection rather than at the till, this is a footfall loyalty scheme rather than a spend loyalty scheme. It rewards the habit of coming in, which for a coffee shop or a bar is very close to what you actually want to reward.
The identity problem nobody mentions in the sales deck
Device recognition is imperfect and you should design around that honestly. Modern phones randomise their MAC address per network, which is why identity has to hang off the login rather than off the hardware address. A guest who logs in with the same email each visit is recognisable. A guest who types a different address, uses a different device, or lets a friend join on their phone, is not. Households and couples share visits between devices. The practical consequence is that visit counts are a good signal and a bad audit trail. Build rewards that are generous at the edges rather than schemes where a miscount feels like a broken promise.
Designing tiers people can actually reach
A frequent design mistake is setting the first reward too far away. A guest who needs ten visits before anything happens will never see the scheme exist, because they will have stopped counting by visit three. Front-load it.
- Visit two: a welcome back message that simply acknowledges the return. No offer needed.
- Visit three to five: the first small tangible thank you, ideally something with low marginal cost and high perceived value.
- Visit ten and beyond: the perk that is worth talking about, and the one you are happy to be known for.
- Recency override: a guest who has not returned in months should re-enter the sequence rather than continuing where they stopped.
What the operator sees on a normal Tuesday
In the dashboard the useful view is not the total contact count, it is the split between first-time and returning connections in a given period. That single ratio tells you whether the venue is acquiring or retaining, and it moves for real reasons: a new competitor opens, a menu changes, a member of staff leaves. Loyalty messaging is the lever you pull when the returning share slips, and the ratio is how you find out whether pulling it worked.
Where WiFi loyalty is the wrong tool
If your value depends on basket size rather than visit frequency, a WiFi scheme measures the wrong thing, because it cannot see what anyone spent. If most of your guests never connect, because visits are short or the crowd is not phone-first, the coverage is too thin to be fair. And if you need a legally exact points ledger, the identity limits above will bite. Be honest about which of those apply before you print anything promising a reward.
How to set it up
In order. Skipping a step here is usually why a portal ends up showing a spinner instead of a login screen.
- 1
Get consistent identity at the login
Loyalty depends on the same guest producing the same record. Encourage a stable identifier by keeping the login simple and the returning experience frictionless, so guests do not switch methods between visits.
- 2
Decide what a visit means at your venue
VoqadoWiFi counts one visit per guest per venue per day, so a phone that reconnects after a walk outside does not count twice. Decide whether that matches a visit at your venue, and write down what earns a reward before you promise one.
- 3
Define the tiers and the rewards
Write the ladder down before building it, with the first reward within reach. Cost each tier at its marginal cost rather than its menu price so the scheme survives contact with a busy month.
- 4
Build the messages
One campaign per tier, sent to the matching segment and only to guests who consented to marketing. Campaigns are on Growth and are not live yet; you can write and schedule them now. Keep the wording warm and specific, because generic loyalty copy reads as automated and defeats the point.
- 5
Brief staff on redemption before launch
The scheme fails at the counter, not in the software. Staff need to know what the message looks like, what to accept, and what to do when a guest insists they should have a reward the system did not issue.
Who this suits
The venue types where this job comes up most often, and where the data the portal produces is dense enough to act on.
Run this on your own network first
The Starter plan is free forever: one location, 500 logins a month, a branded splash page and consent logging. Growth is $49 a month and covers up to three locations. Works with TP-Link Omada and Ubiquiti UniFi.
Common questions
Do guests need to download an app?
No, and that is the main reason this approach is worth trying. Recognition happens through the WiFi login the guest was already going to complete. There is nothing to install, nothing to open at the counter, and nothing to lose.
How accurate are the visit counts?
Accurate enough to segment on, not accurate enough to litigate over. Phones randomise hardware addresses, guests switch devices or email addresses, and couples share visits. Treat counts as a strong signal and build rewards that fail generously rather than schemes that feel broken when a count is off by one.
Can loyalty work across several locations?
Yes, provided the guest logs in with the same identity at each site. The Growth plan covers three locations, so a small group can run one recognition scheme across all of them. Larger estates sit on Enterprise.
Can I tie rewards to how much someone spent?
Not from WiFi data alone, because the portal sees connections rather than transactions. If spend-based tiers are essential you would need to join the guest record to point of sale data, which is a bigger integration project than a visit-based scheme and worth scoping separately.
Read next
These jobs share the same plumbing, so operators normally set them up in sequence rather than one at a time.
Measure How Many Customers Actually Come Back
Replace a gut feeling about regulars with a number you can compare month to month.
Win Back Customers Who Stopped Coming In
Notice when a regular quietly stops coming in, and reach them before the habit belongs to somewhere else.
Collect Emails From Your Guest WiFi
Turn the WiFi login that already happens hundreds of times a month into a consented, deliverable email address you own.
Terms used on this page
Related pages