An AI phone agent for the calls your travel advisors cannot get to

A travel agency's phone rings on someone else's schedule. New trip inquiries arrive while every advisor is deep in a quote, travelers call about itineraries from six time zones away, and the moment a storm cancels a bank of flights, the line lights up with everyone at once. The calls that build the business — a new inquiry, a final-payment chase, a pre-departure check — compete with the calls that protect it, and something always waits.

ThunderPhone gives an agency or tour operator an AI phone agent that works in both directions: inbound coverage for the inquiries, status questions, and disruption calls you receive, and outbound campaigns for the reminder and follow-up calls your advisors never have time to place. It follows your instructions and searches your approved knowledge base without inventing policy.

The agent is not a travel advisor and does not pretend to be one. It never gives visa or entry advice, never takes card details, and never makes a rebooking decision — you define what it may say, what it must collect, and when it must hand off, and the agent executes those rules.

What a travel-agency phone agent can handle

Trip-inquiry intake and qualification

A new inquiry follows a script every agency already knows: destination or trip type, fixed or flexible dates, departure city, party size and ages, budget band, and the occasion. The agent can walk through your qualification script conversationally, answer approved questions about how the agency works, and deliver a structured inquiry record to your CRM or inbox by webhook or connected API. An advisor calls back with full context instead of playing phone tag to learn the basics — and an inquiry that arrives at 9 p.m. is qualified at 9 p.m., not the next afternoon.

Consultation scheduling with advisors

Once an inquiry qualifies, the next step is usually a planning conversation with the right advisor. Connected to a calendar or scheduling API — via HTTP tools, MCP servers, or webhooks — the agent can offer available consultation times, book the slot, and confirm it to the caller on the same call. Routing rules are yours: group trips to the group specialist, honeymoons to the advisor who owns them, existing clients to their own advisor's calendar.

Booking-status and itinerary questions

"Did my payment go through?" "What time is the transfer pickup?" "Is my room confirmed?" These calls interrupt quoting work all day. When the agent can read the relevant record through a connected system, it can answer from live data; when it cannot, it answers from the itinerary and policy documents you have approved, and anything outside either source becomes a transfer or a structured callback task instead of a guess. Travelers get an answer on the first call, and advisors get their afternoons back.

Payment-deadline reminder calls

Most bookings carry a deposit and a final payment due well before departure, and a missed deadline can put the reservation itself at risk — so agencies chase final payments, usually late and by hand. An outbound campaign can call travelers ahead of each due date, state the amount and deadline from your booking data, answer approved questions about payment options, and log the outcome. The agent never takes card details by phone: it directs the traveler to the agency's secure payment process and, when someone needs help or wants to discuss terms, routes them to your team. Voicemail detection can leave your configured reminder or let the campaign retry later on your schedule.

Pre-departure checklist calls

Travelers get the pre-departure pack by email and call about it anyway. A checklist campaign can reach each traveler a set number of days out, confirm the items on your list — documents in hand, insurance arranged, forms submitted, arrival details reviewed — and record what is still open. Documents and visas are handled generically: the agent can remind a traveler that the checklist includes confirming passport and visa requirements, but any question about what a specific traveler needs routes to the advisor. The agent never gives visa or entry advice.

Tour-operator group-departure coordination

A group departure means the same call placed forty times: final details collected, rooming or dietary questions chased, a meeting time confirmed, a schedule change announced. An outbound campaign can work the whole manifest with one approved script, record each traveler's answers as structured data, and flag the exceptions — the traveler with an unanswered question, the one who never picked up — for the operations team. The tenth call is delivered with the same patience as the first, and the coordinator works a short exception list instead of a phone list.

Disruption support intake — collect and prioritize, humans rebook

When weather rolls through a hub, every affected traveler calls at once, and the bottleneck is not sympathy — it is that rebooking against supplier policy is skilled agent work. The AI agent's job in a disruption is intake and triage: answer immediately, collect who is calling and which booking, capture where they are and when they travel, deliver the agency's approved status message, and prioritize the queue by your rules — travelers mid-journey or departing soonest first. Every intake lands with your team as structured data by webhook. Rebooking decisions stay with your agents; the AI simply makes sure no traveler hears a busy signal while they wait for one.

