Start from the problem, not the feature
Operators arrive here with one of three complaints. These are the playbooks that answer each of them.
Build the list
"I have hundreds of guests a month and no way to contact any of them."
Bring them back
"People come once and I never see them again."
Understand the room
"I am guessing at footfall, dwell time and who my regulars actually are."
What every playbook here assumes
None of these jobs work without the same three foundations underneath them. If any of the three is missing, fix that before choosing a use case.
Supported hardware
VoqadoWiFi runs as an external captive portal on TP-Link Omada and Ubiquiti UniFi. Controller access is required, and the portal domain has to sit in the walled garden.
Hardware integrationsA splash page worth completing
One field, one clear benefit, consent unticked by default, and a layout that survives a narrow in-app browser window with no address bar.
What a splash page isDemonstrable consent
A separate marketing checkbox, plain wording, and a stored record of what was agreed and when. Guests who decline still get WiFi.
How opt-in consent worksOr start from your venue type