She switched to Hindi halfway through

A composite, drawn from patterns across many real calls. The names and details are illustrative rather than a particular patient. About a minute into the call, she switched to Hindi. Not because the English was failing, but because explaining a symptom in a second language is work, and she had reached the part of the conversation where she did not want to be doing work.

Language in healthcare is not a feature you tick on a comparison table. It is whether the call functions at all. A patient describing pain in their second language will simplify, hedge, and leave things out - not deliberately, but because precision is expensive. The information the practice needs is exactly the information that gets lost.

Most systems handle this by asking the patient to choose a language at the start, which assumes they know in advance which one they will want. Real conversations do not work that way. People start in one and drift into another, particularly when the subject gets personal or difficult.

The agent follows rather than asks. If the caller switches, it switches, and the rest of the conversation happens wherever they are comfortable. The details still land in the practice's system in the language the practice works in, so nothing downstream has to change. It is the sort of thing patients mention afterwards almost with surprise - several of the comments on patient feedback are about exactly this - and it is part of the intake design rather than an add-on.

One call is an anecdote; the pattern is the point. These arrive constantly, they are individually small, and together they are the difference between a full schedule and a leaky one. The demo will ring your phone in under a minute with this exact scenario, or you can book fifteen minutes and we will use your own call flows. Practices already running it describe what changed.