Attendees report
What the attendees report contains: one row per ticket, with the attendee name, email, event, ticket type and check-in status.
What the attendees report contains: one row per ticket, with the attendee name, email, event, ticket type and check-in status.
Checking guests in at the door from a phone: the check-in walkthrough and the states a ticket moves through when it is scanned.
Check people in at the door from your phone by scanning the QR on their ticket email, or searching for the attendee; owners and managers can overrule a failed scan.
What to actually do when a scan comes back Already Used, Refunded, Problem, or won't let you override it. Step-by-step responses for each real scenario at the door.
Everything door staff need to know — the check-in app, what each scan result means, and how to handle problems at the door.
When a ticket's QR code won't scan at the door, the cause is almost always the camera or the image quality, not the ticket itself. Here is how to tell the difference and fix it.
Door-staff links give your team a temporary, event-scoped login to the check-in app. They can scan QR codes and check in attendees — but cannot access your dashboard.
TimbaTicket is built for the latest Chrome, Edge, Firefox and Safari, and for Safari and Chrome on phones — the door check-in screen works from a phone browser.
When a QR code is scanned at the door, the check-in app returns one of several states. Understanding each state helps you handle every scenario at the door.
Check in your first guest: open the event's Check-in screen, scan the QR on the ticket email or find the attendee, and admit them — with the Owner/Manager override for scan failures.