A travel enquiry is rarely a question. It is a paragraph containing a destination, a rough date, a number of travellers and a budget hint, sent at eleven at night. Someone has to read it, work out what is actually being asked, and reply before the customer has messaged three other operators. Multiply that by every package and every season and the bottleneck is not sales skill. It is the reading.
The setup
What is running today
Live channels: WhatsApp. The figures at the top of this page are read directly from the account rather than estimated, and describe the setup rather than a claimed outcome.
The problem
A travel enquiry is rarely a question. It is a paragraph containing a destination, a rough date, a number of travellers and a budget hint, sent at eleven at night. Someone has to read it, work out what is actually being asked, and reply before the customer has messaged three other operators. Multiply that by every package and every season and the bottleneck is not sales skill. It is the reading.
What changed
The rollout
Stage one
One number, one thread
WhatsApp became the front door. Every enquiry, from every source, lands in the same thread against the same contact, so the history is in one place rather than split across an inbox, a phone and a notebook.
Stage two
Guided journeys per package type
Rather than one catch-all bot, the team built separate flows for the journeys that behave differently: destination enquiries, date and availability questions, and post-booking follow-up. Each one asks only what it needs and stops.
Stage three
Handoff with the answers already collected
When a conversation reaches a person, the destination, dates and party size are already captured against the contact. The consultant joins an informed conversation instead of starting one.
What is live
- Menu-driven enquiry capture, with a route back to the main menu from every branch
- Separate journeys per package type rather than a single catch-all flow
- Human handoff that carries the collected answers with it
- A unified contact record, so a returning traveller is recognised rather than re-qualified
Why a menu, and not a language model
Travel enquiries turn on facts that must not drift: which dates are open, what is included, what it costs. A guided journey answers those from the actual values every time. The judgement calls, the ones that need a person, are exactly what the handoff exists for.
Questions this raises
It replaces the wait, not the consultant. The flow collects what would otherwise be asked over three messages, and a person picks up the part that needs judgement, already knowing the answers.
The enquiry is still captured and qualified. The traveller gets an immediate, useful reply and a clear expectation of when a consultant will follow up, instead of silence until morning.
Related reading