The short answer
On One Ticket, add the questions under Questions at checkout. A dropdown for the role they want (a speaking part, a small part, just watching), a dropdown for dietary needs, and a free-text question for allergies. Mark them required and nobody holds a ticket without answering.
A question can belong to one ticket type, so a Dinner and Show ticket asks about food and a Show Only ticket does not. Answers sit against each order in Orders and in the attendee CSV, which is the casting sheet for the host and the list for the kitchen.
The reminder the day before carries the ticket and the dress code, and the morning-after email says how many came and how many were new.
Which fits your event?
Start from the one requirement that decides it.
| Your main requirement | Start with |
|---|---|
| Eight friends at home with a boxed game | A group chat |
| A dinner theatre night for sixty | Required checkout questions, on One Ticket |
| Dinner tickets and show-only tickets | Questions on the dinner ticket only, on One Ticket |
| A monthly mystery with regulars | A series with one link |
Casting at the door is chaos. Casting from the booking list is a script.
How it works in practice
Nothing here is food safety advice. Ask your venue how it wants allergies reported.
| You ask | You get |
|---|---|
| Which role they want | A casting sheet before the night |
| Dietary needs, required | A complete list for the kitchen |
| Allergies, free text | Room for the answer that matters most |
| Asked of the dinner ticket only | Show-only guests are not asked about food |
| The attendee export | Both lists, by name |
One Ticket for a recurring room
Everything below follows from one decision: a series is one object, not a list of dates.
| Feature | What it does |
|---|---|
| Who keeps coming | Roll call, after every session of a series: who is new, the regulars and who has stopped coming, by name, with an address to write to |
| Subscriptions | One subscription covers every session in a series. Each night's ticket is minted ahead of time |
| Paid out | Every ticket is charged to your own Stripe account. It is paid out to your bank two days after each event, or as it sells on request through One Ticket's trust system |
| Fees | You keep 100% of your ticket price. Buyers pay a small booking fee: a platform tier of 35c to $1.45 a ticket, then 1.5% of the price above $100, plus card processing. On a $25 ticket that is $1.45 all in, so the buyer pays $26.45. Free tickets cost nothing |
| Refund if it changes | Move the date, start time or place after people have booked and every one of them can refund in full, booking fee included, until it starts, whatever your refund policy says. You are warned before you save, and everyone booked is emailed the new details |
| Refund requests | On a case-by-case event the buyer asks from their ticket. You have 3 days to refund or decline; a request nobody answers goes to One Ticket support, and your payouts are held until it is settled |
| Scam protection | Our emails carry none of an organiser's own links or phone numbers, and a new organiser's money is held until after the event |
| Verified tick | On every plan, earned by selling here: 3 past events that sold tickets, 25 tickets, payouts verified, no chargebacks and no ignored refund requests. Checked every hour; a chargeback or an ignored request takes it away at once |
| Your page | Your colours, your title font, your cover. Nobody else's event on it |
| Not included | A marketplace. There is no search page and no audience to sell into; the people are the ones you bring |
Answers to your questions
Can I make a checkout question required?
Yes. A required question must be answered before a ticket can be bought.
Can I ask a question on one ticket type only?
Yes. A question can belong to a single ticket type.
Where do the answers go?
Against each order in Orders, and into the attendee CSV export.