Tickets and check-in
Follow a free sample ticket from an event to the wallet, then rehearse authorized staff validation results.
Illustrated sample. No messages sent, payments taken or account changes made.
Sample workspace1 / 6Ready to play.
Synthetic / attendee
Community Open House
Synthetic free ticket. No order, usable code, or real check-in.
Synthetic / attendee
Attendee / ticket wallet
Sample / not valid for entry
Community Open House
Wallet details
Opened, not redeemed.
Synthetic free ticket. No order, usable code, or real check-in.
Synthetic / authorized staff
Staff / manual validation
Event scanner
Manual entry
Validate ticket
Synthetic free ticket. No order, usable code, or real check-in.
Synthetic / authorized staff
Staff / validation result
Simulated result
VALIDAdmit guest
No real redemption.
Admission details
Synthetic free ticket. No order, usable code, or real check-in.
Synthetic / authorized staff
Staff / repeat validation
Simulated result
ALREADY USEDCheck before admitting
Prior sample check-in: 2:05 pm.
Admission details
Synthetic free ticket. No order, usable code, or real check-in.
Synthetic / authorized staff
Staff / unmatched example
Simulated result
INVALIDDo not admit
No sample match. Refer to the event lead.
Resolution
Synthetic free ticket. No order, usable code, or real check-in.
Your next step
Start with a practice lesson or use your own details.
Read the complete walkthrough
Review the event and ticket
An attendee starts on the public event page and reviews the date, venue, and ticket type. This fictional Community Open House uses a free sample ticket; no checkout or order is created.
Open the sample ticket wallet
The attendee wallet keeps event details and pass access together. Opening a pass does not check in a guest. This sample deliberately replaces the live QR and fallback code with a non-scannable placeholder.
Hand off to authorized staff
Only authorized staff use the event scanner. Select the correct event and use manual entry when needed. The real Validate ticket action can redeem a ticket; this rehearsal has no camera, code, or request.
VALID: admit the guest
A successful first validation returns VALID - Admit guest. Staff check the event and admission details before entry. Only the synthetic example changes to Checked in; no ticket is redeemed.
ALREADY USED: pause admission
Repeating the sample produces ALREADY USED - Check before admitting. Review the previous check-in and ask the event lead to resolve a dispute; do not treat a repeated ticket as a second admission.
INVALID: resolve at the help desk
An unmatched sample returns INVALID - Do not admit. Staff check the event and the attendee's original pass or refer them to the event lead. Do not invent a code or override the result.