EventsCheck-in
Doors open in five minutes. Scan a QR code and somebody is in: badge printing, walk-ins registering themselves, and a log that remembers who did what.
A ticket, a scan, and they are in. The whole of check-in, in three steps.
- It arrives in their emailA QR code, in the confirmation and in your Hub. No app to install, no account to remember.
- You scan itA phone, a laptop or a tablet at the door. Whoever is on the door can scan, including a volunteer you sent a link to, with no account of their own.
- They are inThe record updates itself, the badge queues to print, and the log keeps who scanned it and on what.
Put a tablet at the door. And then go and do something else.
No account, no login: attendees scan themselves in and the badge just prints. It wears your branding, not ours.
- A tablet at the door, running on a link of its own: no account needed
- Scan, or check in by email address (your choice per kiosk)
- Walk-ins register on the spot, with a one-time code if you want one
- Print on demand, so the badge comes out as they arrive
- Your logo, your colours, your wording on the success screen
- Leaving the kiosk screen takes a PIN, so nobody wanders into your event settings
Walk-ins, without a free-for-all. They register; you decide.
Approving turns the walk-in into a normal attendee: a real ticket, on whichever type you choose for the door.
- Kiosk walk-ins land in a queue rather than going straight through
- You approve or reject, and a rejection carries a reason
- Approving issues a real ticket on a type you choose
- Limit which ticket types a kiosk can sell, and hide questions from it
- Allow overselling, or don’t (per kiosk)
- A walk-in you register yourself skips the queue entirely
Badges, three ways. Because events do not agree on how badges should work.
One badge, on scan
Somebody arrives, gets scanned, and their badge prints. That is the whole interaction.
Or the whole run, before doors
Mass-print everyone registered ahead of time and lay them out on a table alphabetically.
And a queue you can watch
What has printed, what is printing, and the reprint somebody asked for after their name came out wrong.
Into the room, not just the building. Per-session scanning, with the walk-ins named.
Every scan is tied to the session it happened in, walk-ins included, so the room’s number is one you can actually explain afterwards.
- Scan people into a session, not just into the building
- A walk-in with no RSVP is recorded as a walk-in, not quietly counted
- Check-out as well as check-in, where you need a room count
- Per-session attendance that survives the day it was taken
Every scan, with who and from what
Check-in is a log that only ever gains rows, not a checkbox on a ticket: nothing is edited and nothing is overwritten. Each row records the person or the kiosk that did the scan, and the kind of device it came from. That is what makes the attendance figure something you can stand behind a week later.
Nothing bad. The second scan is recorded as a second scan. It does not overwrite the first, and it does not throw an error at somebody standing in the queue. The door screen still shows the person once; the history keeps both scans.
Yes. Send them a link and they get the door screen and nothing else. Their scans are recorded against that link, so the log still says who did it.
Check in by email address instead. A kiosk can be set to accept either, and whoever is on the door can always find the person by name in the door list.
That is what it is for. It runs on its own token, it only shows the ticket types you allow it to sell, and getting out of the kiosk screen requires a PIN. Revoke the kiosk from the day-of screen and the tablet stops working.
Every scan records the person or the kiosk that performed it and the kind of device it came from. That is what makes the attendance count trustworthy afterwards.