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
- All: Show everyone
- Verified only: Show only validated tickets
- Unverified only: Show tickets not yet validated
Export
Click Export to download the list as CSV or Excel. Includes all visible columns.
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
Common uses:
- Check-in lists for manual backup
- 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
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.
Export the assistants list — each row includes the ticket ID. These IDs are what's encoded in the QR codes. You can share this list with external validation systems or create your own QR codes from these IDs.
The Phone column only has data if you configured your event to request phone at checkout. If when you created the event (or later in Edit → Checkout configuration) you did NOT enable the "Phone" field in Buyer data fields, buyers didn't have to provide it and therefore you don't have that data.
For future purchases: enable "Phone" in checkout configuration. For past purchases: there's no way to retrieve data you didn't request.
The same applies to Birthdate.