Ticket Types are most commonly set up so that each ticket represents a single traveler:
Single-traveler ticket types
↓
Example indicates 4 adult travelers
However, if your tour is designed to accommodate groups with a set number of travelers (e.g. groups of 2, groups of 3, groups of 6) or groups that fall within a specific number range (groups with 2-3 travelers, groups with 4-6 travelers, etc.), you may benefit from utilizing one of the multi-traveler settings. Review the tabs below to learn more about each one.
Set Number of Travelers
Let's say that we offer private flight tours, and we have created three unique booking options: a 2-passenger flight, a 3-passenger flight, and a 4-passenger flight. We want to charge each option at a set, flat rate.
Rather than prompting our customers to specify the number of individual travelers booking the trip, we instead create multi-traveler ticket types with set numbers and — even more important — clear labeling.
↓
For us, the above setup is ideal because we can offer each booking option at a clear, flat rate while avoiding any potential confusion that could be caused if we offered these same options as single-traveler ticket types.
Important Note
Be mindful of the Allow quantity option at checkout setting. With grouped ticketing, you want to make sure it's clear to your customers what exactly they're purchasing.
Using the flight example above: If you enable the Allow quantity option at checkout setting, your customer may ask: "Wait, if I choose the 2-passenger flight, should I mark '1' to show we're purchasing one 2-person flight, or should I mark '2' to show that there are two people planning to fly?"
In this case, it may make more sense to select the Do not show a quantity option at checkout setting
vs.
Will I be able to collect all customer data with multi-traveler ticket types?
When a multi-traveler ticket type is created as a set number, the TripWorks platform knows how many people are represented by that ticket type and applies any corresponding follow-up actions to match. For instance, when our private flight customer proceeds to the next step in the booking process, they are prompted to complete not one but two customer blocks:
The same logic applies if our experience requires signed waivers (this private flight duo would be required to sign and return two), assigned resources (e.g. two headsets), or any other settings that apply to each individual traveler.
Number Range
Let's say that we run party bus tours, and we want to charge a flat rate for each tour, regardless of how full or empty the bus may be. Rather than prompting our customers to specify the number of individual travelers booking the trip, we instead create multi-traveler ticket types with number ranges and — again, this is vital! — clear labeling.
↓
In the above example, the customer has selected the Medium Party Bus ticket type, knowing that it can accommodate up to 18 people. From our — the tour operator's — perspective, it does not matter financially whether 1, 8, or 18 people attend the event as long as the $200 flat rate is paid. However, we do still want to know how many passengers to expect so that we can stock the bus, request waivers, and assign resources accordingly.
For these reasons, multi-traveler ticket types that are created as number ranges automatically prompt customers to specify the number of event attendees while booking their trip.