Getting started

How booking works

The path from the event page to the ticket in their inbox.

The event page

The same event page serves from your own address and, when you allow it, from Tito's shared address. A design you customize shows on your own address, and the shared address always uses the standard design.

Ticket types on sale show with a quantity picker. If the event offers more than one language, a switcher is in the corner, and a language chosen there is remembered for a year.

Choosing quantities and selecting the button under the ticket list sends the whole selection to checkout.

The tickets, times and items a buyer chooses are held for them from that moment, so nobody else can buy them while they fill in their details. The hold lasts 15 minutes, or as long as you set in Hold tickets for in the event's payment settings. When it runs out and nobody else is waiting for what they chose, it's held for them again, for up to two hours. Otherwise, if they haven't started paying, everything they chose goes back on sale, and the order isn't shown in your lists.

Anything with a price goes to Your details before paying, which asks the booker's own name and email, the address the tickets and the receipt go to. If the event asks questions of its own, they appear on this same page, alongside a holder name and email for each ticket of an assignable type.

An event set to collect its questions after payment still asks for the name and email here. A free selection skips this page, because the claim screen asks the same two things.

A Your order list on that page shows what is being bought and what it comes to, with Continue to payment under it.

Payments

Free orders skip payment. The next page asks for the booker's details, and tickets are issued on Confirm.

Anything with a price sends the buyer to pay, either on Stripe's own payment page or on a payment form inside the event page, depending on how you set the event up. The form inside the page keeps a plain button underneath it that goes to Stripe's own payment page for the same order, so a buyer whose browser can't load the form can still pay.

That form shows the same Your order list, with a line for each thing bought and then one for each rate of tax added on top. Tax already in the prices is noted under the total, one line for each rate, as in “Includes €11.55 VAT (13.5%)”. The total on the event page carries the same note, so a buyer can see it with the summary closed. When an order mixes rates, each thing bought names its own, as in “Attendee Ticket (VAT 25%)”. Stripe's own payment page and PayPal always name each item's rate of tax beside its name. Where Stripe offers to charge in the buyer's own currency, the total follows the currency they pick and the lines show what was bought without amounts.

An order that's still unpaid shows what it comes to on its own page, above the button that takes the buyer to pay. That button goes straight to payment when your event takes money one way. When there's more than one, it opens a page to choose from first. An order being paid by bank transfer shows the amount there with the account details to transfer to.

After the order

Every order gets its own page at a private link that the booker and you both have. It needs no account and no sign-in. A line on it confirms a copy is on its way to the booker's email, and offers to fix that address there and then.

Each ticket on the order links to its own page. A paid order has a Download receipt button. An order still waiting for a bank transfer links to its invoice instead.

The receipt has everything an invoice has: its own number, your business details, the issue date, the date of the event it covers, the tax charged on each rate and the total. It also says what paid the order, as Visa ending 4242 or PayPal. The number is taken the first time somebody opens it, and that order keeps it from then on.

You can rename the receipt in Customize, for example to Tax invoice. The PDF attached to the confirmation email uses the same name.

Where the event sells anything a booker can pick up afterwards, the order page offers it under Add to this order. That opens one list of tickets and add-ons, laid out like the event page. Whatever they pick is paid for in one payment, separate from the one they already made. Something free is added immediately. When the event has codes, the list has a promotion code field too, and a code typed there comes off the new tickets.

Anything their picks need answering comes after the list, on its own page. A new ticket that comes with a choice of workshop asks which one. An add-on that goes on a ticket asks which ticket, one already on the order or one they're adding now.

A ticket with price tiers is added at the price of the tier on sale at the time, and counts toward how many that tier has.

Confirmation emails

A confirmation email goes out the moment an order is paid or claimed for free.

When the order has a single ticket, that email is the ticket: the stub with the attendee's name on it, the code to scan at the door with the reference printed underneath, when and where the event is, whatever they answered at checkout, and what they paid.

When the order has several tickets, the email is a summary of who each one is for and its reference, and each person gets their own full email, with their own code, as soon as they're named.

The code is inside the message, so it still shows in an inbox that blocks pictures. The reference is under it, and door staff can find someone by reference when a code won't scan.

A paid order's confirmation email has its receipt attached as a PDF, unless you've chosen to link to it, or leave it on the order page, in the event's After registering settings. View your order in the email opens the order page, which has Download receipt on it too. If your account gives free orders no document, a free order's confirmation has no receipt attached, and neither does an RSVP or a free invitation. A free order's confirmation can still have its tickets attached, as below.

You can also attach the tickets themselves, as a PDF laid out like the printed ticket, with Attach the ticket as a PDF in Customize. It's off until you switch it on. Each attendee's ticket email then has their ticket attached, and the booker's confirmation has one PDF with a page for each ticket.

If a PDF takes a while to make, the email waits for it, for up to five minutes. After that it's sent without the PDF.

Orders with ten or more tickets

On an order with ten or more tickets, the order page groups the tickets by ticket type. Each ticket type shows how many of its tickets have a name, and opens to list those tickets.

Under the count of tickets still to assign, Upload a spreadsheet instead opens a page where the booker downloads the order's sheet, adds a name and email on each row, and uploads it.

Download, beside Your tickets, offers two files:

• Tickets to print is one PDF with a page for each ticket.
• List of who’s coming is a CSV file with a row for each ticket, giving its ticket type, its code, and the name and email on it. A ticket with nobody on it yet keeps its row, with the name and email left empty.

An order with fewer tickets shows one list and one bar for the whole order.

Notes

• When the account has no outgoing mail set up, that confirmation email is recorded instead of sent. Worth knowing if a booker says one never arrived.
• What was paid appears in the booker's own confirmation, and stays out of the ticket email sent on to a colleague or a guest.
• A declined card sends the buyer back to try again or pick another payment method. Nothing is charged, and the order stays pending until they do.
• A buyer who reloads a page during checkout comes back to the same step with the same tickets, still held for them. Reloading the payment form brings back the same order, ready to pay.
• A buyer can have two unpaid orders at a time. A bank transfer they signed in to pay doesn't count towards the two. If they start a third, checkout shows them the two, each with its reference and a link to pay for it. An unfinished checkout can also be canceled from there or from the order's own page, after a confirm step, and the new checkout carries on. Checkout also carries on once one of them is paid or has gone back on sale.