Specialty desk

This page describes the concepts you will need to understand to use specialty desk.

What is specialty desk?

Specialty desk (SPD) is an event management service that allows Travel Management Companies (TMCs) and their partners and clients to create bulk events using preconfigured information from custom templates. This feature is useful when TMCs need to organize recurring events or events that often have common travel parameters. For example, a company offering a relocation assistance program may want to book flight tickets for their employees in a specific cabin class.

Sample use case

Assume a company wants to book hotel reservations for all their interview candidates. This is a recurring activity for the event coordinator as the company conducts interviews every month, sometimes for more than 50 candidates at a time. The company would like to use the same hotel and location for all interviews. Using the specialty desk service, travel arrangers, TMC administrators, and company administrators can create a custom template containing reusable information such as the preferred airports, the hotel, and location. Event coordinators can use this template to quickly prefill the recurring details, add travelers (e.g., interview candidates), and send out invites. Each candidate will receive an event invitation with the trip details including their booking details, accommodation, location, dates, etc.

Difference between a generic event and specialty desk

In a generic event creation workflow, the event coordinator is responsible for filling in all the event details such as the event name, description, location, booking types, payment mappings, and custom field questions. This process is ideal for creating company-wide events that only happen on specific occasions (e.g., an annual company offsite, a semi-annual hackathon program, a company anniversary celebration, etc.).

In a specialty desk event creation workflow (used for recurring programs), the event coordinator can quickly prefill all event details from a pre-defined template. The coordinator then just needs to add event dates, travelers, and bulk publish the events. The event parameters (e.g., booking type) can also be overridden and modified for individual travelers. For example, assume two candidates are traveling from different locations to participate in an interview. The event coordinator can use an event template to allow one candidate to book air travel while the other books rail service based on their location and proximity to the interview venue.

Travel arrangers or TMC/company administrators work with event coordinators to create custom templates for recurring events.

How a trip is created will vary depending on whether it’s being created from a generic event or from a template. The diagram below illustrates how trips are associated with events in each of these scenarios.

Note: See basic event concepts to learn more about how generic events and trips are related.

When creating events using a template, the template settings can be inherited by the events and trips created from the template. This allows you to avoid entering most details manually every time a new event is created. The specialty desk event creation workflow also allows you to override specific settings inherited from the template if needed (e.g., if the event date needs to be customized).

APIs used by the speciality desk service

The specialty desk service uses the following APIs:

• Template APIs for creating and managing custom event templates.
• Event APIs for creating bulk events using the templates.

Using the specialty desk service involves two workflows:

1. Creating and managing event templates: TMC or company administrators create event templates that are customized for specific events. For recurring events, this template will generally contain common settings and details such as the event name, description, location, allowed booking types (e.g., air, rail), booking guidelines (e.g., allowed airports), payment mappings, traveler personas (e.g., guests), and company travel policies. These details are configured by the administrators when creating the template.

Note: User profiles with the role of COMPANY_ADMIN, COMPANY_TRAVEL_ARRANGER, TRAVEL_ARRANGER, or TMC_ADMIN can create and manage event templates.

2. Creating events using a template: Event coordinators can then use the templates created for them to quickly prefill recurring details, publish the event and its associated trips, and send event invites to travelers.

Note: User profiles with the role of TMC_AGENT, COMPANY_ADMIN, COMPANY_TRAVEL_ARRANGER, TRAVEL_ARRANGER, or TMC_ADMIN can create and manage events.