Tickets
Every person gets a scannable ticket. A ticket never changes after it is issued — fixing one means voiding it and issuing a new one, so the gate is never guessing.
A ticket is one person, one or more days, one code. Codes are issued once and never edited: if a day changes or a name is wrong, the old ticket is voided and a new one issued in the same transaction, and the old code scans as "replaced — see new ticket". That rule is what lets a phone with no signal trust its own copy of the roster.
Step by step
- 1
Choose when tickets go out
Events → Schedules → Ticket delivery. The template sets a default (often 3 days before day one). Move it, or set immediately on registration for events with walk-ins. Ticket delivery is a core schedule — included on every plan and never paused.
Confirmation and ticket delivery are included on every plan. - 2
What the ticket looks like
The email carries a link to the ticket page: the person's name, their days, the venue, the code and a QR. One email can carry every ticket in a household. The page works offline once opened and offers Add to Apple Wallet / Save to Google Wallet when wallet tickets are turned on.
The same QR on the email, the wallet and the printed sheet. - 3
Print for people without email
Anyone registered without an email is put on the print track. Events → Badge runs builds a print sheet (or badges) for a group or the whole event, in the order you choose. Hand them out at the group; they scan exactly like a phone ticket. Nobody is second-class for not having an inbox.
A print run per group, sorted by household so families stay together. - 4
When something changes
Every change goes through void and reissue, in one step:
- Day change — new ticket for the new day; the old one scans "wrong day → replaced".
- Transfer — the new person gets fresh codes; the old ones name the replacement.
- Cancel — the ticket voids; the place is given back.
A Google Wallet ticket goes inactive automatically. An Apple Wallet ticket keeps its old code, so the gate says "replaced" and names the new one — the person is still found in seconds.
An old code never silently works — and never leaves someone stranded. - 5
Resend, and the self-service page
Lost ticket? The person opens My registration (the link in their confirmation) and resends it themselves. From the admin, Attendees → person → Resend ticket. Every send is on the Sent messages page with delivery status.
Registrants fix things themselves. You get fewer emails.
When you are done
What should be true now
- Ticket delivery timing is what you want, in the event's time zone.
- A test ticket opened on a phone, scanned, and the print sheet built.
- You know where to resend from (and so do your registrants).
- You have decided whether wallet tickets are on.