Vaami
Guide 13 min readPublished 28 October 2026

Multilingual Chatbots and Voice Agents in 2026: How They Work, What to Test and How to Roll Out by Language

How multilingual chatbots and voice agents detect language, handle code-switching like Hinglish and sound native, plus a test checklist. Book a demo.

Sandeep Kumar, Co-founder, Vaami
Co-founder, Vaami

A multilingual chatbot is a chat or voice assistant that understands and replies to customers in more than one language, ideally detecting the language automatically and following the customer if they switch mid-conversation. Multilingual voice agents do the same on phone calls, adding speech recognition and a natural-sounding voice for each language they support.

This guide covers why language affects revenue and service, how multilingual chatbots and voice agents work under the hood, code-switching and transliteration, what changes between text and voice, notes for India, the Gulf, US Spanish and Europe, a testing checklist, common pitfalls and a language-by-language rollout plan.

76%
Prefer their own language
When buying, CSA Research survey of 8,709 consumers (2020)
75%
More likely to buy again
If customer care is in their language, CSA Research (2020)
98%
Of Indian internet users
Accessed content in Indic languages in 2024, IAMAI and Kantar
24
Official EU languages
Per the European Union

Why does language matter for revenue and multilingual customer service?

CSA Research surveyed 8,709 consumers in 29 countries for its 2020 study Can't Read, Won't Buy. 76% said they prefer to buy products with information in their own language, and 40% said they will not buy from websites in other languages. The preference held even when quality slipped: 65% preferred content in their language even if it was poor quality.

Service is where the effect compounds. In the same study, 75% said they are more likely to buy from a brand again if its customer care is in their language, and 60% of the most confident English readers still favored customer care in their own language. Being able to read English is not the same as wanting to use it when something has gone wrong.

India shows the scale. The IAMAI and Kantar Internet in India 2024 report counted 886 million active internet users, of whom 870 million, or 98%, had accessed the internet in Indic languages. 57% of urban internet users said they prefer Indic-language content. Indian chatbots and voice agents that work only in English are serving a minority preference, not the market.

How do multilingual chatbots and voice agents work?

Every multilingual system answers three questions on every turn: which language is this, what does the customer mean, and how should the reply sound in that language? There are three common ways to build one.

ApproachHow it worksStrengthsWatch-outs
Translation layerDetects the language, translates into a pivot language such as English, runs the bot, then translates the reply backQuick to add languages; one set of contentMeaning lost both ways; idioms, politeness and names break; adds delay on voice
Native multilingual modelA model trained on many languages understands and replies directly in the customer's languageHandles idiom, register and mixed-language input far better; less delayQuality still varies by language; needs per-language testing
HybridNative conversation, plus human-reviewed templates for regulated or high-stakes messagesNatural conversation with control where wording mattersMore setup; templates must stay in sync across languages

Language detection sounds trivial but isn't. Short messages such as ‘ok’, ‘haan’ or a phone number carry almost no signal, and many customers greet in one language and explain in another. Good systems decide the reply language over several turns rather than from the first word, and let the customer choose explicitly at any point.

Then come the entities: names, addresses, order numbers, amounts and dates. They must survive the trip between languages exactly. A bot that turns an order number into words, or swaps day and month, fails the customer however fluent it sounds.

Code-switching, transliteration and Hinglish

Code-switching is when a speaker moves between languages within a conversation or a single sentence. It is normal in many markets: Hinglish in north India, Tanglish in Tamil Nadu, Arabic and English in the Gulf, Spanish and English in the United States. A customer might write: ‘Mera refund kab tak aayega, order was cancelled last week.’ A good agent understands the whole sentence and answers in the same natural mix, not in textbook Hindi.

Glossary
What is code-switching?

A short definition of code-switching and why it matters for voice and chat agents.

Read more

Transliteration adds a second layer. Many Indian users type Hindi in Latin script rather than Devanagari, and spellings vary: ‘kya’, ‘kyaa’ and ‘kia’ mean the same thing. Gulf users may write Arabic in Latin letters, using numerals for sounds Latin lacks. The bot must understand all of these and reply in the script the customer used, unless they ask otherwise.

