4 March 2026 WeefyBox Team 2 min read
The guest WiFi customer journey, end to end
What should happen from the moment a guest joins the network through to permissioned follow-up and measurable return visits.
A reliable guest WiFi journey has several moving parts, but it should feel simple to the guest and the venue team. Here is the complete flow WeefyBox is designed to support.
1. The guest joins the venue network
The access point detects a new guest and opens the venue's branded portal. The page must be fast, readable on a small captive-browser screen and served from the exact URL configured during hardware setup.
2. The portal explains the exchange
The guest sees the venue name, the information being requested and separate choices for network terms, email and SMS. Optional marketing choices start unticked. Submitting the form creates durable evidence of what the guest selected.
3. The hardware authorises access
WeefyBox completes the vendor-specific handoff or RADIUS exchange. A successful browser form alone is not enough: the hardware must confirm the device is authorised before the session is treated as online.
4. A visit becomes part of the customer view
Trusted connection and accounting signals create visit history without exposing infrastructure secrets in the customer interface. The venue can see whether the guest is new or returning, while tenant boundaries keep each business's data separate.
5. The guest sees a clear connected state
After authorisation, the portal follows the venue's chosen post-login behaviour: a simple connected screen, useful information, a social destination or an approved website. It should never leave the guest watching an indefinite loading state.
6. Follow-up respects the original choice
Campaigns and automations include only guests eligible for the chosen channel. Suppressions and unsubscribes remain authoritative even when an old audience or automation is replayed.
7. The venue measures what happened next
Useful reporting connects portal completion, permission, messages and later visits. That gives the team a clear answer to the question that matters: did the guest relationship lead to a return?
When each boundary is explicit, setup is easier to support and the guest experience stays calm even though the underlying network exchange is technically complex.