Your event

Ticket requests

Collect people who'd like to come, then decide who does.

You share a request form's link, read what comes in, and approve the ones you want. Asking commits nobody to anything. Your event page says nothing about requests, so you choose who gets the link.

Where it appears in your sidebar

Ticket requests arrives in the sidebar the moment you make your first request form. To have it there before then, ask for it on the Features panel under Settings.

To stop taking requests, give the form a closing date. It closes on its own, and your other forms carry on.

One event, several forms

An event can have several request forms, each with its own ticket types, questions, closing date and link.

Three ways to decide

You choose one when you make the form.

• You review each one. Requests wait for you, and you approve or turn down each one whenever you like.
• A random draw, for when more people ask than you have places. You can give a place outright to anyone who's earned one, then draw at random on whoever's left. Everybody not drawn stays on your reserve, so you can draw again when invitations go unclaimed.
• It runs if enough people ask. Set a number and a deadline. Hitting the number gives you a button to press.

The choice is fixed once somebody has asked.

How people pay

A form offering a paid ticket type asks how people pay, in the Paying section of the setup form.

• Send an invitation when you approve. They get the ordinary Tito invitation, with no card asked for on the request form. They claim their place, and pay at that point if it costs anything.
• Take card details when they ask. The person leaves a card without being charged. Approving charges it and emails the ticket straight away.

A form where everything is free says so instead of asking.

This choice is fixed once somebody has asked, the same as the way the form decides.

Approving

On a form that sends invitations, approving somebody sends them the ordinary Tito invitation. On a free ticket type they claim their place. On a paid one they pay when they claim it.

On a form that takes card details, approving charges the saved card there and then and emails the ticket. Either way the approve button says what will happen before you press it.

Anything set to Included on the ticket type comes with it, free, one for each place you approve.

You can approve somebody for fewer places than they asked for, or for a different ticket type that form offers. They're told what they're getting.

Turning somebody down is silent unless you switch that form's rejection email on. It starts off.

Either way, somebody who asked can see where they stand on the page they landed on afterwards. It says whether they've got a place, and where to look for their invitation or ticket. Their confirmation email links to that page.

Deciding a lot of people at once

A ballot and a "runs if enough people ask" form both settle everybody in one press. A confirm step first shows the email everybody is about to get. On a form that takes card details, that step counts cards and money instead, and says how much is about to be charged to people's cards.

One press decides everybody at once, then takes the money card by card in the background. Cards that refuse are handled the same as when you approve one person at a time, and nobody loses their place over it. Filter the list by Card failed to see everybody worth chasing.

Changing their mind

Somebody who asks can take it back, from the page they landed on afterwards. Their request then shows on your list as Withdrawn, and drops out of your waiting count, out of a ballot, and out of the number a "runs if enough people ask" form is counting towards.

They can do it until you answer them. Once you've approved or turned somebody down, the link goes. They can ask again while the form is still open.

Good to know

• Each person's own page keeps an Activity list: what they asked for, what you decided, and what their card did, each with who did it and when.
• The questions a request form asks are your event's own questions, the same ones your booking form and ticket types use. An answer given on a request follows the invitation, so it ends up on the attendee and in your exports.
• Turning somebody down deletes their card, and the rejection email tells them so. The same happens when you finish a form off and turn down everybody still waiting.
• You can change every word people read. Open Customize and rewrite them on the Words tab. Request form and Request sent are steps in the journey, and Withdraw request is under More screens. The closing date, the person's name and the number of places come through as {date}, {name} and {count}, so you can put them anywhere in your own sentence.