Numbers, dates and names deserve their own test plan:

  • Numbers: Indian English and Hindi use lakh and crore, Hindi speakers say ‘dedh’ for one and a half and ‘dhai’ for two and a half, and Arabic may be written with Eastern Arabic digits.
  • Dates and times: 03/04 is 3 April in India and Europe but March 4 in the US. Confirm dates in words.
  • Currency: say ₹2.5 lakh, AED 1,200 or $45 the way a local would, not digit by digit.
  • Names and addresses: read them back for confirmation, and send them in writing by SMS or WhatsApp where accuracy matters.

Locale data such as Unicode's CLDR, which is built into modern operating systems and browsers, handles much of the written formatting. The agent still has to get the spoken form right.

Related guide
Hinglish voice AI: how code-switching works

Why Hindi-English mixing breaks naive speech stacks, and a 10-point test you can run on any vendor.

Read more

Text vs voice: what changes for multilingual voice agents?

A multilingual chatbot only has to read and write. A multilingual voice agent also has to hear and speak, in real time, over a phone line, which adds three problems.

Speech recognition and accents

Speech-to-text accuracy varies by language, dialect and accent, and the gaps can be large. A 2020 study in the Proceedings of the National Academy of Sciences tested systems from Amazon, Apple, Google, IBM and Microsoft and found an average word error rate of 0.35 for Black speakers against 0.19 for white speakers, a gap the authors traced to the acoustic models. The lesson carries across languages: accuracy on demo audio says little about accuracy on your callers' accents. Vaami reports under 6% word error rate across its production call corpus and under 5% across UK accents in production testing. It does not publish per-language figures, so measure on your own calls.

Natural voices per language

Text-to-speech has to sound like a local speaker, not an English voice reading transliterated text. Check how it pronounces local names and places, whether it reads numbers the local way, and whether it can switch languages mid-sentence without changing speaker. A voice that sounds native in English and foreign in Tamil undoes the benefit of supporting Tamil.

Turn-taking and speed

Phone conversations need quick replies and graceful interruptions in every language. A translation layer adds delay to every turn, which is why native multilingual pipelines matter more on voice than in chat. Vaami's agents respond with sub-300ms end-to-end latency in production and let callers interrupt mid-sentence (barge-in).

Product
Hear Vaami's voice agent in Indian languages and Arabic

Play voice samples in Hindi, Tamil, Telugu, Arabic and more, including switching languages mid-call.

Read more

Market notes: Indian chatbots, Arabic, US Spanish and Europe

India: Hindi chatbots and beyond

India's Constitution lists 22 languages in its Eighth Schedule, and the DPDP Act 2023 requires that privacy notices be available in English or any of those languages. Hindi is the obvious first language for many brands, but a Hindi chatbot that can't handle Hinglish, Romanized text or English nouns inside Hindi sentences will struggle on day one. Regional languages matter for state-level businesses, clinics and lenders. Vaami's agents cover Hindi, Hinglish, Tamil, Telugu, Kannada, Marathi, Bengali, Gujarati, Punjabi and Malayalam, and handle switching between languages mid-call.

Regional guide
AI voice agents for India

Hindi, Hinglish and regional-language calling, with TRAI/DLT-aware outbound calling to Indian numbers.

Read more

The Gulf: Arabic chatbots and voice agents

UNESCO describes Arabic as used daily by more than 400 million people, in forms ranging from classical to dialectal. That range is the core challenge for an Arabic chatbot. Modern Standard Arabic suits formal written content, but many Gulf customers speak local dialects day to day and mix in English, and a reply in stiff formal Arabic can feel as distant as English. Arabic also marks gender in second-person verbs and pronouns, so the agent must address men and women correctly or use neutral phrasing. Right-to-left layout, Eastern Arabic digits and Arabic in Latin letters all need testing in chat. Vaami's agents support Modern Standard and Gulf Arabic alongside English.

Regional guide
AI voice agents for the UAE

Arabic and English calling, with UAE telemarketing and data protection context.

Read more

United States: Spanish and Spanglish

The US Census Bureau counted 41.8 million people who spoke Spanish at home in 2019, and in its 2018 to 2022 estimates Spanish accounted for 61.1% of people who speak a language other than English at home. US Spanish speakers come from many countries, so choose a neutral Latin American register, default to usted unless your brand is deliberately casual, and expect Spanish-English switching within a sentence.

Europe: many languages, formal registers

The EU has 24 official languages, and a 2024 Eurobarometer found that 47% of Europeans can speak English, so English-only support misses roughly half of them. Formality matters more than in English: German Sie or du, French vous or tu, Spanish usted or tú. Pick a register per language and brand and keep it consistent across chat, voice and email. Since August 2026, the EU AI Act's transparency rules also require that people are told when they are interacting with an AI system, unless it is obvious, so disclose it in every language you support. Vaami is GDPR and UK GDPR compliant.

How to test a multilingual chatbot or voice agent

Test each language as a separate product launch, using real customer messages and call recordings where you have consent, not vendor demo scripts. Mark each item pass or fail per language.

TestWhat good looks likeChannel
Language detectionRight reply language after short or mixed first messages; switches when askedChat and voice
Code-switchingMixed sentences such as Hinglish or Spanglish understood and answered naturallyChat and voice
Script handlingNative and Romanized input both understood; reply in the customer's scriptChat
Accents and noiseAccurate on regional accents, speakerphone, street noise and weak mobile signalVoice
Numbers and datesLakh and crore, Eastern Arabic digits, day-month order and times all correctChat and voice
Names and addressesLocal names pronounced well, read back and captured exactlyChat and voice
RegisterConsistent formal or informal address; correct gendered formsChat and voice
Brand termsProduct, plan and legal names kept as approved, not translated literallyChat and voice
Voice qualityNatural voice per language, stable when switching mid-sentenceVoice
Hand-offTransfer to a human who speaks the language, with a summaryChat and voice
Disclosure and consentAI disclosure and privacy or recording notices in the customer's languageChat and voice
MetricsContainment, transfers and satisfaction tracked per languageChat and voice

Common pitfalls: literal translation, formality and script mixing

  • Literal translation. Word-for-word versions of English scripts read as correct but unnatural, and idioms like ‘touch base’ make no sense. Write or adapt content natively for each language.
  • Wrong formality. Mixing tu and vous, or aap and tum, in one conversation sounds careless. Pick one register per brand and language.
  • Script mixing. Replying in Devanagari to someone who typed Romanized Hindi, or switching scripts mid-reply, slows reading and looks broken.
  • Translating what shouldn't be translated. Product names, plan names, addresses and reference numbers stay exactly as they are.
  • One voice for every language. An English voice reading Hindi or Arabic sounds foreign and erodes trust.
  • No fallback. If the agent can't handle a language, it should say so politely in that language and offer a human or a callback, not switch to English.
  • Measuring in aggregate. A strong overall score can hide one weak language.

How to roll out multilingual support, one language at a time

  1. 01Find out which languages your customers use, from call recordings, chat logs, CRM fields and lead sources.
  2. 02Pick the next language by volume and value, not by how easy it is to add.
  3. 03Write a style guide per language: register, brand terms that stay in English, how to say prices and dates, and phrases to avoid.
  4. 04Build the knowledge base natively, with a fluent reviewer checking answers rather than relying on a translation pass.
  5. 05Run the testing checklist on real audio and messages from that market, then launch to part of your traffic with a human fallback in that language.
  6. 06Track containment, transfers and satisfaction for that language separately, fix the top failures, then add the next one.

Plan for channels too. Customers move between messages and calls, so the same multilingual agent should work on both. Vaami runs WhatsApp automation on the same agent as its voice calls, with 24/7 replies, approved templates and one-tap Call me callbacks, and standard configurations go live in under one business day.

Product
WhatsApp automation on the same agent as your calls

24/7 WhatsApp replies, approved templates and one-tap callbacks, alongside voice.

Read more

Sources

  • CSA Research, Survey of 8,709 consumers in 29 countries finds that 76% prefer purchasing products with information in their own language (Can't Read, Won't Buy – B2C), 7 July 2020: csa-research.com/Blogs-Events/CSA-in-the-Media/Press-Releases/Consumers-Prefer-their-Own-Language
  • IAMAI and Kantar, Internet in India 2024 (ICUBE 2024), January 2025: iamai.in/sites/default/files/research/Kantar_%20IAMAI%20report_2024_.pdf
  • Press Information Bureau, The Government remains steadfast in its commitment to the development of India's linguistic heritage, 18 December 2024: pib.gov.in/PressReleaseIframePage.aspx?PRID=2085529
  • Government of India, The Digital Personal Data Protection Act, 2023, section 5(3): meity.gov.in/static/uploads/2024/06/2bf1f0e9f04e6fb4f8fef35e82c42aa5.pdf
  • UNESCO, World Arabic Language Day: unesco.org/en/world-arabic-language-day
  • US Census Bureau, Language Use in the United States: 2019 (ACS-50), 2022: census.gov/content/dam/Census/library/publications/2022/acs/acs-50.pdf
  • US Census Bureau, Most Americans speak only English at home or speak English very well, 7 December 2023: census.gov/newsroom/press-releases/2023/language-at-home-acs-5-year.html
  • European Union, Languages: european-union.europa.eu/principles-countries-history/languages_en
  • European Commission, Europeans strive toward multilingualism and value language diversity, according to latest Eurobarometer, 21 May 2024: education.ec.europa.eu/news/europeans-strive-toward-multilingualism-and-value-language-diversity-according-to-latest-eurobarometer
  • Koenecke et al., Racial disparities in automated speech recognition, Proceedings of the National Academy of Sciences, 2020: pmc.ncbi.nlm.nih.gov/articles/PMC7149386
  • Unicode Consortium, Common Locale Data Repository (CLDR): cldr.unicode.org
  • European Commission, AI Act: regulatory framework for AI, accessed October 2026: digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai
  • EU AI Act (Regulation (EU) 2024/1689), Article 50, AI Act Explorer: artificialintelligenceact.eu/article/50

Frequently asked questions

What is a multilingual chatbot?
A multilingual chatbot is a chat or voice assistant that understands and replies to customers in more than one language. Good ones detect the customer's language automatically, follow them if they switch languages mid-conversation, keep names, numbers and dates accurate, and hand over to a human who speaks the same language when needed.
Are native multilingual models better than translation layers?
Usually, yes, for conversation. A translation layer converts messages into a pivot language and back, which loses idiom and politeness and adds delay on voice calls. Native multilingual models understand and reply directly in the customer's language. Many teams pair native conversation with human-reviewed templates for regulated or high-stakes messages, and test every language separately.
What is code-switching in chatbots and voice agents?
Code-switching is when a customer moves between languages within a conversation or a single sentence, such as Hinglish, which mixes Hindi and English. A chatbot or voice agent handles it well only if it understands the mixed input, keeps track of meaning across both languages and replies naturally in the same mix rather than forcing one language.
Can a Hindi chatbot understand Hinglish?
Only if it was built and tested for it. Many Hindi speakers mix English words into Hindi sentences and type Hindi in Latin script, so a Hindi chatbot needs to understand Devanagari, Romanized Hindi and Hinglish, and reply in the script and mix the customer used. Test it with real customer messages before launch.
Do customers prefer customer service in their own language?
Yes. In CSA Research's 2020 survey of 8,709 consumers in 29 countries, 75% said they are more likely to buy again from a brand that offers customer care in their language, and 60% of the most confident English readers still favored customer care in their own language. 76% preferred buying products with information in their language.
How do you test a multilingual voice agent?
Test each language separately with real customer audio: language detection, code-switching, regional accents and phone-line noise, numbers and dates, names, formality, voice quality, hand-off to a human who speaks the language, and AI disclosure. Track containment, transfers and satisfaction per language, because an average across languages can hide one that is failing.
What makes an Arabic chatbot hard to build?
Arabic varies widely between Modern Standard Arabic and spoken dialects such as Gulf Arabic, and customers often mix in English. An Arabic chatbot also has to handle right-to-left text, Eastern Arabic digits, Arabic written in Latin letters and gendered second-person forms, so it addresses men and women correctly or uses neutral phrasing.
Which languages does Vaami support?
Vaami's AI agents support 30+ languages, including Hindi, Hinglish, Tamil, Telugu, Kannada, Marathi, Bengali, Gujarati, Punjabi and Malayalam, plus Modern Standard and Gulf Arabic, English, Spanish and French. They handle code-switching between languages mid-call, and the same agent can run WhatsApp automation alongside phone calls.
Found this useful? Share it.
Sandeep Kumar, Co-founder, Vaami
Written by
Co-founder, Vaami

Sandeep is a founding member of EmpowerX Labs and a core technical member of the team. A technology leader with an engineering-manager background, he brings deep technical experience, has built multiple startups and products, and leads AI development at Vaami.

See it in action

Ready to put an AI voice agent on your phone line?

Book a 20-minute demo — we'll configure a working agent for your use case and show you live.

Back to blog