An international call ends one of two ways in most businesses: unanswered, or with the customer on hold while somebody who speaks English is found. In a voice agent setup, the answer to this is not building one agent per language; it is one agent moving to the caller's language.
How it works
The agent greets in a default language. When the customer answers in another language, the agent switches and continues there. The switch happens without the customer having to ask "do you speak English?".
Three things must be true at once for this to work:
- The model must actually speak that language. Understanding and speaking are different; in some languages comprehension is good while production is weak.
- The voice must sound natural in that language. A voice chosen for Turkish may sound accented in Arabic. Defining a separate voice per language solves this.
- The knowledge base must contain information in that language. The agent switches language but cannot invent facts it does not have. If the price list exists only in Turkish, the agent will translate on the fly during an English call — usually fine, but not for product names and legal wording.
Where it works well
- Tourism and hospitality. Availability, price, location and transport questions are formulaic and translate well.
- Exporting manufacturers. Most first-contact questions are catalogue and delivery questions.
- Customers living abroad. Turkish speakers calling from a foreign number are handled by a single agent without friction.
Where it stumbles
- Two languages in one sentence. Mixed sentences can lead the agent to pick the wrong language.
- Legal text. Recording notices, consent wording and return conditions should not be left to translation; write them separately per language.
- Proper nouns. Product names, campaign names and place names become unrecognisable when translated. The instruction must state explicitly that these stay untranslated.
One persona per language, or one for all
The practical argument for a single persona: there is one knowledge base. With two agents, a price change has to be applied in two places, and one of them is eventually forgotten.
A separate persona is justified only when the conversational style genuinely diverges — markets where forms of address, levels of formality and ordering differ culturally.
The right way to test
The most common mistake in testing a multilingual setup is testing in your own language and declaring success. Three tests are needed:
- A call that starts and stays in the greeting language.
- A call that starts in the greeting language and switches on the second sentence.
- A call conducted entirely in the second language — especially when saying numbers, dates and times.
The third surfaces the most errors. Date and time formats differ by language; "14:00" should be spoken as "two pm" in an English call, not read out digit by digit.
Which language for recordings and summaries
The call happens in the customer's language, but your team reads the record in theirs. Producing the summary and tags in the panel language is what makes international calls followable by the team. The transcript itself should stay in the original language: summary translated, transcript verbatim.
Tomorrow we look at something less discussed that eats a real share of outbound budget: calls that land on voicemail.