Attendees use EventOxygen. Your staff run the door from Appmint Mobile, and you set the event up in Studio Manager → Events.
EventOxygen shows the attendee's QR; it has no scanner of its own. Ticket scanning, verify-scan, check-out and credential assignment happen in Appmint Mobile — open the event there and use the Scanner tab of the event shell. See Events and scanning and, for the screen-by-screen operator guide, Event-day operations.
Before the doors open
1. Publish the event so it is discoverable and tickets can sell.
2. Set the event live when it starts. This turns on the door-side features.
3. Brief staff on which zones they scan for. Accreditation is per zone — a scanner set to the wrong zone turns away valid attendees.
4. Check the venue network at the door. Scanning cannot work offline. Test where staff will actually stand, not at reception.
5. Pre-generate badges if you are printing, and confirm the printer is reachable through the Device Hub.
Checking people in
Staff scan the attendee's QR. The scan validates the ticket, records the check-in against a zone, and logs which device did it.
Check-out is recorded too. That is what makes occupancy a live count per zone rather than a cumulative total of everyone who ever walked in — the number that matters when you have a capacity limit.
Validation asks the server whether the ticket has already been used at another door. It cannot be decided on the device, so a scanner with no signal will wait rather than accept. Plan network coverage at every entrance.
Will-call
For people who bought but never opened the app: look them up by email or booking id on the Accreditation Desk and fulfill their ticket from the staff app. They do not need to install anything.
Accreditation and credentials
Zone-based access decides who may enter where. Every scan is logged with its device, so you have an audit trail rather than a headcount.
For physical credentials — wristbands, RFID cards — import the range of pre-printed codes ahead of time, then assign them to attendees on arrival. A lost credential is revoked individually without affecting the ticket.
Badges
Generate a badge from a template and print it through the Device Hub. Once printed, the badge is marked as such, so a second cannot be issued against the same ticket.
Perks
Drink tokens, meal vouchers and merchandise are claimed by the attendee and fulfilled by staff — two separate steps, so both halves are recorded and the count reconciles at the end of the day.
Leads
Leads live in the Appmint Mobile CRM pipeline, where an exhibitor adds them by hand with source event. Scan-to-lead from a badge is not in the app or the events API today — see Event-day operations → Leads.
Watching it run
The live dashboard shows check-in statistics, occupancy per zone and attendee counts, so whoever is running the door is not waiting on someone at a laptop.
Troubleshooting
"Ticket already used." It was scanned elsewhere, or someone forwarded a screenshot. The check-in record shows which device scanned it and when.
An attendee cannot find their ticket. Almost always an email mismatch — they bought with one address and signed in with another. Reassign the ticket to the address they actually use.
Scanning is slow at one entrance. Network coverage, not the app. Compare against a door that works.
Someone needs a ticket transferred at the door. Assign it to their email; they receive a new QR immediately. The original stops working, so there is no risk of both being used.
Badges will not print. Check the Device Hub is connected and the printer is assigned. See Device Hub troubleshooting.