Checkout flow

How the registration flow works in Tito

Doc Parsons avatar
Written by Doc Parsons
Updated over a week ago

Our goal is to create the best user experience possible for both our customers (event organisers) and your customers (event attendees). If we’re not providing the fastest and simplest method for a customer to secure a ticket, we’re doing it wrong. So we’ve designed Tito's checkout flow to be a little different from most registration platforms.

Minimal information required by default

To make our forms super friendly for all types of user, we only ever ask for the minimum amount of information required to complete the transaction. For a free ticket this is just two fields: name and email. Attendees can optionally also add a company name.

If enabled by the organiser, we also display a data privacy checkbox. And for paid tickets, we obviously also include credit card fields.

Collecting additional information at order level

Under Settings > Payment / register form, there are a few options to customise this form with additional fields and make them required or optional, including:

  • VAT number

  • Billing address

  • Phone number

  • Job title

  • Purchase order number

Information collected at this stage will only be associated with the Order, rather than individual Attendees. The data can be downloaded from Orders > Export

Collecting additional information at attendee level

You can add custom questions for the individual attendees to fill in during the assign stage. This could include things like dietary and access requirements.

What happens next?

Once a registration has been made successfully — whether free or paid — a few things can happen, depending on the nature of the order.

Single ticket with no custom questions

If only one ticket has been registered and there are no additional custom questions to answer, we auto-assign the ticket to the purchaser. We also send them an email that includes a link to view their Order and ticket details.

For multi-ticket orders

If an order contains multiple tickets, we send the purchaser an order confirmation email and prompt them on-screen to assign their tickets.

Screenshot of the dialogue box prompting the purchaser to assign their tickets.

The purchaser can choose to: 1) assign the ticket to themselves, 2) assign the ticket to someone else, or 3) come back later to assign the ticket. We provide this last option because the purchaser might not yet know who the ticket will be for.

If they choose the to assign the ticket to someone else, they'll be prompted to enter the recipient's name and email address. Upon saving, Tito will send a confirmation email to the ticketholder, prompting them to complete their ticket by answering any custom questions if required.

What to do about unassigned tickets

Unassigned tickets can be easily identified and managed. You can use our Messages tool contact purchasers who have unassigned tickets and ask them to provide details for the ticket holder. See instructions here.

For tickets with custom questions

Once a ticket is assigned (either to the purchaser or a third party), they'll be shown a form to submit their answers to any custom questions the organiser has attached to the ticket. They can choose to fill this in later, and their ticket will be marked Incomplete in the admin dashboard until all required questions have been answered.

What to do about incomplete tickets

Incomplete tickets can be easily identified and managed. You can use our Messages tool contact attendees who have incomplete tickets and ask them to submit their answers. See instructions here.

If you're interested in reading about the philosophy behind our approach, check out this blog post from all the way back in 2014.

Still need help? Search our FAQs for instant answers. You can also leave a message for our support team by email or in-app, and we'll get back to you by the next working day.

Did this answer your question?