Event assistants
The Assistants tab shows a complete list of all ticket holders for your event. Each row represents one ticket (not one purchase — a purchase with 3 tickets creates 3 rows).
Table features
Search
Search by email, name, or ID number.
Filters
The only filters available on this tab are by verification status:
- All: Show everyone
- Verified only: Show only validated tickets
- Unverified only: Show tickets not yet validated
There is no filter by ticket type in the table. You can't filter by VIP, General, free, etc. from the UI. To see validations broken down by ticket type, export the list (the file includes a Ticket Type column) and filter or group in Excel/Google Sheets.
Export
Click Export to download the list as CSV or Excel. Includes all visible columns, plus Ticket Type and verification status (even though those aren't filterable on screen).
Table columns
| Column | Description |
|---|---|
| User | Name, last name, and email (always present) |
| ID | Identification number (always required) |
| Phone | Phone number (only if you enabled "Phone" in Checkout configuration for the event) |
| Birthdate | Birthdate (only if you enabled "Birthdate" in Checkout configuration for the event) |
| Verified | Validation status with timestamp if verified |
| Actions | Edit assistant |
Note: If you see empty Phone or Birthdate columns, it's because you didn't configure your event to request them. To configure these fields, go to your event → Edit → Checkout configuration → Buyer data fields.
RSVP columns
If your event has RSVP questions, additional columns appear showing each attendee's answers.
Actions
Edit assistant
Modify the ticket holder's information:
- Name, last name
- ID number
- Phone
- Birthdate
Use cases:
- Buyer entered incorrect information
- Ticket was transferred to another person
- Typo corrections
Edit answers
Only appears if the event has RSVP questions. Opens a form to edit the attendee's responses.
Use cases:
- Attendee changed their dietary preference
- Incorrect response was submitted
- Updated information needed
Understanding the data
One ticket = one row
A purchase of 4 tickets creates 4 assistant rows. Each attendee appears separately.
Verification status
- Not verified: Ticket holder hasn't entered the event yet
- Verified + timestamp: Shows exactly when the ticket was scanned
RSVP data
RSVP answers are attached to individual tickets, not purchases. If "Ask buyer info per ticket" is enabled, each attendee has their own answers.
Exporting assistant data
The export includes:
- Ticket ID (QR code identifier)
- Verified (Yes/No)
- Verified At (date and time of validation)
- Verified By (name of who validated the ticket)
- Ticket Type
- Name, Last Name, Email
- ID (if enabled in event settings)
- Phone (if enabled in event settings)
- All RSVP question answers
- One row per ticket
⚠️ The "Ticket ID" in the Excel does NOT match the number printed on the ticket — and that's expected. They are two identifiers for different entities:
- Ticket ID (the one exported in the Excel/CSV): the unique identifier of each ticket and exactly what's encoded in the QR code. It's the value scanners/validators use at the door.
- Number printed in the top-right corner of the ticket (
ID: XXXXXXXX): the first 8 characters of the purchase (order) ID, not the ticket ID. It's a quick reference to locate the purchase in the Orders list and the dashboard.Since one purchase can contain several tickets (each with its own
Ticket ID), the number printed on the ticket (which identifies the purchase) and the ID exported in the Excel (which identifies the ticket) represent different things and therefore never match. This is not a bug.
Common uses:
- Check-in lists for manual backup
- Validation breakdown by ticket type (filter Ticket Type + Verified in the spreadsheet)
- Marketing follow-up after the event
- Compliance and record-keeping
- Analyzing attendee demographics
- Sharing ticket IDs with external validation providers
Best practices
Before the event
- Export the list as a backup check-in option
- Review for any missing information
- Contact attendees with incomplete data
During the event
- Use the Verified filter to see who's arrived
- Monitor attendance in real-time
- Cross-reference with validation app
After the event
- Export final list for records
- Use data for feedback campaigns
- Analyze attendance rate (verified vs. total)
FAQs
No. On the Assistants tab you can only filter by verified / unverified (or show everyone). There is no ticket-type filter in the UI.
To see how many tickets of each type were validated (for example, 80 of 100 free tickets), export the list: the file includes Ticket Type and Verified. Then filter or use a pivot table in Excel/Sheets.
Export the assistants list (CSV or Excel). Each row is one ticket and includes Ticket Type plus Verified status. Filter or group by type in the spreadsheet to get the breakdown (validated vs. pending for each type). The dashboard has no native report or filter with that breakdown.
Each ticket is a separate row. If someone bought 3 tickets, they appear 3 times (or their guests appear if different names were provided).
Use Send courtesies to add free tickets, which creates assistant entries.
Click "Edit assistant" and update the name, email, and other details to the new person's information.
No. Entries are tied to tickets. To remove someone, refund or cancel their ticket.
RSVP columns only appear if the event has questions configured. Check Edit → Questions.
Yes. The export includes ticket IDs (the same codes used in QR codes). Download the assistant list, share the ticket IDs with your external provider, and they can use those IDs for validation. When converted to QR codes, they will work with any compatible scanner.
Because they are two identifiers for different entities, and this is the expected behavior:
- The Ticket ID exported in the Excel/CSV is the unique identifier of each ticket and is what's encoded in the QR code (what gets scanned at the door).
- The number printed in the top-right corner of the ticket (
ID: XXXXXXXX) is the first 8 characters of the purchase (order) ID, not the ticket ID. It's just a quick reference to locate the purchase within the Orders list and the dashboard.
A single purchase can contain several tickets, so the number on the ticket (which identifies the purchase) and the ID in the Excel (which identifies the ticket) will never be the same. To cross-reference them, look up the purchase by those first characters in Orders and you'll see all of its tickets with their respective Ticket IDs.