Access
Design the guest access flow around the existing network environment.
Helios can connect the guest access layer with property context, consent and available guest signals so network entry can continue into a useful, personalised digital journey.
The exact implementation depends on the existing Wi-Fi stack, RADIUS or captive portal capabilities. Compatibility is confirmed before an integration scope is agreed.
Design the guest access flow around the existing network environment.
Capture consent and privacy choices before optional analytics or marketing signals are used.
After connection, guests can continue into relevant services, offers or the My Stay experience.
The exact flow is configured around the property operation, permissions and confirmed integrations.
The guest selects the hotel's network.
The configured network flow handles access, terms and any required identity information.
Optional analytics and marketing permissions are requested according to the agreed privacy model.
Where legally and technically available, context can connect to the relevant experience.
The guest continues into services, information or campaigns relevant to the property.
Adaptation to the access method supported by the infrastructure.
Used only where the existing network stack and agreed architecture support it.
Separate necessary, analytics and marketing choices where applicable.
Relevant landing, service discovery or campaign experience after network access.
Connect and continue into a useful experience without irrelevant steps.
Use only permitted first-party signals for relevant journeys.
Keep technical boundaries and integration ownership clear.
The discussion covers captive portal, RADIUS, consent requirements and the desired post-login journey.