Win-back outreach to past travelers

Past clients are the warmest list an agency has, and calling them is the task that never gets done. A win-back campaign can work that list under the consent and do-not-call rules you configure: a script your team approves, an honest reason for the call, an offer to book a consultation with the traveler's advisor, and a clean opt-out that is recorded and honored. Who is contacted, how often, and under what consent basis is your call — the agent only dials the list you give it, and every conversation produces a transcript.

Multilingual traveler communication

Travel is the industry where the 47-language question stops being hypothetical. ThunderPhone supports 47 voice languages, and the agent can switch mid-call when a caller changes to one of the languages you have configured — a traveler can start in English and finish in Spanish, Portuguese, or Japanese without a callback protocol or a hunt for the one colleague who speaks it. The same qualification script, escalation rules, and guardrails apply in every configured language, and every call produces a transcript the team can review.

After-hours and time-zone coverage

An agency's clients are, by definition, somewhere else. Calls arrive from destinations half a day ahead, and the highest-stakes ones — a missed connection, a no-show transfer — rarely happen during office hours. The agent answers around the clock: it qualifies the overnight inquiry, answers the approved-material question, takes the disruption intake, and wakes a human only when the escalation rules you wrote say to. Everything else becomes a clean, categorized queue for the morning instead of a voicemail box.

Calls that reach a supplier's phone tree

Outbound calls sometimes hit the other side's automation. The agent can wait on hold at a flat reduced rate and navigate keypad menus — useful for reaching a supplier or carrier line to confirm a detail before handing off to your staff.

Sample travel-agency call flow

Agent: Thank you for calling Meridian Travel. Are you calling about a new trip, an existing booking, or something else?

Caller: We're thinking about Portugal in the spring — two of us, maybe ten days.

Agent: Wonderful. Are your dates fixed, or flexible within the spring?

Caller: Flexible, ideally late April or May.

Agent: Got it — two travelers, about ten days, late April or May. So the right advisor can prepare, do you have a rough budget range in mind for the trip?

Caller: Probably eight to ten thousand total.

Agent: Thank you. Our Europe specialist has consultation openings Thursday at 2:00 p.m. and Friday at 10:00 a.m. Which works better?

Caller: Friday. Oh — will we need visas?

Agent: Entry requirements are something your advisor will confirm with you directly, since they depend on your documents. I've booked Friday at 10:00 a.m. and noted your visa question so it's covered first.

If the caller reports an in-trip emergency or a departure inside the window the agency defines as urgent, the agent skips scheduling and follows the configured escalation path — for example, a warm transfer to the on-duty advisor or an immediate webhook alert to the operations team.

Guardrails a travel agency should set

The value of a phone agent in this industry depends on what it refuses to do. The guardrails are configuration, not hope:

• No visa or entry advice. Passport, visa, and entry-requirement questions are a known liability area for agencies. The agent may reference the checklist generically; specific requirements route to the advisor, every time.
• No card details by phone. Payment reminders state amounts and deadlines; actual payment goes through the agency's secure process.
• No rebooking decisions. During disruptions the agent collects and prioritizes; changes against supplier policy are made by your agents.
• Consent rules on outreach. Win-back and reminder campaigns run only on the lists, cadences, and consent bases you configure, with opt-outs recorded.
• Escalation on script edge. Anything the script and knowledge base do not cover becomes a transfer or a structured callback task — never an improvised answer.

Features that matter in a travel agency

Compliance posture

ThunderPhone's public compliance posture is GDPR and HIPAA compliant. The agency still controls the workflow: limit the agent to necessary information, attach only approved documents, choose recording settings deliberately, and define where call data may be sent — including how traveler data from international callers is handled.

Booking-system and CRM connections

Agents can use connected apps, HTTP APIs, or MCP tools during a call, which makes it possible to check a booking record, create a consultation appointment, or deliver a structured inquiry when the receiving system exposes the action. Webhook deliveries are HMAC-signed and retried automatically, so a briefly unavailable endpoint does not lose an inquiry.

Knowledge grounded in your documents

