> ## Documentation Index
> Fetch the complete documentation index at: https://docs.apollospace.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Travel & tourism

> Itinerary requests, booking follow-up, supplier coordination, and traveler messaging before and during trips — with payments, refunds, and contracts always staying human.

It's 10pm. A couple asked over WhatsApp for "a seven-day Chile trip leaving on
the 12th" and has been waiting for options since this morning. Three hotel
bookings made last week still haven't come back confirmed by the supplier. A
client flying out the day after tomorrow hasn't received their voucher or the
airline check-in reminder. And the ground operator in Santiago sent a transfer
time change that nobody passed on to the traveler. All open at once, and every
idle hour is a sale going cold.

**What leaves your plate:** taking the request and assembling options from what
suppliers offer, chasing booking confirmations, firing the pre-trip routine
with documents and reminders, and keeping the traveler informed when a supplier
changes something — all with context, within budget, and with **payments,
refunds, and contracts always waiting on a human**.

## How it works, in one line

A travel agency or tour operator is **relationship and logistics on top of
information that already exists**: what each supplier offers, the cancellation
policy, the documents each destination requires, the traveler's history. The
agent invents no price and closes nothing that touches money — it reads what's
in the [Company Brain](/en/features/brain), acts within it, and only decides
alone when the action is neither a financial commitment nor a change to the
trip's terms.

```mermaid theme={null}
flowchart LR
    A[Trigger<br/>itinerary request, pending booking,<br/>trip arriving, supplier change] --> B[Agent pulls context<br/>from Company Brain + CRM + supplier info]
    B --> C[Decides + uses tools<br/>WhatsApp, CRM, Documents, Routines]
    C --> D{Touches money<br/>or the trip's<br/>terms?}
    D -->|No| E[Assembles options / chases / reminds / informs]
    D -->|Yes| F[Proposes + calls a human<br/>with full context]
    E --> G[Becomes memory<br/>the next trip starts from what's known]
    F --> G
```

## Concrete flows

### 1. Itinerary request — options assembled from supplier info

**Trigger:** a "ten days in Patagonia in March, two adults" lands by
[WhatsApp](/en/integrations/whatsapp) or [chat](/en/features/chats).

The agent logs the request as a [lead with an activity in the CRM](/en/features/crm),
identifies the traveler, and cross-checks what they asked against what suppliers
offer — rate sheets, packages, availability, and conditions living in the
[Company Brain](/en/features/brain). From there it **assembles a draft of
options** in a [document](/en/features/documentos): legs, lodging, transfers,
the price band of each combination, and what changes between them. When public
information is missing — the best season for a trek, whether a park requires an
advance reservation, how long a leg takes — [Scout](/en/agents/scout) researches
the open web (via [Tavily](/en/integrations/tavily)) and returns the source.
The draft comes back ready for you to review and send.

<Note>
  The win isn't "a bot that sells a package." It's that assembling the first
  proposal — the work of digging through suppliers and stitching options
  together — stops eating the whole afternoon, and the consultant steps in to
  add the human touch and close.
</Note>

### 2. Booking follow-up — confirmation chased before it becomes a problem

**Trigger:** a [routine](/en/features/rotinas) the agent schedules for itself —
it sweeps bookings with a pending confirmation.

On fire, the agent cross-checks what was requested against what each supplier
has already confirmed, in the [CRM](/en/features/crm). For each booking with no
reply — hotel, transfer, tour — [Marcus](/en/agents/marcus) **chases the
supplier** on each one's channel ([email or WhatsApp](/en/features/outbound)),
asking for the confirmation number and the status. Replies flow back into the
CRM as activity. If a supplier doesn't answer within the window, it opens a
[task](/en/features/boards) so the consultant acts before the traveler flies out
without a firm booking.

<Warning>
  Follow-up is external communication at volume. Keep **human approval before
  each send** at first — the agent prepares the chase queue, you review and
  release it. Autonomy grows like a ratchet: once it's reliable, you let the
  batch go. Any **payment to a supplier or change to a booking's terms** stays a
  proposal for a human to approve.
</Warning>

### 3. Pre-trip routine — documents and reminders right on time

**Trigger:** a [routine](/en/features/rotinas) that sweeps whoever flies out in
the next 72 hours.

