Multilingual service for Now Assist
Summarize
Summary of Multilingual service for Now Assist
Now Assist applications leverage large language models (LLMs) to provide multilingual support by translating user-generated content. This enables communication with users in their preferred languages based on their Language & Region settings or the language detected in their messages. Multilingual capabilities are supported through multiple LLM providers including Now LLM Service, Microsoft Azure OpenAI, Anthropic Claude on AWS, and Google Gemini, with Azure OpenAI offering the broadest language coverage on the ServiceNow AI Platform.
Show less
Key Features
- Native Translation: The LLM directly processes and responds in the user’s language without intermediate translation. Supported languages are grouped into three categories:
- P1: Strong native support with high-quality translation and nuanced understanding (e.g., English, French, German, Italian, Spanish, Brazilian Portuguese).
- P2: Good native support with some limitations in nuance (e.g., Canadian French, Japanese, Dutch).
- P3: Broader language coverage supported by major providers but with less depth in training, affecting subtleties in tone (e.g., Swedish, Korean, Russian, Simplified Chinese).
- Dynamic Translation: For languages not fully supported natively, content is translated to English before processing by the LLM and then translated back to the user’s language. This fallback ensures coverage for unsupported languages and improves response accuracy and latency.
- Provider-Specific Support: Different LLM models offer varying language support levels; for example, ServiceNow Large Language Model v1 supports English natively, while Azure OpenAI GPT-4.1 supports 80+ languages.
- Extending Language Support: Customers can add languages beyond the predefined P1, P2, and P3 groups by confirming provider support, updating the syslanguage table, configuring model settings, and activating the language in Now Assist Admin settings. Reindexing sources and clearing the embedding model cache may be necessary for semantic search functionality.
- Translation Service Choice: Selection depends on factors like latency and translation quality. Native translation is included with Pro Plus and Enterprise licenses at no additional cost, while Dynamic Translation uses Microsoft Azure OEM services.
Practical Application for ServiceNow Customers
By enabling the multilingual service in Now Assist, customers can enhance user experience by providing seamless interactions in multiple languages, improving accessibility and user satisfaction. Native translation should be prioritized for supported languages to optimize performance, while Dynamic Translation ensures fallback coverage for others. Customers can customize and expand language offerings to fit their specific user base by configuring language records and model settings appropriately.
To enable and manage multilingual services, customers should use the Now Assist Admin settings and ensure proper configuration of language entries and model language support. Monitoring usage and understanding licensing entitlements will help optimize translation service utilization.
Now Assist applications use the multilingual capabilities of large language models (LLMs) to translate user-generated content.
Multilingual service overview
You can configure the multilingual services for Now Assist applications to communicate with your users in their preferred languages. The LLM detects the language used based on the user's language choice in their Language & Region preferences or the contents of the text, such as a conversation message.
Multilingual support is enabled for multiple LLM providers, such as Now LLM Service, Microsoft Azure OpenAI, Anthropic Claude on AWS, and Google Gemini. Azure OpenAI offers the most language support on the ServiceNow AI Platform.
How the different multilingual services work
The inherent multi-language capabilities of the LLM is called native translation. In native translation, text is sent as-is to the model and the model responds in the user's language. For example, if a user sends a message in Spanish, the multilingual LLM supports Spanish, so it receives the Spanish input directly from the user. It then generates a response in Spanish, regardless of the language used in the source material it uses to create that response.
For Dynamic Translation, once non-English content is detected, the translation service translates the content to English before sending the request to the large language model (LLM). After the LLM returns a response, the response is translated back into the user's preferred language for them to see. For example, a user enters a message in Slovenian. Dynamic Translation translates the Slovenian to English before giving the message to the LLM. The LLM generates a response in English, and then Dynamic Translation translates that response to Slovenian to show to the user.
If you enable both native translation and Dynamic Translation, native translation has preference and is used first.
Native translation
Supported languages are categorized into three basic groups.
P1 languages have the strongest native support across most model providers, meaning high-quality translation and generative capabilities with fewer errors. Nuance, idioms, and context are usually handled well because these languages are deeply integrated into the models.
P2 languages are supported natively by smaller ServiceNow models and most external providers, but not always by every model (e.g., some exceptions for Canadian French and Dutch). Accuracy is good, but there may be occasional gaps in nuanced understanding compared to P1 languages.
P3 languages include a broader set of languages supported by major providers like Microsoft Azure OpenAI, Google Gemini, and Anthropic Claude on AWS, but not natively by ServiceNow’s own large models. While coverage is comprehensive, these languages generally have less training depth, so subtle tone or idiomatic expressions may be harder to capture perfectly.
- P1
- English
- French
- German
- Italian
- Spanish
- Brazilian Portuguese
- P2
- Canadian French
- Japanese
- Dutch
- P3
- Swedish
- Finnish
- Czech
- Hebrew
- Hungarian
- Korean
- Norwegian
- Polish
- Portuguese
- Russian
- Simplified Chinese
- Traditional Chinese
- Thai
- Turkish
- Arabic
- Danish
Specific models vary in their support.
- ServiceNow Large Language Model v1 (Llama 3.3 70B) only supports English natively.
- ServiceNow Large Language Model v2 (GPT-OSS) supports English, French, German, Spanish, and Italian natively.
- ServiceNow Small Language Model v1 (Mistral Nemo 12B) and v2 (Apriel) supports all P1 and P2 languages.
- Microsoft Azure OpenAI GPT-4.1 and GPT-4.1-mini support more than 80 languages, including P1, P2, and P3.
- Google Gemini 2.5 Flash/2.5 Pro currently does not support French Canadian natively.
- Anthropic Claude 4.0 Sonnet currently does not support French Canadian or Dutch natively.
Adding languages beyond the P1, P2, or P3 language groups
Some providers, such as Azure OpenAI, offer additional language support beyond the P1, P2, and P3 language groups previously described. You can configure your instance to include additional languages.
- Ensure the language is on the sys_language table.
- Create a record for the language if necessary. The record should include the language name and code. The Active field should be set to true.
- Enable the language for the Now Assist model.
-
- Go to the sys_generative_ai_model_config table and open the record for the model you want to add the language to, such as gpt_small by Azure OpenAI.
Note:The model for AI Search is named E5FT. If you want to make changes to the language support for AI Search, you can configure that record. After, you need to reindex all sources in the new language.
- In the Supported languages list, add the language and save the record.
- Go to the sys_generative_ai_model_config table and open the record for the model you want to add the language to, such as gpt_small by Azure OpenAI.
- Activate the language for Now Assist applications.
-
- Go to and open the Multilingual service tab.
- Scroll to the provider you edited, then select the edit button.
- Select the language you added and save. Note:If you don't see your language as an option, ensure that the language is on the sys_language table and Active is set to true.
GlideCacheManager.flush("ais_semantic_embedding_model_cache");.Dynamic Translation
- For the list of available language packs, see Activate a language.
- For more information about Microsoft Azure OEM, see Microsoft Azure OEM for Dynamic Translation in Now Assist.
Choosing a translation service
Enabling translation for Now Assist
For more information on turning on multilingual services for Now Assist applications, see Enable translation for Now Assist applications.