It's 7:30pm and you're driving an airport transfer. The phone rings on the passenger seat: a number you don't recognize. Obviously you can't pick up, so it keeps ringing until it goes to voicemail. By the time you hit a red light and call back, twelve minutes later, the person has already booked with another operator. It wasn't a bad service or a bad price. It was simply a phone nobody answered in time.
Why the phone still decides whether there's a booking
An online booking engine covers a good chunk of demand, but not all of it. The last-minute customer who needs a car in forty minutes, the hotel concierge juggling half a dozen transfers at once who'd rather dictate them over the phone, the older passenger who isn't going to install an app for a trip they take twice a year: all of them call. And in transfers, airport runs especially, the window between the call and the actual need is often short. If nobody answers, you don't just lose that call, you lose the whole customer, because the alternative is one search away.
What happens when the driver is also the one answering
At a small operator, the person driving is often also the one invoicing, the one negotiating with hotels, and the one answering the phone. That's a physical impossibility, not an organizational gap: you can't safely take a call while driving, let alone quote a job or confirm a pickup time while looking at your phone. The usual workaround is a chain of parallel calls: to the passenger who doesn't pick up the first time, to a colleague to check if they have a free car, back to the passenger to confirm, and fifteen minutes have gone by on a booking that could have closed in the first minute.
A voice agent that knows where every car is
The alternative isn't a call center routing calls to whoever's free, it's an AI voice agent that knows the fleet's real-time status and can resolve the call without human intervention in most cases:
- Answers immediately, any time of day, with no hold music and no voicemail.
- Quotes the ride using the same pricing engine as the website, with pickup, drop-off, vehicle class and extras.
- Checks which vehicle can cover it, with enough buffer to arrive on time, before confirming anything to the passenger.
- Confirms the booking on the same call if a car is available, instead of leaving it pending for someone to review later.
- Hands the job off to the dispatch pool if no vehicle of your own can cover it, instead of simply saying there's no availability.
The passenger hangs up with a confirmed booking. The operator never had to stop driving to make that happen.
Not just phone: WhatsApp and web chat
The same logic applies to the two other text channels a passenger uses today just as naturally as the phone. WhatsApp and the website's chat run on the same booking engine and the same real-time fleet knowledge, so a conversation that starts with a price question can end in a confirmed booking without anyone at the operator having to type the reply by hand. And unlike a call, it leaves a written record of the whole exchange, useful later if there's ever a dispute about what was agreed.
Phone bookings for the customer who doesn't use apps
There's a segment of customers, mostly older travelers and mostly one-off bookings, who are always going to call, app or no app. Handling that call well isn't a concession to old technology, it's simply not leaving money on the table: that passenger pays exactly the same as the one booking from their phone, and their call gets resolved with the exact same pricing and availability engine, just spoken instead of typed.
Which channel each type of customer uses
| Channel | Who uses it most | What it needs behind it |
|---|---|---|
| Phone | Last-minute, hotel concierges, older passengers | Immediate answer and a quote on the same call |
| Regular customers, quick confirmations | Conversation history connected to the booking engine | |
| Web chat | People browsing the site with a question before they book | Reply within seconds, without leaving the page |
| Website booking engine | People who already know what they want and would rather not talk to anyone | Real-time pricing, no form answered the next day |
No channel replaces the others. What decides whether a booking closes or is lost is whether all four respond just as fast, with the same price.
What to do next
If your operation's phone today is a personal mobile ringing while you drive, the first fix isn't hiring someone to answer it nine to five: most missed calls happen outside that window. The fix is having the phone, WhatsApp and web chat share the same booking engine and the same knowledge of which car is free, so the answer arrives in seconds instead of depending on you being able to pull over. And when that engine finds that no vehicle of your own can cover the job, the sensible move is for it to hand off automatically to a network of partner operators, as described in handing a ride to another operator: how a dispatch pool works, instead of losing the booking for lack of your own availability.
Automated answering is measured in voice minutes a month, and the voice agent is included in every plan, with more minutes the higher the plan, and so is chat. If you want more minutes, you can buy a pack or add the voice add-on. What the voice agent actually does is set out separately, and the plans list the minutes each one carries. What decides whether it pays for itself isn't the price of those minutes: it's how many calls you lose out of hours today.