On fire, the agent pulls from the [CRM](/en/features/crm) who's traveling and
assembles the pre-trip pack: vouchers and trip documents gathered in a
[folder](/en/features/pastas) per traveler, the check-in reminder, the times,
what each destination requires (passport, visa, vaccination proof — whatever's
recorded in the [Brain](/en/features/brain)), and emergency contacts.
[Marcus](/en/agents/marcus) sends it all on the traveler's channel
([email or WhatsApp](/en/features/outbound)) with the right lead time and asks
for a delivery confirmation. Whoever doesn't reply enters a second reminder
round.

```mermaid theme={null}
flowchart TD
    A[Routine: flies out in 72h] --> B[Agent gathers voucher, documents,<br/>destination requirements, times]
    B --> C[Marcus sends on the traveler's channel]
    C --> D{Confirmed<br/>receipt?}
    D -->|Yes| E[Marks ready in the CRM]
    D -->|No| F[Second reminder + task to the consultant]
    E --> G[Becomes memory]
    F --> G
```

### 4. Supplier coordination mid-trip — traveler always informed

**Trigger:** a change arrives from a supplier — a flight delay, a transfer time
change, a hotel swap — by [WhatsApp](/en/integrations/whatsapp) or email.

The agent reads the change, identifies which trip and traveler it belongs to in
the [CRM](/en/features/crm), and **assesses the impact**: the 2pm transfer
became 4pm, so the afternoon tour needs adjusting. It drafts the message to the
traveler in the house's tone — what changed, the new time, what to do — and
**leaves it waiting for your approval** before sending. In parallel, it prepares
the coordination reply to the supplier. The whole case sits on a
[task](/en/features/boards) with the history, for the consultant to follow.

<Info>
  **Why this matters:** a supplier change is what ruins a trip when nobody
  relays it in time. The agent captures the change, measures the knock-on
  effect, and prepares the traveler's heads-up **before** they show up for a
  transfer that isn't coming — not after.
</Info>

## What stays human

<Warning>
  The agent **proposes**, never decides alone, whenever the subject is:

  * **Payments and refunds** — paying a supplier, processing a chargeback,
    adjusting a charge. Every financial move goes through approval.
  * **Supplier contracts** — closing, renewing, or changing terms with a hotel,
    ground operator, airline, or operator.
  * **Any commitment that changes the traveler's booking terms** — rebooking,
    canceling, upgrading, or altering what's already confirmed.
  * **A commercial proposal to the client** — closing the package and the final
    price.
  * **Heavy external, legal, or regulatory communication.**
  * **Governance decisions and destructive actions** — deleting records,
    canceling bookings in bulk.

  In those cases the agent prepares everything — the draft, the context, the
  recommendation — and **waits for a person to approve.** Every action lands in
  the auditable trail, with author and justification, and spend is capped by
  [Stars](/en/billing/stars) before the call ever happens.
</Warning>

## Where to start

<Steps>
  <Step title="Connect the channel and teach suppliers to the Brain">
    Wire up [WhatsApp](/en/integrations/whatsapp) and upload your rate sheets,
    per-supplier conditions, cancellation policies, and per-destination
    requirements into the [Company Brain](/en/features/brain). That's where the
    first itinerary proposal comes from.
  </Step>

  <Step title="Schedule booking follow-up">
    Create a [routine](/en/features/rotinas) that sweeps bookings with a pending
    confirmation and let the agent chase each supplier — with human approval
    before each send at first.
  </Step>

  <Step title="Turn on the pre-trip routine">
    Set up the [routine](/en/features/rotinas) that sweeps whoever flies out in
    72 hours and let the agent gather documents and reminders into each
    traveler's folder and send them right on time.
  </Step>
</Steps>

## Next steps

<CardGroup cols={2}>
  <Card title="Commercial" icon="handshake" href="/en/use-cases/commercial">
    The lead, proposal, and follow-up pattern that carries the itinerary sale
    from first contact to close.
  </Card>

  <Card title="People & support" icon="users" href="/en/use-cases/people">
    Triage and traveler messaging at volume — before, during, and after the
    trip.
  </Card>

  <Card title="WhatsApp" icon="whatsapp" href="/en/integrations/whatsapp">
    The channel where the itinerary request and the traveler happen — proposal,
    confirmation, and heads-up in the same place they already are.
  </Card>

  <Card title="Routines" icon="clock-rotate-left" href="/en/features/rotinas">
    The cron behind follow-up and pre-trip — the agent fires on the right day,
    with nobody remembering.
  </Card>
</CardGroup>