--- title: Enable Dynamic Translation for an unsupported language description: The ServiceNow platform supports several languages, but you can enable dynamic machine translation for additional languages in Virtual Agent. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/conversational-interfaces/virtual-agent/enable-dt-unsupported-language.html release: australia product: Virtual Agent classification: virtual-agent topic_type: task last_updated: "2026-03-12" reading_time_minutes: 3 breadcrumb: [Localization options for Virtual Agent, Build and deploy, Virtual Agent, Conversational Interfaces] --- # Enable Dynamic Translation for an unsupported language The ServiceNow® platform supports several languages, but you can enable dynamic machine translation for additional languages in Virtual Agent. ## Before you begin Install and configure the plugins for Dynamic Translation, as described in [Prerequisites for using Dynamic Translation in Virtual Agent](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/conversational-interfaces/virtual-agent/prereq-using-dt-va.md). Role required: virtual\_agent\_admin or admin ## About this task You can configure Dynamic Translation for any installed language plugin on the ServiceNow® platform. Once installed, the language is available for configuration in the Multi language support card in Virtual Agent Chat Settings. But if you want to support a language that doesn't have a plugin, you can add it to the Languages \[sys\_language\] table. Once added, you can enable dynamic machine translation for that language. For more information about multi-language support options and their tradeoffs, see [Localization options for Virtual Agent](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/conversational-interfaces/virtual-agent/multi-language-options-va.md). For more information about custom localizations, see [Custom translations](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/translating-applications.md). ## Procedure 1. Navigate to **All**, and then enter `sys_language.list` in the filter. 2. On the Languages page, click **New**. 3. On the form, fill in the fields.
| Field | Description |
|---|---|
| Name | Name and locale of the language, if applicable. For example, **Spanish \(Mexican\)**. |
| Active | Check box indicating that the language is enabled on the instance. |
| ID | The [BCP 47](http://www.iana.org/assignments/language-subtag-registry/language-subtag-registry) code for the language. For example, **es-MX**. |
| Text Direction | Direction of text for the language. Options are **Left-to-Right** or **Right-to-Left**. |
| Fallback | Language to be used if a translation is not available. The language plugin must be installed on the instance and activated for NLU, if you are using NLU topic discovery.For example, if the language is Mexican Spanish, you can specify **Spanish** as the fallback language. |