Guest list

The Guest list (event sidebar, under Sales) is every ticket holder of the event — paid and complimentary — with who they are, what they hold, where they sit, and whether they've arrived. It's equal parts sales view, door fallback, and the printout the venue asks for.

What's in the list

Each row is a customer:

• Name — the attendee's name where attendee names are collected, the buyer's otherwise;
• Ticket type and seat — Balcony, B‑14 at a glance;
• Paid amount — what that ticket actually cost after phases and discounts;
• Arrival status — checked in (with time) or not arrived.

Expand a row to see the individual tickets that customer holds; the search box finds people by name, email, ticket code, or order reference — whatever fragment the person at the door can offer. The ticket code itself isn't shown in the list — it's an export-only column.

Filters for the two questions that matter

• All / Checked in / Not arrived — during the event, Not arrived is the live no-show list; after doors close it's tomorrow's follow-up list.
• Combined with search: "Novák, not arrived, two seats at table 12" is a three-second lookup.

The door fallback

Phones die, QR codes stay home, printouts smear. When a code can't be scanned, the guest list is the door process:

1. find the guest by name,
2. verify it's them (ID for named-ticket events),
3. hit Admit on their not-yet-arrived ticket.

Each valid, not-yet-arrived ticket carries an Admit action that checks the guest in through the same audited scan path as the console — it respects the ticket's admission mode and lands in the live feed and audit log exactly like a scanned code. It's slower than scanning — which is exactly why it's the fallback, not the plan — but it never fails.

Exporting

The export dialog produces the venue's XLSX/CSV with your choice of columns — leave emails off the door copy, keep seats on it. Exports are audited, and remember the printed list ages from the moment it prints; the live page doesn't.

Related