Manage Ticket Attendees and Check-In

The Attendees page is the operational list of issued tickets for an event. It is useful before doors open, during entry, and after the event when you need to understand who attended, who was stopped, and which tickets need follow-up.

Attendee tools

• Search ticket reference, order reference, buyer, attendee, ticket type, and schedule context.
• Filter by ticket status, ticket type, schedule item, and checked-in state.
• Edit attendee details when corrections are needed.
• Open the dedicated ticket detail page for history, answers, refunds, and actions.
• Manually check in a ticket if you have check-in permission.
• Use selected-row group check-in for visible issued or partially checked-in tickets.
• Export filtered attendees CSV or filtered check-ins CSV.
• Generate a filtered print batch PDF when the team needs paper or offline gate support.

Mobile scanner app

• Use the SmartGig Scanner app for live QR scanning at gates, entrances, box offices, and arrival desks.
• In normal mode, the camera pauses after a scan result so the operator can read the accepted, rejected, duplicate, or override-needed message before choosing Scan next.
• Speed mode is optional and off by default. It lets accepted green scans clear quickly and keeps the camera ready for the next person.
• Duplicate, rejected, wrong-event, already-used, or override-needed tickets still stop on the full result in Speed mode so staff cannot accidentally wave through an exception.
• Use manual lookup when a QR code cannot be scanned. Search the attendee or ticket record, check the details, then use the available check-in action only when the person is eligible.

Common ticket statuses

• Issued: ticket is valid and not yet checked in.
• Checked in: ticket has been used for entry.
• Partially checked in: a reusable or multi-use ticket has been used for some, but not all, allowed entries.
• Transferred: attendee details have changed through a transfer workflow.
• Cancelled: the ticket should not be treated as an ordinary valid entry.
• Voided: the ticket has been invalidated.
• Refunded: the ticket is connected to a refund and should not be accepted as ordinary entry.
• No show: the event passed without an accepted check-in.

Check-in history

The Check-in history page is for troubleshooting scan decisions. It can show accepted and stopped scans, result codes, ticket/order/attendee context, scanner attribution, gate assignment, operator, date filters, and override reasons.

Gate safeguards

• Wrong-event scans should be rejected.
• Duplicate scans should be clearly shown.
• Early or late scans can be blocked or flagged based on entry windows.
• Refunded, voided, cancelled, transferred, expired, and no-show tickets need state-specific handling.
• Already-used tickets should not quietly pass as new entry.
• Accepted overrides require a reason so managers can review the exception later.