Registration questions
Registration questions turn a checkout into a registration: dietary requirements, company and job title, session choices, consent boxes — asked at exactly the right moment, and required before payment.
Where to find it: questions live organiser-wide under Audience → Registration questions; you arrange them into steps by opening your event, then Registration in the sidebar.
Building the questions

- Questions live in a shared library (Audience → Registration questions, organiser-wide), so “Dietary requirements” is written once and reused across events.
- Thirteen field types cover the usual ground: short and long text, number, yes/no switch, single and multiple choice (dropdown, radio or checkboxes), date, email, phone, web address and country.
- Each event arranges questions into steps — pages of the wizard the buyer walks through.
- A question applies per order (billing contact, heard-about-us) or per ticket (each attendee’s name-badge details), and can target specific ticket types — the VIP dinner question only appears when a VIP ticket is in the basket.
- Conditional questions appear based on earlier answers — “Which allergy?” only after “Yes”.
- A live preview in the console shows the wizard exactly as buyers will see it.
What buyers experience
After choosing tickets, the buyer walks the steps you built. Only questions relevant to their basket appear, and every required question must be answered before payment unlocks — an incomplete registration can’t become a sale. Answers save when the order completes, not as they type — the wizard is kept short so that’s never a burden, and a buyer who wanders off mid-form hasn’t left half an answer set behind.
Where answers end up
Checkout answers attach to the order, visible in the console on the order record and in exports; the company-name answer also prints on badges.
Guest details, after booking
The same questions can be answered per guest once the tickets exist. A guest opens their own ticket link and finds “Your details”; a host answers for everyone they booked from the order page (Edit attendee on each ticket); your team adds what a guest phoned in from the Attendees page. A complimentary ticket’s invitation asks for dietary and access needs, because nobody on a guest list ever sees the checkout. The buyer’s own checkout answers stand in for the buyer’s own ticket — never for a guest named on their address, whose details stay blank until the guest or the host fills them in.
Choosing when a question is asked
Each question has a When to ask setting. The default, at checkout and on the ticket, asks it in the wizard and again from each guest’s ticket if it is still unanswered. At checkout only asks it once per order, of whoever books, and never shows it on a ticket. After booking, on the ticket skips the wizard altogether: each guest answers from their own ticket link, the invitation and the details reminder ask for it, and it never holds up payment. An event whose every question is asked after booking has no registration step at checkout at all — the right choice for a dinner where one person books a table and the dietary and access needs are each guest’s own.
On the Attendees page, Show details adds a column per question beside each guest’s seat, No details yet lists the guests you have heard nothing from, and the export carries the same columns — the list the caterer and front of house actually want. The Reports page counts the answers per question and per table, and a reminder step set to “only guests missing details” chases the rest for you before the night.