Attach your service descriptions, booking terms, payment policies, pre-departure packs, and FAQ material — as text or PDF/DOCX uploads (up to 5 MB per text file and 50 MB per PDF or DOCX), or imported directly from a page on your website. The agent searches those documents mid-call instead of relying on a generic answer, and each agent uses only the documents you scope to it.

Your numbers, your telephony

Bring the agency's existing numbers through a supported VoIP connection or SIP configuration; verified numbers handle inbound and outbound calling. A web voice widget can put the same agent on the agency website, so a visitor can start a trip inquiry by voice without dialing.

Human handoff

Cold transfers are available for immediate routing. Warm transfers are available on eligible production VoIP or SIP numbers that can place an outbound leg: the caller waits while the agent privately briefs the advisor, then connects the call only if the advisor accepts.

Testing before travelers hear it

Use a browser mic test for quick iteration, then run AI-caller simulations of the scenarios that worry you — a vague first inquiry, a traveler calling mid-disruption, a caller pressing for visa advice, a past client who wants to opt out. Simulations create transcripts and grading so the team can tighten the prompt before deployment, and graded scenarios can be kept as a regression suite so a prompt change never quietly breaks the disruption script. When two scripts seem equally good, an A/B experiment on live traffic settles it. Every production call leaves a transcript — and a recording when recording is enabled — that the agency can review.

What would this cost each month?

Suppose an agency handles 800 AI-assisted calls per month, averaging 5 minutes each:

800 calls × 5 minutes = 4,000 minutes per month

• Spark: 4,000 × $0.02 = $80/month
• Bolt: 4,000 × $0.05 = $200/month
• Storm: 4,000 × $0.09 = $360/month

That is base engine usage, not a quote. Premium voice or language paths can add up to 3¢ per minute, and phone-number or carrier charges depend on the telephony setup. Hold time bills a flat 2¢ per minute; voicemail and phone-menu minutes bill at the engine rate. Optional add-ons such as verbal acknowledgements, call supervision, and long prompts carry their own published surcharges. The agent builder shows the current all-in rate before calls are placed.

Frequently asked questions

Can a ThunderPhone agent qualify trip inquiries the way our advisors do?

Yes, when you give it your qualification script. The agent collects the fields you specify — destination, dates, party size, budget band, occasion, and anything else on your intake — and delivers a structured record to your systems by webhook or connected API. It asks your questions in your order; it does not invent its own.

Can it check a real booking, or does it only recite documents?

Both, depending on what you connect. Through HTTP APIs, MCP servers, or webhooks, the agent can read from and write to systems that expose the action — checking a booking status or creating a consultation appointment mid-call. Without a connection, it answers from the documents you attach, and routes anything those do not cover to a person.

Will it answer visa or entry-requirement questions?

No. The agent can remind a traveler that confirming documents is on the pre-departure checklist, but specific passport, visa, or entry questions route to the advisor. That boundary is configured, tested in simulation, and enforced on every call.

Can it take payments over the phone?

No — and it should not. Payment-reminder calls state the amount and deadline from your booking data and direct travelers to the agency's secure payment process. The agent never collects card details.

What happens during a mass disruption, like a storm?

The agent answers every call, collects the traveler's identity, booking, location, and travel dates, delivers your approved status message, and prioritizes the queue by the rules you set — soonest departures and mid-journey travelers first. Your agents work the prioritized queue and make the rebooking decisions; nothing is changed on a booking without a human.

Can one agent handle travelers in multiple languages?

Yes. Configure a primary language and additional languages, and the agent can switch mid-call when the caller changes to one of them, provided the selected voice supports the configured set. ThunderPhone supports 47 voice languages, with the same scripts and guardrails applying in each.

Is win-back calling allowed under consent rules?

Outbound campaigns run only on the lists and rules you configure. You define the consent basis, the contact cadence, and the do-not-call handling; the agent records opt-outs and every conversation produces a transcript. Whether a given list may be called under the laws that apply to your agency is a determination your team makes — the agent enforces the rules you set.

How do we make sure it sounds right before clients hear it?

Test in the browser first, then run AI-caller simulations of your hardest calls — a rambling inquiry, an anxious traveler mid-disruption, a caller pushing for advice the agent must not give. Simulated calls are graded against your criteria and can be re-run as a regression suite whenever the prompt or knowledge base changes.