Walk-ins are visitors nobody invited. They register themselves at the kiosk, so they take longer and need more care.
When you need this
Your kiosk accepts walk-ins (switched on by default) and you want them to go smoothly.
What happens before a host hears about it
- Where your administrator has switched on Enable OTP Verification for the kiosk (off by default), the visitor proves their email or mobile number with a code.
- The visitor is checked against the Watchlist. A match refuses the walk-in on the spot and no visit is created; the kiosk is told it is a watchlist refusal, but not the entry’s reason.
- Where Require Host Approval for Self/Walk-in Check-in is on (off by default), the host is asked to approve: first on the EvTrack mobile app, and by email (Email Host Approval, on by default). If nobody answers within the Host Approval Timeout (two minutes by default), the request times out and no visit is created.
| Risk | What to do |
|---|---|
| The host does not see the request in time | Tell hosts that walk-in requests expire; keep their app notifications on |
| The visitor picks the wrong host | The kiosk lists every enabled user; reception can help at the kiosk, and clear user names help everyone |
| A queue forms at busy times | Ask regular visitors to register in advance; a walk-in takes several screens |
| A refused visitor argues at reception | The kiosk is not given the entry’s reason; security handles the conversation, and the record is in the Logbook |
Where to do it
- Journey: A Walk-in at the Kiosk
- Kiosk settings and Host Approval
- Walk-ins registered at the desk instead: Walk-in Registration