Tito redux

Tito Documentation

Anything out of place? Please get in touch!!

Activities (beta)

Activities is a feature that allows you to separate tickets,things that people buy, from activities, things that people can go to. You can describe your event in terms of distinct things that people get if they buy a ticket. Additionally, you can attach times to activities, so your attendees can receive a schedule attached to their ticket.

Because activities can have individual capacities, and can be attached to multiple ticket types, you can achieve some powerful setups that solve some of the more complex problems that arise when organising events.

Activities is a very powerful feature, but it has a bit of a learning curve, so it’s best understood with a few examples.

The Basic example

Let’s say you have two tickets: Early Bird and Regular. You sell 50 Early Birds and 100 Regulars. That’s 150 attendees. Simple, right? But sometimes you may have way more than 2 ticket types, and they all do the same thing: they get attendees access to your event.

For a conference, you would set up an Activity called “Conference”, and attach it to “Early Bird” and “Regular” and any other ticket that include access to the conference. Now, when you visit Activities, you’ll see the total number of people who have access to the conference. Super handy.

But Activities is so much more powerful than that…

The Multi-Day Conference Example

The first problem that activities solves well is an event that spans multiple days, but that people can buy tickets to either day, or both days.

In that case, there would be three tickets available:

  • A Day One ticket
  • A Day Two ticket
  • A Day One + Day Two ticket

In a traditional setup, managing this is hard because:
1) You have to guess how many of each type to allocate
2) In order to find out how many attendees you have per day, you need to add quantities together.

Number 2 is easy in a simple setup for a small event, but it can quickly get complicated.

Enter Activities. To solve this case in Tito, you would create two activities:

  • Day One
  • Day Two

The Day One activity would be attached to the Day One ticket and the Day One + Day Two ticket.

The Day Two activity would be attached to the Day Two ticket and the Day One + Day Two ticket.

In addition, you can set a capacity for each day, so you don’t need to guess quantities for the separate ticket (you can still set quantities if you only want to sell a limited number of either ticket). Now, if Day One sells out, both the Day One ticket and the Day One + Day Two ticket will both be sold out, whilst the Day Two ticket would remain on sale.

In Tito, you can find Activities in the Tickets section.

## The Tiered Ticket Example

The tiered ticket example lets you keep track of attendance across a number of tickets that offer different things.

Let’s say you have three tickets:

  • Regular Ticket, which includes conference admission
  • Midi Ticket, which includes conference admission and meals
  • Maxi Ticket, which includes conference admission, meals, and a bonus gift pack

Again, Activities makes keeping track of all of this quite straightforward.

In Tito, after setting up the above tickets, you would set up three activities:

  • Conference
  • Meals
  • Gift Pack

The Conference activity would be attached to all three tickets. The Meals activity would only be attached to Midi and Maxi, and the Gift Pack would only apply to the Maxi.

Now, no matter what combinations of tickets people eventually end up buying, you will know exactly how many Conference attendees you have, how many Meals you need to order, and how many Gift Packs you need to make.

If you ever need some help, don't hesitate to contact us…