# 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

```plaintext
mail_send
```

Deliver the itinerary

Itinerary goes from a real travel-desk identity with every leg, confirmation number, and local detail.

```plaintext
calendar_create
```

Add events to the calendar

Each leg, dinner reservation, and tour gets added to the traveler's calendar with the right time zone.

```plaintext
mail_list_messages
```

Handle 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.

01 `mail_send`

Assemble the itinerary

Agent gathers flight, hotel, transfer, and reservation details and sends a clean itinerary from the travel-desk identity.

02 `calendar_create`

Sync to calendar

Agent creates events for every leg with the right time zone, location, and attached confirmation.

03 `mail_list_messages`

Handle 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
- Corporate travel
- Group trips
- Last-minute changes
- Local recommendations

## 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
- Per-trip audit
- Identity per agent

## Run itineraries as a conversation.

Build, send, and update — fully autonomous.