Your AI Agent can communicate with end users in their preferred language. Use multilingual functionality to provide a personalized experience for end users across different regions and languages.
For setup instructions, see Multilingual support setup.
Multilingual support has the following constraints:
Multilingual support enables your AI Agent to serve end users across languages and regions.
Multilingual support provides flexible language handling across channels.
Ada supports 60 languages with native Reasoning Engine response generation and Knowledge ingestion in every one. All 60 languages are supported in Messaging and Email channels. Voice supports a subset of these languages today; additional languages will be added to Voice over time.
For supported right-to-left languages, web chat is tailored for the best end user experience. This includes flipped UI components such as settings, loading bar, and more.
Your AI Agent can understand end user questions in any of Ada’s supported languages, regardless of whether they are enabled in your AI Agent. However, it only responds in the languages that are enabled in the multilingual settings.
English is the default support language in all Ada AI Agents. You cannot disable it—your AI Agent always replies to English-speaking end users.
English is also the fallback language that your AI Agent uses if it cannot determine what language to use with an end user or if it cannot find Knowledge articles in the end user’s spoken language.
Your AI Agent can use Knowledge articles in any of Ada’s supported languages. For non-English Knowledge articles, your AI Agent does the following:
Determines the language the end user is writing in and identifies how best to respond using Ada’s Reasoning Engine.
If your knowledge base contains ingested content in the same language as the end user’s inquiry, the generated response only uses this matched language content.
If your knowledge base does not contain content in the same language as the end user’s inquiry, the Reasoning Engine falls back to your English Knowledge content and generates the reply natively in the end user’s language.
If the language is not an enabled language, the AI Agent replies in Ada’s default language, English.
Ada supports ingesting localized articles in any supported language. This ensures that you can serve region-specific content to your end users. For example, if your knowledge base contains different versions of English articles for end users in different regions, like American users (en-US) versus Canadian users (en-CA), Ada ingests region-specific articles from all of these locales.
Ada serves localized content to your end users based on the language that they speak. For end users speaking en, your AI Agent uses en and all localized en articles (e.g. en-CA, en-US, etc.) when serving them.
To ensure that localized content goes to the right end users, set availability rules on your localized articles.
To set availability rules for localized articles:
On the Ada dashboard, navigate to Config > AI AGENT > Knowledge > Articles.
At the top of the articles table, click Filter and select Language as the filter option.
Select the locale that you would like to set availability rules for, then click Apply.
At the top-left of the articles table, click on the check box to bulk-select all of the articles you can see in the list.
After selecting all articles under this locale, click Set availability in the bar at the bottom of your screen.
Next, set rules so that these articles are only available to end users in this region.
initialurl to do this. For example, set a rule like initialurl contains '.ca' to ensure en-CA articles only show up to Canadian end users chatting with the AI Agent on your .ca website.Lastly, click Save to apply these rules.
Now, your AI Agent will always use these localized articles with the right users, even if their language field isn’t localized (i.e. no region).
Your AI Agent can respond to end users across Web Chat, Email, and Voice, but there are differences in how each channel handles language: