Visitor flows, VIPs and exceptions

Visitor flows, VIPs and exceptions

Q: Does every visitor have to use a kiosk or QR code to get Wi‑Fi? What about VIPs or longer term guests?

A: Not necessarily. The standard flow is kiosk or QR check‑in, but GuestConnect also provides a web portal for authorised staff. Reception or admin staff can:

§  Manually create a visitor record (e.g. for a VIP who won’t use a kiosk)

§  Issue a credential with a suitable duration (e.g. a day, a week, or a board‑meeting cycle)

§  Email the Wi‑Fi details and QR code directly to the VIP

You still maintain traceability and control, without forcing very senior guests through a self‑service kiosk.

 

Q: Can we give contractors or board members a longer‑term key so they’re not reconnecting every day?
A: Yes. You can configure different key durations for different categories of visitors:

§  Day passes for ad‑hoc guests

§  Multi‑week or multi‑month passes for board members and recurring visitors

§  Longer‑term passes for contractors who are on‑site frequently

We work with you to align durations with your security risk tolerance so they’re convenient but still appropriate for your environment.

 

Q: How do we stop front‑desk staff from giving everyone a three‑month pass “because it’s easier”?
A: There are a few controls and patterns you can use:

§  Default behaviours: by default, passes can be configured to last for a day, requiring a conscious choice to extend them.

§  Process and role design: use the visitor management system for routine guests (day passes), and reserve the GuestConnect admin portal for authorised staff who can issue longer‑term passes under policy.

§  Future enhancement: GuestConnect’s design already allows for role‑based controls in the portal (e.g. limit some users to short‑term passes only). Where customers need this, we can align configuration and roadmap accordingly.


    • Related Articles

    • Visitor compliance and behavioural change

      Q: How does GuestConnect help us enforce visitor sign‑in policies? A: GuestConnect tightens the link between sign‑in and Wi‑Fi: § If visitors don’t sign in, they don’t get Wi‑Fi – there’s no alternate shared code to “just give them”. § Staff learn ...
    • Data, logging and investigations

      Q: What logs and reporting does GuestConnect provide? A: GuestConnect provides: § Per‑visitor access history: who was issued which key, for what period, and at which site. § Timestamps aligned with your visitor management system (check‑in and ...
    • Hosting, architecture and operations

      Q: How is our data separated from other customers? A: Each customer receives a dedicated GuestConnect instance, including: § Separate application instance and data store § Independent scaling to match your guest volumes § Shared, centrally maintained ...
    • Multi site, acquisitions and different networks

      Q: We have multiple sites and different network vendors. Can GuestConnect handle that? A: Yes. Each customer gets their own GuestConnect instance, and within that instance: § You can have multiple sites, each mapped to different wireless backends ...
    • Technical depth: APIs, Aruba, ClearPass and network design

      Q: Aruba’s APIs and versions keep changing. How do you keep this working reliably? A: Keeping up with Aruba Central versions and API changes is part of the managed service: § We maintain our own API libraries for Aruba, including handling differences ...