Task · Questions
Choose who answers a question
Ask it of each attendee, of the person booking, or both, and say whether an answer is required.
9 steps · About 3 minutes · Needs: A field in your library
-
Open the question from Questions
Your eventSet upQuestions -
Under Where it’s asked, select Ask it somewhere else
The block lists every place that asks the question. A question you haven't asked anywhere yet says so, and the button under it reads Choose where it’s asked.
go.tito.io/acme/summer-fete/admin/questions/3 -
Tick the places and select Ask it there
Your ticket types, sessions, portals, request forms and the order form itself are all in the panel, minus the ones that already ask it. Search narrows the list, and you can tick as many as you like. They'll all be set to optional, and the next step is where you change that.
-
Set each row to Optional or Required
Optional lets them leave it blank. Required means an answer is needed before the ticket can be bought or claimed.
A pick-one question opens on a blank either way. Set to Optional it opens on No answer, which they can leave. Set to Required it opens on Choose one and they cannot get past the form until they pick.
The ✕ on a row stops that place asking the question. The answers already given are kept.
For a detail you fill in yourself, the rows have no Optional or Required. Attendees are never asked for one, so there's nothing an answer could be required of.There's nothing to save here. Setting an answer, adding a place or taking one off saves it.Requiring an answer applies to bookers only.When you add or edit an attendee yourself, you can leave the answer blank.
A booker answers the questions on their own ticket, and hands over the rest.Where they put somebody else's name and email address on a ticket, that person is asked its questions when we email them their ticket, Required ones included. So a booker can get past the form with those blank, and the answer arrives once the ticket reaches the person it's for.
Asking the person booking
The question's page has a second block under the first, On the order form. It's the one place a question goes to whoever pays rather than to whoever the ticket is for, so it's asked once however many tickets are on the order.
-
Select Ask the person booking
-
Set what it asks, and select Ask the person booking again
Ask only if the order contains: names the ticket types that make an order qualify. Tick none and every order is asked. Show on the invoice prints the answer on the order's invoice, next to the order reference.
It arrives optional. Optional and Required are on the row afterwards, the same way they are for a ticket type you added from the picker.The row's second line reads back what you set.It names the ticket types that make an order qualify, or says every order, and says whether the answer prints on the invoice. The pencil opens it again.
What a place asks, and when
Three more rows have more to set than Optional and Required, and each one carries a pencil.
-
Select the pencil beside the row, set what it holds and select Save
All portals holds the portals the rule asks. Untick one and it stops asking, and the rest carry on. Portals you add later are asked as well.A portal on a document question holds a Deadline. It's the date the document has to be handed in by. Leave it blank and there's no deadline.A session holds Who’s asked this. Everyone who books it, or only the people who pick certain options. See Ask about one workshop.
Starting from a ticket type instead
Every ticket type has a Questions block under its name, listing what that one ticket asks and nothing else. It's the quicker end when you're setting up one ticket rather than one question.
-
Select Add a question
Your library opens with a search box over it. Tick as many as you want and select Add questions. They'll all be set to optional, and you can make any of them required afterwards.
A ticket type asking nothing yet offers a shortcut instead. If your other ticket types all ask the same questions, the block says how many there are and offers Copy questions to this ticket. A new ticket type never inherits questions on its own. Each one arrives set the way the others ask it, and you can change any of them afterwards.On a brand new event, Or start with one of ours is under the block. Before you have written any questions, the block offers six to start from. Selecting one writes it to your library and asks it on this ticket, with its answer choices already translated into every language you sell in. The strip goes once your library has a question in it, and the same suggestions are offered while you type on the new question form.Each row sets to Optional or Required the same way it does on the question's own page.
-
Select the handle icon beside Add a question to change the order
Attendees are asked the questions in the order they're listed here. The icon puts handles and arrows on every row. Drag a row by its handle, or use the up and down arrows. The new order saves as you make it, and it applies to this ticket type alone. Every other ticket type keeps the order your library is in. Select the icon again when you're done.
Write a new question at the foot of the picker makes one that isn't in your library yet. It joins your account's questions, so you can use it on every event you run. See Ask attendees a question for the rest of what a question can be.
The pencil on a row opens that question's wording, description and choices over the ticket, so a typo is fixed without leaving the page. Changes there apply everywhere the question is asked.
The ✕ on a row stops that ticket asking the question. The row is replaced by a line saying so, with how many answers are already in and an Undo beside it. The answers are kept either way. Undo puts the question back where it was, optional or required as it was before.
When the order form asks anything of its own, a line under the list names those questions. They're asked once of whoever books, so they aren't on this list and you can't change them from here. Select one to open it. The buyer's name and email are always collected and never appear there.
Details you fill in yourself are further down the page, in the Recorded details row under Details. The row names what this ticket records. Select it to add one, remove one, or open one to edit. Those rows have no Optional or Required, because attendees are never asked for them. See Metadata.
Starting from a session instead
A session has the same Questions block on its own page, under its options. Open it from Offerings, and Add a question opens the library the same way a ticket type does. Everything you add there is asked of everyone who books the session, whichever option they pick, and the section above is how you narrow one to certain options.
Each row's second line says who it reaches. It reads Everyone who books this is asked, or it names the options that ask it. So the session's page tells you the same thing the question's page does, without opening either.
The handle icon changes the order, the pencil opens the question's wording, and the ✕ stops the session asking it. They all work the way they do on a ticket type.
Good to know
The answers people have already given are kept. On one ticket type, the ✕ beside the row does the same for that ticket alone.
On any event where somebody answered a question you've since set to Don’t ask, it stays in the export column picker and in the report builder's Group by menu, marked switched off. In the export picker it starts unticked, so tick it when you want it in the file.
It's one question with one answer, so a person who's asked it both ways sees one box. If either of the two says the answer is required, it's required.
Fill in both and the question is asked twice over: once for the order, then once for each attendee. On an order of three tickets that's four times. Take it off On the order form if you only want it per person.