Help an attendee without a usable QR code
Read the guide →Guide preview
Use the authorized lookup route and event policy; a missing phone display is not automatically a missing ticket.
Resolve ordinary arrivals consistently and hand uncertain cases to the right person. Keep ticket status, event policy and payment decisions separate.
Resolve ordinary arrivals consistently and hand uncertain cases to the right person. Keep ticket status, event policy and payment decisions separate.
New to the topic? Begin with the first guide. Otherwise, go straight to the question you need to answer.
Use the authorized lookup route and event policy; a missing phone display is not automatically a missing ticket.
An error describes the current check; investigate the context without overriding the event’s rules.
Investigate the recorded action and the event’s re-entry policy before changing a ticket’s status.
A valid purchase for another occurrence does not automatically authorize entry now.
Confirm the present tickets before using an all-order action.
Give uncertain cases a named owner, a minimum handoff and a clear return instruction.
Software can record changes of status; the organizer decides whether and how re-entry is permitted.
If ticket records can change during admission, define how each entrance learns about the change.
Check device, processor, permissions and payment confirmation separately from the ability to scan a ticket.