Your event

Registration

When registration closes for this event, when you ask your questions, and whether buyers can save a quote.

Registration holds three decisions about taking orders for this event: when it closes, when attendees are asked to fill things in, and whether a buyer can save a priced quote instead of paying now.

When registration closes

When to close registration sets when this event closes. Individual tickets and items can close earlier than this, or stay open later. There are three answers.

When the event ends closes registration at the event's end time, or at its start when there is no end date. It follows whatever the dates on General say.

Never, registration stays open means no end date is set.

On a date I choose opens a date field. What you set there stays put, whatever the event's dates do afterwards.

Questions and names

When attendees answer your questions and say who each ticket is for has two answers: during checkout, or after the order is confirmed. Asking after payment gets more orders finished. Asking before means you have the answers by the time they pay.

A question you attached to an Item or a Session is asked during checkout whichever you pick, so a t-shirt size is always asked while the buyer is choosing it.

New events ask after the order is confirmed. Events you set up before this keep whatever they were on, and you can change either way at any time.

Names and email addresses

Every ticket needs a name means whoever orders has to name each person before the order is finished. Every ticket needs an email address does the same for addresses, and each person then gets their own ticket by email so they can answer their own questions.

Printing badges needs names and no addresses. Sending everybody their own ticket needs addresses whether or not the badge matters.

Both start off. With both off, a name box only appears where you ask attendees something, so an event that asks nothing per attendee collects no names unless you turn one of these on.

Anonymous ticket types collect no name at all, so they are never affected.

Who answers each attendee's questions

Whoever orders gives a name and an email for each ticket, and fills in whatever they already know. Anything they leave blank is asked of the person on the ticket when it's sent. There is nothing for the booker to choose: a filled box is their answer, an empty one is a question for the attendee.

Other people's questions start folded away on each ticket, behind Answer their questions now. A booker who knows an answer opens the fold and gives it. The booker's own questions are always in the open, because nobody asks them again afterwards.

A question you marked as required is only required of the person being asked. The booker's own ticket is the one they have to finish. On everybody else's, a blank is the booker handing the question over.

A ticket named without an email address is not sent, and its row says Needs an email until one is added. If you would rather that never happened, turn on the setting above that asks for an address on every ticket.

What saving sends

Saving emails each newly named person their own ticket, and the line above the button names who is about to get one before you press it.

That email has a link to their own ticket page. If anything is still outstanding it asks them to complete their details. If nothing is, it's their ticket. Either way the ticket page has an edit link, so somebody who was emailed before you added a question can still answer it.

Each ticket is emailed once, and coming back to change an answer sends nothing new. Give a ticket to somebody else, or correct the address, and the new address gets its own email.

The booker is never emailed a ticket separately. Their order confirmation is already their ticket.

Rows that have been sent say Sent.

Seeing what is still outstanding

The order page lists every ticket in the order. On an event that asks something about the people going, a ticket nobody has named yet says Needs a name. Once it has a name, the row says how many questions on it are still unanswered, so a booker can see what is left without opening anything.

On an event that asks nothing about attendees and does not insist on a name, none of that appears. A link under the list, Add names to these tickets, opens the same form for a booker who wants names on their tickets anyway. Naming somebody there emails them their own ticket, exactly as it does everywhere else.

Each attendee sees the same count on their own ticket page, with a button that takes them to the questions. It counts every question you ask about a person, whether or not you marked it required, and it disappears once they are all answered.

When attendees get their code

When attendees get their code decides when the code that gets somebody through the door appears on their ticket page.

Once somebody is named on the ticket is where new events start. The code appears the moment the ticket has a person on it, and any questions can follow.

Once the ticket is finished waits for every required question too. Somebody who never answers a question arrives at your door with no code.

Straight away is how events worked before this setting, and events you set up before it stay on it.

Whatever you pick, the ticket page says a code is coming, and the reference is always there. Anonymous and canceled tickets are never held back.

This setting governs the ticket PAGE. The ticket email has the code whichever way you set it, so it still works at a door with no signal. When a ticket still has an unanswered question on it, the email says so above the code and offers a link to the questions.

Quotes

Allow quotes instead of paying lets a buyer download a priced quote before ordering, then convert it to an order when they're ready. A quote reserves nothing, and availability is checked when it's converted.

Where buyers can ask for a quote lists every page that can offer one: your event page, and each audience landing page. Tick the ones that should offer it. Untick them all and nobody can ask for a quote.