An enquiry at 11 PM waited until morning. The traveller did not.
Travezco sells fixed-departure group tours and fully customised trips, and every enquiry arrives on WhatsApp. At peak season that is 10,000–14,000 a month against a team of twelve - over 400 conversations a day, on top of running the trips already sold. We rebuilt the whole enquiry-to-review journey so that speed and quality stopped depending on how busy the team happened to be.
- Client
- Travezco Pvt Ltd
- Function
- Enquiry-to-review operations
- Geography
- India · WhatsApp-first
- Live in
- 2 weeks
Business was not the problem. Volume was.
Travezco runs two quite different product lines - fixed-departure group tours on readymade itineraries, and fully customised trips built around each traveller. All the demand arrives in one place: WhatsApp, which is where Indian consumers actually transact.
At peak that meant 10,000–14,000 enquiries a month reaching a team of twelve. Over 400 conversations a day, roughly forty per person, on top of running the trips already sold - and every one handled by hand, from qualification through to the review ask.
The assignment was not to add a chatbot. It was to redesign the journey so quality and speed stopped depending on how busy the team happened to be that day.
Where it started
Travezco's own figures, supplied by the client from their records for the period before the build. We publish the client's baseline as the client's baseline.
- Peak-season enquiries a month
- 10,000–14,000
- Conversations a day at the top end
- 400+
- Time to first reply
- 5 min – 2 days
How an enquiry used to travel
Nine steps, and a person had to notice, decide and act at every one. Two quite different product lines ran through the same ad-hoc threads, and the trip generated as much work as the sale - payment reminders, traveller details, departure logistics, daily updates, the review ask, every one of them manual and time-sensitive.
- 01
Enquiry arrives on WhatsApp
Into inboxes already carrying active-trip coordination.
- 02
It waits for a free team member
Five minutes, or two days. Not carelessness - 400 conversations a day and no queue.
- 03
Someone qualifies it by hand
Asked differently by each of twelve people, because the process lived in habits.
- 04
An itinerary is assembled and sent
Built by hand per chat, fixed departure or bespoke alike.
- 05
Pricing and payment are chased
Status known only to whoever was chasing.
- 06
Traveller details are chased too
More messages, more remembering.
- 07
Departure logistics coordinated by call
Coordinator and driver numbers, pickup points - arranged by voice, held in one head.
- 08
On-trip updates sent manually, or missed
And every miss was visible to the customer.
- 09
A review is requested, if remembered
The last step was also the one most likely not to happen.
Answered at 23:41. Confirmed before anyone woke up.
A customised-trip enquiry arriving four hours after the office closed - qualified, drafted, revised and confirmed overnight. Waiting for the team next morning: one priced quotation.
Enquiry 23:41 · qualified 23:49 · itinerary drafted 23:56 · revised and confirmed 07:15. Nobody at Travezco was awake.
Interface shown with representative data, not real customer records.
- hi, planning a trip23:41
- Hi! I'm Travezco's virtual travel assistant. Happy to help you plan it. Where are you thinking of going?23:41Identifies itself as an assistant on the opening turn.
- manali for 4 days, 6 of us, from delhi23:43One message, four fields, no punctuation - which is how people actually write.
- Thanks Rupesh. Two quick things - which dates are you looking at, and is 3N/4D right for the six of you?23:46
- around 12 oct, yes 3N/4D23:49
- Here's a first draft. Day 1 Delhi → Manali · Day 2 Solang Valley · Day 3 Atal Tunnel + Sissu · Day 4 Hadimba temple and return. Stay: 4-star Old Manali, 2 rooms + 1 family room.23:56
- can day 3 be lighter? my parents are with us07:12A revision in plain language, handled without a human.
- Of course. Day 3 is now Atal Tunnel with a short stop at Sissu and back by early afternoon - no long walking. Everything else is unchanged. Shall I confirm this version?07:12
- yes perfect, confirm07:15
What changed
| Before | After | |
|---|---|---|
| First response | 5 minutes to 2 days | Under a minute, 24/7 |
| Follow-up | Individual memory | Timed, on every conversation |
| Itineraries | Built by hand, per chat | Drafted and revised in chat |
| Payments | Chased; status known to one person | Tracked, reminded, visible |
| Trip communication | Manual, occasionally missed | The same sequence every trip |
| Visibility | None | Live pipeline, full history |
What it was worth
Measured by Travezco against their own pre-project figures after go-live. The revenue effect below is arithmetic on the client's booking volume and average booking value, and is stated as a range because those inputs are ranges.
- Lead-to-paid conversion
- +10%
- Google rating
- was 4.74.9
- Time to first reply
- was 5 min – 2 daysUnder a minute
- Additional bookings a month
- 50–80
- Additional revenue a year
- ₹1.4–2.4 cr
- Added headcount
- None
Where the revenue actually comes from
A 10% conversion improvement on 500–800 bookings a month, at Travezco's ₹25,000 average booking value, is roughly 50–80 additional bookings and ₹12–20 lakh a month - ₹1.4 to ₹2.4 crore a year, from the same enquiry volume and the same team.
That is arithmetic on the client's own figures rather than a separate measurement, and it deliberately excludes any upside from after-hours capture or from the improved rating.
The rating is the part worth dwelling on. A 4.7 becomes a 4.9 at this volume only when every trip gets the same attentive communication - not most trips.
How it runs now
Website, Instagram, Meta ads and referrals all land on the same WhatsApp thread, and one defined path runs from there.
- 01
The assistant answers and qualifies, instantly
Destination, dates, group size, budget, hotel preference - and the practical questions travellers actually ask.
- 02
The conversation routes by trip type
Group enquiries get matching readymade departures. Customised ones go to requirement gathering instead.
- 03
The itinerary is built and revised in chat
The assistant drafts, takes revisions in plain language, and iterates until the traveller confirms. Standing requests - a family room, a relaxed pace - are held append-only, so a later message can never erase an earlier promise. Quiet leads get timed follow-ups; unresponsive ones go cold on a schedule rather than lingering.
- 04
Payment runs without the chase
A link for the 40% advance, the balance reminded automatically before departure, and a status the whole team can see.
- 05
The booking confirms itself
Coordinator and driver contacts, pickup point, timings and packing essentials - and for group departures, the coordinator gets the group's details.
- 06
The trip communicates on a schedule
Reminders at 24 and 4 hours, a morning itinerary each day, an evening check-in, then the review request.
- 07
A person is always one click away
Mid-trip problems arrive on the same thread and reach the team with the full conversation attached - resolved in minutes rather than re-explained.
What the assistant does, and what stays human
The objective was to make the same team cover the whole funnel, not to replace anyone. Two guarantees made that acceptable: no action inside the operations console can send a customer a message, and payment processing stays under explicit human approval.
The assistant
- First response, at any hour
- Qualification before anything is sold
- Matching readymade departures
- Building and revising itineraries in chat
- Timed follow-ups and cold-lead handling
- Every pre-trip, on-trip and post-trip message
The team
- Complex and unusual itineraries
- Partner and supplier negotiation
- Pricing judgement and exceptions
- Anything the assistant flags
- Approving what goes out formally
- The trip itself
The half most systems skip
The sale is the start of the work, not the end of it. From the moment a booking is confirmed the trip communicates on a schedule, and nobody has to remember any of it.
Confirmation, reminders at 24 and 4 hours, a morning message every day of the trip, an evening check-in, then the review ask. Mid-trip problems arrive on this same thread and reach a person with the full context attached.
- Your quotation is ready, Rupesh. 6 travellers · 3N/4D Manali. Trip total ₹1,92,000, 40% advance ₹76,800. Secure payment link below.11:20Every figure read from a record, never written by the assistant.
- Payment received - you're confirmed. Your coordinator is Ravi, and your pickup point and packing list are below.11:34
- Reminder: your balance of ₹1,15,200 is due before departure.T−3dNobody remembered this. The schedule did.
- Departure tomorrow - please be at the pickup point by 21:30. See you soon!T−24h
- Good morning! Today - Solang Valley, leaving 09:30. Carry a jacket, it's 6°C up there.Day 2
- Hope you had a wonderful trip! Two minutes of feedback would mean a lot - and if you enjoyed it, a Google review helps us more than you know.T+1
What the founders open in the morning
The owner's question - "how many enquiries came in, and where are they?" - now has an answer on a screen instead of a guess.
Travezco · one operations view · peak-season week
- 147
- Enquiries overnight
- 100%
- Answered automatically
- 9
- Awaiting a person
- 11s
- Median first response
PIPELINE
- New214
- Details taken96
- Itinerary built41
- Confirmed18
WHERE ENQUIRIES COME FROM
- Instagram44%
- Website27%
- Meta ads18%
- Referral11%
One operations view, shown with representative data. The published outcome figures are above, and are labelled separately.
"I used to be the bottleneck of every operation. Today the whole process runs on its own, operations are automated, our ratings have gone up, and I finally have time to work on scaling the business instead of running it message by message."
A process that survives people
A team of eight now supports peak volumes of 10,000+ enquiries and 500–800 bookings a month, because the routine layer no longer consumes human hours. Time went to the work that needs judgement.
The journey is defined in software rather than in habits, so a new joiner inherits a working process on day one and a leaver does not take it with them. For the founders the question changed from "can we keep up?" to "how much more volume do we want?"
Where else this applies
The architecture is not travel-specific: instant capture, conversational qualification, automated lifecycle communication, and full visibility with a person one click away. It fits clinics, estate agencies, education consultancies and home services unchanged - and the same system runs on SMS, Instagram or web chat.
Inbound enquiries arriving faster than a team can physically open them.
Response speed as a competitive variable, where the customer is messaging your competitors in the same session.
Repetitive qualification done by the people who close deals.
Time-sensitive follow-up that runs on someone remembering.
Two or more product lines served by one undifferentiated process.
Growth that would otherwise mean proportional growth in headcount.
You do not have to take our word for it
Travezco published two short demos of the system running - the sales conversation, and the trip lifecycle that follows it.
Have an operational problem worth solving?
Bring us the process that's expensive, slow, manual or difficult to scale. We'll spend 30 minutes understanding it and telling you - honestly - whether AI or automation can meaningfully improve it.