Victor Chen
ServiceNow Employee
ServiceNow Employee

You may have already activated pre-built Virtual Agent topics or created your own topics. After success with one initial language, you may decide it’s time to go international! 

Previously, localizing topics was a manual process of translating individual strings. In the Rome release, this is no longer the case. You can enable dynamic translation to automatically translate entire Virtual Agent topics. You can also automatically translate NLU models and all the utterances within. This lets you deliver a more personal conversational experience to your global workforce without having to configure individual languages.

find_real_file.png

To automatically translate topics and NLU models, install the Dynamic translation plugin and connect with a 3rd party translation service (IBM, Microsoft, or Google). Virtual Agent topics can be translated into any language available on the ServiceNow platform, which is over 20 languages. NLU intents and utterances are supported in 16 languages, with entities supported in 5 languages (English, French, Spanish, German, and Japanese).  

If you’re using pre-built ITSM Virtual Agent conversations and NLU models from the ServiceNow Store, then French and German are automatically available. More languages are coming in Winter 2021. 

 

Required plugins to translate your Virtual Agent topics and NLU models: 

  • Virtual Agent, NLU (part of Pro or Enterprise SKU) 
  • Dynamic Translation (part of Pro or Enterprise SKU) 
  • Rome+ instance 
  • Recommended: ITSM Virtual Agent Conversations and NLU models ServiceNow store apps for a head start 
  • i18n language pack(s)

 

Sign up for a 3rd party translation service 

Sign up and create an account with a cloud-based translation service provider. By default, the following translation service providers are supported. Note that these services are billed at a per usage rate, however their free tiers are very generous: 

 

Activating dynamic translation 

To enable dynamic translation of Virtual Agent topics and NLU models, install the plugins and sign up for one of the services noted above. Then follow one of the following docs depending on the translation service you selected: 

 

Translating your Virtual Agent topics 

Navigate to the Virtual Agent Designer, and navigate to a topic’s Languages and Translations tab. If you installed an i18n language pack, you’ll see the language listed on the Translations tab. Otherwise, you need to manually create a language record in the sys_language table. Click “Edit” next to the desired language, and then click the “Machine Translate” button. Your topic will then be translated in the selected language. You can then review and publish your translated topic.  

 find_real_file.png

Quick tip!: You can now just as easily test your topic in different languages without switching languages in the user profile. In your tester’s URL, just add “&sysparm_requester_session_language=<language code, e.g., ‘es’ for Spanish>” 

  

Translating your NLU models 

To translate NLU models, navigate to the NLU Workbench. On the right-hand side of a model name, click the 3-dot menu and select “Add a language”. One of the options is “Use software”. This automatically translates the model to the language selected in the drop-down.  

find_real_file.png

 

NLU models in your translated language will appear as a “secondary” model. Within each intent, you can review both the translated and original utterance. You can review and publish your model. 

 

 find_real_file.png

A final disclaimer: you should still use a set of eyes to review dynamic translations. Translations from any machine/model may not account for unique phrasing and the idiosyncrasies of language. A topic author or NLU model author should take the opportunity to review and refine any translated content if necessary. If you prefer a hands-on approach, you can also rely on the Localization Framework which provides a workflow tool to assign Virtual Agent topics and NLU models to be manually translated by a linguist. More information on using the Localization Framework for translations can be found here

 

Here's a Virtual Agent Academy session with a step-by-step walkthrough:

Try it out in your Rome instance today! 

Comments
John Moon
ServiceNow Employee
ServiceNow Employee

Hello Victor,

 

Virtual agent topics can be translated into other languages which are not supported from ServiceNow platform through Dynamic translation?

Victor Chen
ServiceNow Employee
ServiceNow Employee

Yes, albeit manually via our localization framework mentioned near the end of the article. 

Ulrich1
Tera Contributor

Hi Victor

We have existing NLU models for our languages and therefore grouped them. Can I still use the machine translation somehow for new intents or does it only work when you create those translations from scratch?

 

We are using San Diego and have all the mentioned components installed.

Victor Chen
ServiceNow Employee
ServiceNow Employee

You can machine translate new intents too. 

Ulrich1
Tera Contributor

Hi Victor, thanks, but what are the steps to be performed? Where should I find the option to translate an intent (obviously I was not able to locate it intuitively nor could I find documentation). As mentioned we have previously translated our NLUs manually and grouped them recently, e.g. they already exist but we would like to use the machine translation for new intents. The machine translation works fine in VA topics.

Victor Chen
ServiceNow Employee
ServiceNow Employee

Translations occur at the model level. (You can't translate individual intents if that's what you were thinking.) 

To translate NLU models, navigate to the NLU Workbench. On the right-hand side of a model name, click the 3-dot menu and select “Add a language”. 

If you've added new intents to a previously translated model, you'll have to re-translate the model.

Ulrich1
Tera Contributor

Thanks. And if I do so it will not update my previously translated intents but only translate the new ones in the existing translated models? May be the naming of that functionality is a bit misleading.

Ulrich1
Tera Contributor

@Victor Chen  Using add a new language, I cannot select a language which already exists in the NLU grouping, so I need to completely remove the existing one to be able to translate one additional intent, which also means that I loose all manually translated intents and need to review/update all the other intents again? Is this functionality only intended for the initial translation? Is there any plan to simplify this process and support intent level translation?

1234567789hrebn
Tera Expert

Hi Victor , 

Can we disable dynamic translation once we activated the plugin , and can we restrict to only few modules like ITSM 

 

1234567789hrebn
Tera Expert

@Victor Chen can we disable dynamic translation for agent chat once we install the plugin ??

1234567789hrebn
Tera Expert

@Victor Chen can we disable dynamic chat translation for agent chat once we install the plugin ,

 

Thanks ,

HK

anchalgupta
Tera Contributor

How to translate HTML message

Vinuthna
Tera Expert

I am not having the Machine translate button in my instance, Could you please suggest how to activate it?

Thack02
Tera Contributor

@Victor Chen For the virtual agent topic any topic , Machine Translate button is not available ? Am I missing any configuration step? When I check the Insights dashboard-->VA Topcis -->Partially Translated topics-->Any particular topic selected--> When i try to request translation the languages are read only and it gives info message as "Languages without localization settings are disabled". 

Thanks

Version history
Last update:
‎11-10-2021 07:00 PM
Updated by: