Post-purchase support
Find the buyer, open the relevant order and check its status. This helps you explain whether payment was completed and which ticket relates to the enquiry.
Customer contact details, order history, tickets, and registration answers are available in your dashboard. Handle enquiries, prepare attendee lists, and see who has bought tickets before—all without piecing information together from different conversations.
Use purchase history to handle specific enquiries and prepare for your event.
Find the buyer, open the relevant order and check its status. This helps you explain whether payment was completed and which ticket relates to the enquiry.
The list for a specific event brings together contact details and form responses. Prepare materials or follow up about attendance without manually copying information from orders.
Order counts and history help you see whether someone has bought before. Use this context when communicating, without assuming interests the buyer hasn’t shared.
Use it to find a person and review their order history. It brings together interactions with your events, but does not create a separate profile for each guest in a group purchase.
This list focuses on tickets, registration responses and check-in. Search and the “checked in / not checked in” filters help you prepare for an event and review attendance; if only part of a group checked in, check the tickets individually.
CSV and XLSX let you share the relevant data with a team member or use it in your own workflow. The file is a snapshot of the data at the time of export: new purchases and check-ins do not update the downloaded copy.
Set up your event form and explain which fields attendees need to fill in. The quality of your database depends on the information provided during checkout.
Search using the customer’s details or order number. Open their record and check the event, date, number of tickets, and payment status before taking any action.
Use CSV for a general customer list; for attendees of a specific event, use XLSX with registration answers and check-in statuses. Before exporting, check the filters and the recipient’s needs.
Staff know which details to ask for to find the right order.
The general buyer database does not replace the attendee list for a specific event.
Select the right filters and event, and make sure you are using the latest data.
Search orders by name, email or phone number, and filter by event, status or date range. Check a few details before sending a ticket or discussing the order, especially if names match.
Available contact details, order and ticket history. The main list also shows the number of orders and the dates of the first and most recent orders. This helps you review interactions related to sales through the platform.
The main buyer list is available in CSV. Attendees for a specific event can be exported in XLSX, including contact details, registration responses and check-in status; the export reflects the selected filters. These are separate lists, so choose the one that fits your task.
The row refers to the buyer. The “checked in” status means all of their trackable tickets have been used. If only part of the group attended, check the individual tickets and check-in history for details.
This feature focuses on buyers, their orders and tickets, and event attendees. Custom lead pipelines and interest-based segmentation are not part of the described use case. If you need your own CRM, first define the data and integration process using the available API.
Create an event and manage orders, tickets and attendees together in your account.