Answer trip questions across every timezone you sell into
Travellers ask questions from airports, at midnight, in a language your evening shift does not read, about a trip that departs tomorrow.
No credit card. Live in an afternoon.
What a travel business actually gets asked
Both columns matter. The right-hand one is what a reader is really checking for, so it is on the page rather than in a footnote.
Answered from your own pages
The reply is the answer, with a link to the page it came from.
- “What's included in the price?”
- “How much baggage can I take?”
- “What's your cancellation policy?”
- “Do I need a visa for this trip?”
- “Is airport transfer part of the package?”
Handed to a person
Declined plainly, then routed with the whole conversation attached.
- “My flight was cancelled — what now?”
- “Can you move my booking to next month?”
Each of these arrives with the whole conversation attached, so whoever picks it up starts from what the customer already said rather than from a one-line message.
Travel questions are urgent, repetitive, and global
Support demand does not follow your office hours because travel does not. The questions themselves are largely fixed — what is included, what to bring, what happens if plans change — and they are asked in every language you sell in.
- Urgent questions arrive from timezones you do not staff
- The same inclusions and baggage questions repeat on every booking
- Cancellation and change terms generate the most anxious contacts
- Multilingual support is expensive and uneven across markets
You have already written most of it
Point the crawler at these four and the assistant has what it needs. There is nothing to re-author, and nothing to keep in sync afterwards.
- 01
Trip and package pages
What is included, and what is extra.
- 02
Booking conditions
Changes, cancellations, deposits, balances.
- 03
Travel information
Baggage, transfers, what to expect on the day.
- 04
Destination guides
The practical pages people read before they commit.
The practical questions, answered anywhere
What is included, what is not, baggage rules, transfer arrangements, documentation requirements, and change and cancellation terms. All published, all answerable instantly, in the language the traveller asked in.
- Inclusions and exclusions
- Quoted from your own published itinerary rather than summarised loosely.
- Documentation guidance
- What you have published about requirements, with the source attached.
- Change and cancellation
- Your actual terms, cited, at the moment the traveller is anxious about them.
- Every timezone covered
- The same answers at 3am local as at 3pm in your office.
One knowledge base, many markets
Selling into several countries normally means maintaining several translated help centres, which fall out of sync within a quarter. Answering in the language of the question from a single maintained source removes the sync problem entirely.
Never improvise on entry requirements
Visa and documentation questions are the ones where a confident wrong answer has the highest cost, because the traveller acts on it at a border. The bot answers only from your published guidance and refuses beyond it, pointing at the official source you cite.
Every market you sell into
Answered in the language of the question, from content you maintain once.
Airport-hours coverage
The most urgent travel questions arrive at the worst possible time.
No improvised entry rules
Visa and requirement questions come from your page or not at all.
Disruption reaches a person
A cancelled flight is not a content question and never gets treated as one.
It will not improvise on entry requirements
Visa rules, passport validity and health requirements change, and a confident wrong answer about one can end a trip at a border. The assistant repeats what your own pages say and refuses beyond them — which means the currency of those pages is doing real work.
- Inclusions, baggage and booking terms: answered from your pages
- Live disruption and booking changes: routed to a person
- Entry requirements are quoted, never assembled from general knowledge
- Scheduled re-crawls mean a page you update reaches the assistant on its own
If a requirements page goes stale, the assistant will faithfully repeat the stale version. That is an argument for the crawl schedule, not against the approach.
What a travel business asks first
Short answers. If yours is not here, the assistant on this page will try it — and tell you honestly if it cannot.
Can it answer visa and entry-requirement questions?
Only to the extent your own published guidance covers them, and it will cite that page. Entry requirements change frequently and authoritatively belong to governments, so the right pattern is to publish your guidance with a link to the official source and let the bot cite it rather than paraphrase.
Can it look up a specific booking?
No. It answers from published content, not from your reservation system. Booking-specific questions escalate to a person with the conversation attached.
How many languages does it handle?
It answers in the language of the question rather than from a fixed list, working from content you maintain in one language.
Keep reading
All solutionsFrom the blog
All posts- MeasuringSatisfaction must travel with every automation numberNever report deflection, containment, or answer rate alone. Pair every automation figure with the same satisfaction instrument you used before launch.Read
- BuildingClinics: when fluent answers are unacceptableFor clinics and health-adjacent sites, AI support must refuse outside published admin facts. Fluency without grounding is unacceptable.Read
- BuildingAgencies: one bot, many client knowledge basesHow agencies should run AI support across clients: separate knowledge bases, domain locks, and evaluation per property.Read
Answer honestly. Capture the rest.
Point Matter Chat at your site and see what it can — and can't — answer. It's honest about both.
No credit card. 2 minute setup.
Every answer cites the source it came from. When there isn't one, it says so — and hands the visitor to you.
Installs on the tools you already run.