Itineraries that arrive
before the questions.
A great itinerary takes a travel agent half a day to assemble — flights, hotels, transfers, restaurant notes. A Loomal agent assembles it in minutes, sends it from a real travel-desk identity, and handles every change request in-thread until departure day.
API Primitives used
mail_sendDeliver the itinerary
Itinerary goes from a real travel-desk identity with every leg, confirmation number, and local detail.
calendar_createAdd events to the calendar
Each leg, dinner reservation, and tour gets added to the traveler's calendar with the right time zone.
mail_list_messagesHandle change requests
Travelers reply with questions and changes. Agent updates the itinerary and confirms in-thread.
Itineraries are static documents.
Most itineraries are PDFs. They're out of date the moment something changes — and something always changes. The traveler emails the agency, waits, gets a new PDF, and tries to remember which version is current. The whole experience feels broken even when nothing has gone wrong.
An agent runs the itinerary as a living conversation. Every change updates the same thread, the calendar reflects the latest state, and the traveler always knows where to look.
How to build it.
mail_sendAssemble the itinerary
Agent gathers flight, hotel, transfer, and reservation details and sends a clean itinerary from the travel-desk identity.
calendar_createSync to calendar
Agent creates events for every leg with the right time zone, location, and attached confirmation.
mail_list_messagesHandle changes
Reply-driven changes get processed in-thread — flight changes, restaurant reservations, tour swaps.
Example prompt
“Build the itinerary for the Lisbon trip — flights, hotel, day tours, dinner reservations. Send it to the client from my travel agent address and add every leg to their calendar.”
What travel desks build.
Personalized leisure trips
Agent assembles bespoke itineraries with the local detail clients pay travel agents for.
Corporate travel
Business travel desks use agent identities to handle the mechanical itinerary work at scale.
Group trips
Multi-traveler itineraries get coordinated across calendars and handled in one master thread.
Last-minute changes
Flight cancellations and reschedules get reflected in the itinerary and calendar within minutes.
Local recommendations
Agent adds restaurant and activity recommendations based on traveler preferences.
Why itineraries need an agent identity.
Travel agents are valuable because of the personal, conversational layer. The mechanical work — assembling the document, syncing the calendar, processing changes — takes the time that should go to the personal layer. An agent owns the mechanical work and frees the human to do the relationship.
Loomal makes the agent practical at travel-desk scale. Every itinerary, every change, every confirmation is logged against the human travel agent who delegated the work.
Trip data scoped
Itinerary details live in the travel desk's own inbox, not a third-party tool.
Per-trip audit
Every change and confirmation is logged with the travel agent identity.
Identity per agent
Each travel agent gets their own delegated identity for clean client attribution.