AI TRAVEL AGENT

Advise on the tour while they are still dreaming about the trip. Alongside them until they get home.

AI agents ask the right questions, suggest tours that fit the budget and have places left, help hold a seat, and stay with travellers throughout the trip — on the website, Zalo, Messenger and calls.

Book a workshopSee a real scenario

Before the trip

Advice and holding a place

During the trip

Trip assistant

After the trip

Reviews and the next tour

GIAO DIỆN MINH HOẠ

The gaps in the customer journey

Tours are not lost on the price list.
It is lost in the questions nobody answered in time.

Travellers can drift off mid-enquiry, when they have to explain themselves again on a second channel, when they need help mid-trip, or after they get home and nobody follows up.

Travellers on a tour with their guide

An illustrative traveller journey

01 / 04

The moment a traveller still has ten unanswered questions

Before they open another tour operator’s tab.

01

Bottleneck · Before the tour is booked

They ask ten questions and get three answers.

What time is the flight, how many stars is the hotel, how are children priced, are there places on that date, what does cancelling cost. Every unanswered question is a reason to ask somewhere else.

Common signalsAsking departure dates repeatedly · requesting the itinerary then going quiet · comparing prices elsewhere
Last night’s inboxQuestions about tours and dates still outstandingBacklog
Travellers waitingGot a quote, never followed upWhere it leaks
The Travel Agent can step in hereAnswer fully and correctly the first time — which departures have places, how children are priced, the cancellation policy — then keep the conversation going until they book.
One agent · the whole journey

Alongside them from the first question about price.
It continues after they get home.

The Travel Agent holds the same tour catalogue, departure schedule and traveller context across all three stages — so nobody explains themselves again at each touchpoint.

01 · Advice and choosing a tour

Turn a question about price into a trip clear enough to book.

The agent asks what it needs to know — how many, when, what style, what budget — then checks it against departures that actually have places before suggesting anything.

What the agent takes on

Establish the group and the datesHow many, and whether there are young children or older travellers.
Suggest tours within the budgetOnly tours with places on the actual departure date.
Explain how the pricing worksChild rates, single-room supplements, cancellation policy.
Operational resultsA request with a clear group, dates and price — enough to move on to holding places.
AI tour adviserBefore the trip · Running

Hand over to an adviser

Customer · Messenger“Three of us, including a six-year-old, Da Nang at the end of October — is twenty million enough?”
What the agent understood3 travellersWith a childEnd of OctoberBudget ~20 million
Suggested from the departure schedule2 tours with places leftChecked against availability

Da Nang – Hoi An, 4 days / 3 nights

Departs 24 Oct · 4-star accommodation

18.900.000đ

6 places left

Da Nang – Ba Na, 4 days / 3 nights

Departs 26 Oct · Airport pick-up

16,500,000đ

12 places left

Both tours have places and fit your budget. A six-year-old is charged at 75% of the adult rate on either. Shall I send the day-by-day itinerary, or hold places on the 24 Oct departure first?

View the day-by-day itinerary

Hold places on the 24 Oct tour

The context is kept

Group2 adults + 1 child
DatesEnd of October
BudgetAround 20 million
DeparturesPaymentTraveller recordsGIAO DIỆN MINH HOẠ

Context is not lost when the stage changes

Group and datesSaved from the advisory step
Places held on the departureContinues with the same tour and policy
Travel historyReused for follow-up and return invitations
Connecting your tour operator’s systems

The agent does not sit outside the operations room.
The agent works with the systems you already run.

From tour operations and supplier bookings to payments, traveller records and the call centre — each connection states exactly what data is read, which actions are allowed, and which steps need approval.

System layers

01 · Tour operations system

Read the real availability. Use the real tour price list.

Connected within permissions

TravelTech / Tour CRM

Tour operations · API

Needs technical assessment

Bokun / Rezdy

Booking tour · REST API

Public API available

Operations file in Excel

Spreadsheet · Periodic import

Needs technical assessment

Internal systems

Custom API / Webhook

Needs technical assessment

Travel Agent

Tour & Seat Agent

Read scope: tours and availability
Write scope: temporary hold

Guardrails active

Check availability by departure datePer departure; nothing is guessed
Read the tour price listChild rates and supplements; it never sets its own price
Hold placesWithin the configured time limit
Apply the approved policyCancellations, date changes, name changes

Permissions and actions

Policy: Travel Agent v1

ReadableTour catalogue, departure schedule, places remaining, published prices and cancellation policy
Approval requiredDiscounts outside the list, adding places beyond capacity, cancelling places with a paid deposit
No accessNet rates with partners, group contracts and per-tour margins
09:14:26Checked availability on the 24 Oct departureTour CRM API · via the Tour & Seat AgentRead onlyAudit log
Every tour operator runs a different system.Actual connectivity depends on the APIs, permissions, data architecture and security requirements of the systems you already run. The platform names above only illustrate the direction of an API integration.
Assess your systems
Illustrative scenario

One call at 9pm.
One family of three sets off.

A traveller calls the hotline after the office has closed. The Travel Agent takes the call, records what they need, and carries the conversation on over Zalo until the group departs.

N

Nang Vang TravelIllustrative tour operator

Hypothetical scenario

“Are there places on the Da Nang tour at the end of October? Three of us, with a small child.”

PL

A traveller who has never bookedHotline call at 21:04
BeforeIt rings out. The next morning nobody knows the call happened, so nobody rings back.

The Travel Agent handling it

From an out-of-hours call to departure day

Live scenario

Answer calls out of hoursRecords the group, the dates and a callback number21:04
Check availability on the departureOnly offers departures that genuinely have places2 options
Hold places and send a deposit linkWithin the limit the company permits3 places
Stay with them until departurePayment reminders and the itineraryAutomated
Out-of-hours callsAnsweredinstead of ringing out
Manual work4 → 1advisers only approve exceptions
StatusDepartedwith the history of the whole journey
The figures in this scenario illustrate how it operates; they are not a commitment on results. Actual performance depends on your data, processes and connected systems.
See the agent handle your own scenario
Frequently asked questions

Before you let an agent answer in place of an adviser.

What tour operators usually want cleared up about tour data, voice channels, languages and travellers’ documents.

Your question is not here?The InCard team will work through it around your actual systems and processes.
Talk to an expert

No. The agent handles the repetitive work and the out-of-hours cover — departures, pricing, cancellation policy, sending itineraries. Bespoke tours, large groups and special requests remain with advisers.

The agent covers the shift — advisers keep the cases that need a person.

Next step

Start with one specific tour-sales scenario.
You do not have to replace the whole system.

A workshop to review your traveller journey, pick the priority scenario and work out what data to prepare before integration is discussed.

Three inputs to get started

Your tour operations systemWhere your tour catalogue and departure schedule live
Sales channels and call centreWebsite, Zalo, Messenger and the hotline you use
Priority use caseThe lost-traveller scenario you want to tackle first
The workshop does not require connecting to live systems. Integration scope is agreed only after reviewing the APIs and permissions.