Skip to content
Branemind
All case studies
Case studyCustomer experience··6 min read

A voice agent that holds its own in nine Indian languages

Support in English served maybe a third of the callers. Sovereign Indic models and a hard latency budget served the rest, including the ones who switch language mid-sentence.

p95 latency
320ms
Containment
63%
resolved without a human
Languages live
9

Measured against a baseline captured before the work started. One engagement, not a forecast for another business. See the methodology note below.

Two thirds of inbound calls were in a language the existing IVR did not speak. Callers were routed to a queue, waited, and hung up. The support metric that mattered was not CSAT. It was abandonment.

Latency is the whole product

In voice, anything past roughly 500ms of silence reads as the line going dead, and people start talking over the agent. Everything in the design is subordinate to holding p95 under that: streaming ASR, speculative first-token generation, a tool layer that returns partial results, and aggressive caching on the three intents that make up most of the volume.

  • Code-mixing handled as the default case, not an edge case, because most real callers switch mid-sentence.
  • Barge-in supported everywhere, so a caller can interrupt the way they would interrupt a person.
  • A per-turn cost cap that routes to a smaller model when the conversation is clearly routine.
  • Full transcripts, latencies and tool traces in BM Watch, sampled for human review daily.
p95 latency
320ms
Containment
63%
Abandonment
−54%
Languages live
9
The first week, callers kept asking which city the agent was sitting in. That was when we knew the latency work had paid off.
Director, Customer Operations

Methodology and privacy

  • Clients are described rather than named. Where a quote appears it is attributed to a role and published with approval.
  • Figures come from a single engagement and are not a forecast of what a different business would see. Volume, data quality and process maturity move them more than the technology does.
  • Baselines were captured before the work started. The measurement window and sample for any figure on this page are available on request.
  • Where a number is illustrative rather than measured, it is labelled as such in the text.
If this looks like your loop

Scope one customer conversation flow

Tell us the flow you want to automate and see where it sits on readiness.