---
sourceDocument: Australia Conversational Interfaces
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/conversational-interfaces

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Conversational Interfaces

ft:clusterId :

    - convint

bundleId :

    - convint

workflow :

    - Platform


---

# Enable Dynamic Translation for an unsupported language

# Enable Dynamic Translation for an unsupported language {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer

The ServiceNow® platform supports several languages, but you can enable
dynamic machine translation for additional languages in Virtual Agent.

## Vorbereitungen

Install and configure the plugins for Dynamic Translation, as described in
[Prerequisites for using Dynamic Translation in Virtual Agent](https://servicenow-prod.fluidtopics.net/O3xTm_26qCC80iiXE49e0w "To enable dynamic machine translation, install ServiceNow language plugins and Dynamic Translation plugins. Then configure Dynamic Translation for your instance.").

Role required: virtual_agent_admin or admin

## Warum und wann dieser Vorgang ausgeführt wird

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://servicenow-prod.fluidtopics.net/8FshmVSxf1TXr7RuQcrG5g "The ServiceNow platform provides several methods for serving your international Virtual Agent users, regardless of their language and locale. Professionally localize your conversations, use dynamic machine translation, or a combination of the two."). For more information
about custom localizations, see [Custom
translations](https://www.servicenow.com/docs/access?context=translating-applications&version=australia&pubname=australia-platform-administration&ft:locale=en-US).

## Prozedur

1. Navigate to All, and then enter <kbd class="ph userinput">sys_language.list</kbd> in the filter.
2. On the Languages page, click New.
3. On the form, fill in the fields.  
   {#enable-dt-unsupported-language__table_asg_jg4_mtb__entry__2}

   | 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. |
   [ ]

   {#enable-dt-unsupported-language__table_asg_jg4_mtb}
4. Click Submit.
5. **Wahlweise:** For a better user experience, translate some of the Virtual Agent system messages into the new language.
   1. Navigate to All, and then enter <kbd class="ph userinput">sys_ui_message.list</kbd> in the filter.
   2. Translate the following Keys:  
      * Are you sure you want to end the current conversation?
      * Click here to start a new conversation
      * Close contact options
      * \[language name\] (for example, English or German)
      * Disable audio notifications
      * End conversation
      * I have detected you are typing in {0}. Would you like to continue the conversation in {0}?
      * Just now
      * No
      * No Chat Agents Currently Available
      * Please pick an option.
      * Please type your request
      * Please type your response here
      * Send
      * Start a new conversation
      * Start typing to filter the list of topics below...
      * Support options
      * Yes

      {#enable-dt-unsupported-language__ul_mpx_kl4_mtb}  
      Hinweis:  
      If you specify a supported fallback language for the language you're adding, you do not need to translate Keys in the Messages table. For example, if you add Mexican Spanish as a language, you can specify Spanish as the fallback language. The Spanish language plugin already contains translations of these messages. For more information, see [Specify a fallback language for locale-specific languages and NLU prediction](https://servicenow-prod.fluidtopics.net/pHiKCjiLKbOlb2PIpL_t3g "Provide language locale support by specifying a fallback language for Virtual Agent to use for topics, keywords, and NLU prediction. For example, the ServiceNow platform doesn't support Mexican Spanish (mx-es), but it does support Spanish (es), which you can designate as the fallback language for a better user experience.").
   {#enable-dt-unsupported-language__substeps_s44_c2h_15b}
6. When the languages have been added, enable Dynamic Translation.  
   For more information on enabling Dynamic Translation, see [Enable Dynamic Translation for languages in Virtual Agent](https://servicenow-prod.fluidtopics.net/5ZTo2N~QLm_esEqMHhaiEQ "Enable Dynamic Translation for one or more languages in Chat Settings for Virtual Agent.") and [Multilingual service for Now Assist applications](https://servicenow-prod.fluidtopics.net/i_HJKbG72LNkoWm0_J21dw "Turn on multilingual service for user-entered text with Dynamic Translation in Now Assist applications.").