Bookings landing in six inboxes and calls landing anywhere? See what one system looks like. Get a free automation audit

The Challenge

The business had grown into three companies. The operating team was still one team, working across all of them without a system that knew that.

1. Every channel had its own inbox. Bookings came in from third-party travel platforms, each tied to a different email address belonging to a different company. Consolidating them was somebody's morning. Nothing held origin, destination, travel dates, traveller details and guide assignment in one record, so answering "what's happening on Thursday?" meant opening several places at once.
2. Travellers didn't know who was collecting them. Driver and guide details went out manually, when someone remembered. A traveller arriving somewhere unfamiliar without a name or number is the single most predictable support call in this industry, and it was happening every week.
3. Three customer lines, no routing. Three B2B numbers for three companies, with calls arriving and being redirected by hand.
4. Seven numbers for drivers. Seven separate lines across travel support, sales support, medical emergencies and other departments. A driver in trouble had to remember which one, or call the one they knew and hope it got passed on. That is a safety problem wearing a telephony problem's clothes.
5. Spreadsheets were running operations. Bookings, expenses and driver information all lived in Google Sheets. Workable at one volume, not at theirs.

What We Built

Zoho One as the operating system for the whole business, with custom Creator applications where the workflow was specific to how this agency runs, and telephony and WhatsApp wired into it so the two things customers and drivers actually touch — the phone and their messages — connect to the booking record.

One booking record, whatever channel it came from

• Bookings from every third-party platform and inbox consolidated into a single system, across all three companies, so email communication is managed in one place.
• The booking holds what the operation needs: origin, destination, travel dates, traveller details and the assigned driver and guide.
• Expense management moved onto the booking rather than sitting in a separate sheet, so the cost of a trip lives with the trip.
• Reporting across bookings and expenses together.

Spreadsheets replaced with applications

• Custom Zoho Creator apps built to take over from Google Sheets for booking and operational data.
• Automated booking emails, removing a manual step that was repeated on every single reservation.
• An internal driver guide built into the system, so drivers have their tasks and instructions in one place.
• Customer feedback capture and call recording, so service quality is reviewable rather than anecdotal.

The message that stops the phone ringing

• WhatsApp Business API connected to the CRM, with booking details sendable by WhatsApp or email straight from the record.
• Automated notifications carrying driver and guide details to travellers a few days before travel.
• A manual send option too — a button and pre-defined templates — because operations teams need to send things off-schedule, and automation-only designs get worked around within a fortnight.

One number for drivers, seven options

• Cloud telephony and IVR integrated with the system, routing the three customer-facing numbers to the right company or department automatically by dialled number.
• The seven departmental driver lines collapsed into a single number with a one-to-seven menu — travel support, sales support, medical emergency and the rest — routing the driver to the right desk on selection.
• One number to remember, which is the point. Nobody recalls the right extension during an emergency.

Handover done properly

• Staff training across the Zoho suite, the IVR and WhatsApp, with documentation covering usage, configuration and troubleshooting.
• Testing across every integrated component before deployment, then go-live with 15 days of support.
• Twice-weekly progress updates from the project manager throughout, which on a six-month build is the difference between a partnership and a series of surprises.

Results

• Every booking in one place. Three companies, every channel, one record carrying traveller, driver, guide, dates and cost.
• Travellers are told who's collecting them, automatically, before they travel.
• Drivers have one number. Seven lines became a single IVR with seven options.
• Calls reach the right company without a human redirecting them.
• Spreadsheets retired in favour of custom applications, with feedback and call recordings captured as a matter of course.

Why It Worked

The seven-numbers problem is the one worth talking about, and it was never on the requirements list as a priority.

It reads like a tidy-up. It isn't. When a driver has a medical emergency, the failure mode is not that they dial slowly — it's that they dial the wrong department, or the one number they happen to have saved, and lose minutes being passed along. Collapsing seven lines into one number with a menu removes a decision at exactly the moment nobody should be making one. That is a safety outcome delivered through a telephony configuration, and it cost very little. Routing calls by region and language did the same job at a larger scale for a global travel membership club.

The second decision was building both the automated and the manual send. Every pre-travel WhatsApp fires on schedule, and the team can still push one out by hand from a template. Purely automated designs look cleaner in a demo and get bypassed in week two, because real operations have exceptions — a changed driver, a delayed flight, a guest who asks. Give the team the override and they use the system instead of going around it.

And the spreadsheets were replaced, not integrated. There is always a cheaper version of this project where Sheets stays and Zoho reads from it. It would have worked for about a year. Three companies' bookings running through a shared spreadsheet is a data-integrity problem waiting for a busy season.

Frequently asked questions

Facing the same challenge?

If your bookings arrive in several inboxes, or your team is redirecting calls by hand, we'll show you what one connected system looks like for your operation. Start with a free automation audit. Get a free automation audit