Your event

Questions

One account-wide library of the questions people answer when they register.

A question written once can be asked on any event you run. Questions are what people answer themselves, at checkout or when a ticket is assigned to them.

Anything you fill in yourself, like a seat number on somebody's ticket or a note only your team reads, is metadata. So is a Wi-Fi password or a hashtag about the event. Both live at Settings → Metadata. See Add a field about your event or its attendees.

An organization's name, address and VAT number for the invoice are asked at checkout, under Who you sell to at Settings → Checkout. See Checkout.

With no questions in your account yet, the list offers six of ours, among them job title and organization. Selecting one adds it to your library, ready to ask.

The list opens with when attendees answer. A question's own row can't say this: it reads the same whether the event asks during checkout or after the order is confirmed. Change opens that setting in a panel over the list, so you can change it without leaving the page.

Filter opens on Used on this event, which is what this event asks plus any question no event asks yet, so a question you've just written is in the list when you come back to it.

All questions is everything in the library, and archived is what you've retired. Each of those two appears once there's something in it.

Descriptions support links written as [link text](https://example.com) and bold text written as **bold text**. These also work in descriptions imported from Tito Pro.

Good to know

• A question is asked nowhere until you put it somewhere. Where it’s asked on the question's own page is the list of everywhere that asks it. See Choose who answers a question.
• Reorder sets the order for the whole account, and every place that asks the questions follows it, on every event. A ticket type, a request form and a waitlist can have an order of their own instead: arrange them where you choose their questions. The order form and portals always follow the account's order.
• A question on the order form can be limited to orders that include certain ticket types. See Ask a booking question only for some tickets.

Conditional questions

Open the parent question’s Edit form and switch on Show additional questions based on the responses to this one.

Choose a response under When and select follow-ups under Then.

To ask a question that doesn't exist yet, open Add a new question under the list. Write the question, choose its type, and switch on Required if they have to answer it. Add puts it in the list, ticked, and saving the parent creates it.

A new follow-up is asked wherever the parent is asked. To leave it off one ticket type, open its menu on that ticket type and choose Stop asking it here. It keeps being asked everywhere else the parent is, including ticket types you add later. Add it back to that ticket type to ask it there again.

On a portal, select Manage under Ask them for details and set the follow-up to Don’t ask.

What When asks for depends on the question:

• Yes/no and single choice: pick the response.
• Text: choose is exactly or contains. Matching ignores capitalization and surrounding spaces.
• Multiple choice: choose matches any of these or includes all of these.

Add a condition asks a different set of questions for another response. On a yes/no or single-choice question the responses run out, and the button goes once every one of them has a condition.

Remove this condition takes one away. The last condition stays. To stop asking the follow-ups altogether, switch the flow off. The questions stay in your library either way.

Follow-ups are added alongside the parent on this event’s forms, including applications and portals. If several conditions match, their questions appear once each. Hidden follow-ups are not required, and their old answers are cleared when the form is submitted.

API

You can reorder questions through the API, across the account or on one event form, including the order form and a portal.