In the calls of one UK taxi operator, the speech recogniser wrote “Asda” as “Mazda”, a local road name as “Melbourne” or “Malvern”, and a local hospital name as “Readmore”. A lookup given the wrong word finds the wrong place, or nothing, and the passenger is asked to repeat themselves.

The passenger needs the right pickup saved with the booking. Taxi voice agent address recognition has to carry that place through speech recognition, lookup, confirmation and dispatch. Our fixes in this UK deployment show why each step matters, and how a local mishearing can be corrected without making the caller start again.

Where a spoken address goes wrong

Each of these is a real failure or change from the same build, with the stage where it happened and the fix.

Stage What went wrong Fix
Speech to text “Asda” heard as “Mazda”; a local road name as “Melbourne” or “Malvern”; a local hospital name as “Readmore” Phonetic aliases for each mishearing, added to a local places list
Lookup Hotel names came back as internal dispatcher labels rather than usable pickup details Hotels are resolved server-side
Booking A lookup release wiped the coordinates, so bookings were refused Rolled back; contract and sequence tests are now required before release

The first row is the one people blame on accents. The alias list records documented mishearings and helps the lookup recover a candidate place without making the caller start again. Locality and the rest of the request still matter: an alias must not force an ambiguous name into the wrong location. When the match is unclear, the agent asks for confirmation or hands the call to staff. The list needs upkeep because new mishearings need review. The second and third rows are not speech problems at all. The place was lost after the words were understood.

What the lookup does with an address

The agent resolves each pickup and drop-off through a location lookup that uses landmarks, maps and the caller's history. If the result is unclear, it re-asks once and then hands the call to dispatch. Other rules follow from the failures above:

  • An address that names only an area, with no street, is refused.
  • A far town is confirmed with the caller before the agent goes on.
  • A hotel is matched against a landmark list, and the room number goes into the driver notes.
  • At an airport pickup, the agent asks where the flight is coming from, once.
  • If the drop-off cannot be resolved, the booking can go ahead on an agreed “go as directed” fallback.

Illustrative example — not a client transcript. All place names below are fictional.

Caller: “The Northbank Hotel in Eastmere, by the canal entrance.”

Agent: “The Northbank Hotel in Eastmere. I'll note the canal entrance for the driver. Is that right?”

Caller: “Yes. Not the Northbank in Westmere.”

The shared hotel name is the least distinctive part of the request. The locality and the rejected alternative decide the physical pickup. A later search must not quietly bring the Westmere branch back after the caller has turned it down.

Clear matchLikely matchUnclearYesNoYesNo, pickupNo, drop-offYesNoCaller says apickup ordrop-offLocation lookup:landmarks,maps, callerhistoryResultResolveddirectlyPropose it to thecaller to confirmRe-ask onceCaller confirms?Place acceptedClear now?Dispatch teamtakes the callAgreedgo-as-directedfallbackCarry theaccepted placeinto the bookingBookingaccepted with areal ID?Say the journeyis booked
Flow 1: What the lookup does with an address. A numbered text explanation follows.
  1. A clear match is accepted without troubling the caller.
  2. A likely match is proposed to the caller, who confirms or rejects it.
  3. An unclear place gets one re-ask, not an endless loop.
  4. A pickup that stays unclear goes to dispatch. A drop-off can use the agreed “go as directed” fallback.
  5. The accepted place must survive into the booking, and “booked” is spoken only with a real booking ID.

The test that matches the mistake

A replay that now finds the right place is useful, but not enough. After that lookup release was rolled back, we made contract tests (does the lookup's output still fit what the booking call accepts?) and sequence tests (do the steps still run in order?) a condition of release. Those tests check what a transcript cannot: whether the coordinates the lookup returns still reach the booking call.

The check we would ask any supplier for is the same shape: the failing example, the stage where the place changed, the repair and the near neighbour that must still be rejected. For the fictional hotel above, that means Eastmere resolves and a Westmere request is not forced into Eastmere.

What matters: the pickup survives into the booking

The lookup's job is to preserve the physical place the caller means all the way into dispatch. The accepted place, coordinates and driver notes must travel together.

We check the original mishearing, the corrected place and the nearby alternative that must still be rejected. We also check that coordinates and driver notes reach the booking. Where the location remains unclear, the workflow has an agreed fallback instead of forcing a guess.

Where to focus your address tests

Start with the places passengers actually say: hotels with similar names, local landmarks, nearby towns and recurring speech errors. Check each example through to the saved booking. Keep a staff route for unresolved pickups and define when an agreed “go as directed” drop-off is acceptable.

Bring your recurring address problems to Custom Voice Agent. We'll map where the location is lost and what the booking needs to preserve.