“Can you make it later?” is a short request with an expensive way to misunderstand it: a second taxi gets booked and the first is left untouched.
The right response preserves the existing booking and clarifies what the passenger wants changed. It should also recognise when the caller really does want a separate journey.
Our UK taxi build makes that decision using the caller's booking history at the start of the call. This article explains how a taxi booking status voice agent separates changes, cancellations and new jobs, and why fresh arrival-time questions go to staff in this implementation.
What the agent knows when it picks up
Calls from hotel and account numbers never reach the agent. A phone router sends them straight to the operator's team. For every other call, the caller's number loads their history and existing bookings at the start of the call.
That list is the agent's whole picture of the caller's bookings, and it is as old as the start of the call. This is why the agent can recognise "I've got a taxi booked for tonight" and still be unable to say what the dispatch system shows a minute later.
Four requests that sound alike
| What the caller says | Path in this build | What counts as done |
|---|---|---|
| “Where is my taxi?” (a chase) | Mostly to staff, because the agent holds only the call-start snapshot | A person answers; the agent does not guess an arrival time |
| “Make it later.” (a change) | The team, or an update to the booking that exists; never a second booking | The existing booking carries the change and no extra job appears |
| “Cancel it.” | The team, or cancellation of that booking | That booking is cancelled |
| “I need another one.” | A new job: the normal pickup, quote and booking steps | Its own booking ID, separate from the first |
“Another taxi now” is the phrase that trips systems up. It can mean an additional vehicle, or it can mean a caller whose booked car is late. One short question settles it: do you want to change your existing booking, or book a separate taxi?
The status limit, stated plainly
A saved booking tells you a job exists. It does not tell you where the car is. Because the agent's information stops at the start of the call and it cannot ask the dispatch system a fresh question, any live answer from the agent would be a guess. So it does not guess an arrival time; it hands the question to people who can look.
For an operator with many driver-status calls, that staff workload belongs in the plan. The handoff still needs an answered connection and a useful response; initiating a transfer does not establish either.
A new job from a returning caller
When the caller does want a separate journey, they get the standard booking path: a location lookup for the pickup, one fare quote from the operator's single tariff, a recap, a clear yes and a booking into SafeKab. The agent says “booked” only when SafeKab returns a real booking ID. If it cannot confirm the booking, the call goes to dispatch.
- Hotel and account numbers go to the team before the agent speaks.
- The caller's number loads existing bookings once, at the start of the call.
- Chasing a booking goes to staff, because a call-start snapshot cannot answer it.
- Changes and cancellations go to the team or to an update of the existing booking, not to a second booking.
- A separate journey becomes a new job, and “booked” is spoken only with a real booking ID.
A time change that leaves one booking
Illustrative example — not a client transcript.
Caller: “I've got a taxi booked for tonight. Can you make it later?”
Agent: “I can see a booking for this evening. Do you want to change that one, or book a second taxi?”
Caller: “Change that one. Nine o'clock.”
Agent: “I'll pass that to the team as a change to your existing booking, so no second taxi is booked.”
In this example the change is a request for the team; the original time remains until the update is confirmed. Once the team completes it, check for one booking carrying the new time and no duplicate job.
Also test a caller who really does want a second taxi. That caller must be able to book one after the clarification; protecting the first booking should not block a separate journey.
Judge the call on the job the passenger asked for
For returning callers, check whether the system preserves the booking and the request without creating a duplicate job or inventing a live arrival time.
A status question should be judged on a reliable answer or an appropriate handoff. A change should be judged on the existing booking. A new journey should have its own confirmation. Keeping those jobs separate makes the receptionist useful to both passengers and staff.
Scope the existing-booking work before launch
Agree which changes and cancellations the assistant may complete, which require staff and who handles live status questions. In this build, changes and cancellations go to the team or an update path depending on the case; fresh arrival-time information requires staff.