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

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Conversational Interfaces

ft:clusterId :

    - convint

bundleId :

    - convint

workflow :

    - Platform


---

# Localize Virtual Agent topics that use NLU topic discovery

# Localize Virtual Agent topics that use NLU topic
discovery {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 min. de leitura

Use the ServiceNow
Localization Framework to manage the process of localizing Virtual Agent conversations that use Natural Language Understanding (NLU).

## Antes de Iniciar

Check the prerequisites for translating Virtual Agent components. For more information, see [Localizing Virtual Agent conversations](https://servicenow-prod.fluidtopics.net/5SGLCCAi_6swcoEu2GFCRw "The ServiceNow platform provides several methods for localizing Virtual Agent conversations, depending on your needs. Use the Localization Framework to manage all aspects of the translation process, whether you are using machine translation, a third-party provider, or both.").

Make sure that your Virtual Agent topics are published and performing the way you want them to. Make any adjustments before you send them to localization.

Role required: virtual_agent_admin or admin

## Procedimento

1. Navigate to AllConversational InterfacesVirtual AgentDesigner.
2. Slide the disovery type toggle switch to NLU/Keyword, then select Manage Languages
3. In the Select NLU Model list, select the model group you want to manage.  
   Intents that are mapped to a topic display on the page.
4. In the View language list, select a language.  
   The translation status of each topic in the chosen language displays on the page. Select a topic name to open the topic in Virtual Agent Designer, view or edit translations, or test translated content. The Topic translation status column shows the current status of the topic in the localization process.  
   Figura 1. Manage languages page

   If the Topic translation status column shows Needs publishing, you must publish the topic before you can submit it for translation.  
   Nota:  
   The ServiceNow AI Platform provides translations for interface features and pre-built topics. So in some topics, languages may display as partially translated.
5. Do one of the following:
   * Select the check boxes for the topics you want to translate, and then click Request topic translations. When prompted, confirm your choice.

     A translation record is created, and the translation
     status changes to In progress. The translation
     task is assigned to a user with the localization fulfiller role. For
     information about the fulfillment process in the Localization Framework, see [Fulfill a
     localization task](https://www.servicenow.com/docs/access?context=fulfill-localization-task&version=australia&pubname=australia-platform-administration&ft:locale=en-US).  
     Nota:  
     If a topic is already in localization, the corresponding check box is not available.
   * [Edit translations
     directly.](https://servicenow-prod.fluidtopics.net/Z0iVajBiCkaKGD6H~3sYWg "A Virtual Agent admin user can edit and publish translations directly in Virtual Agent Designer.")
   {#use-lf-translate-va-nlu__choices_kx1_wmr_gpb}
6. Click Manage NLU translations.  
   The model opens in NLU Workbench. Request translations for your model group. For more information, see [Translate a multilingual
   model](https://www.servicenow.com/docs/access?context=translate-multilingual-model&version=australia&pubname=australia-intelligent-experiences&ft:locale=en-US).

## Resultado

When translations are complete, Virtual Agent admins can view, unlock, or edit them from the topic Languages tab or the Manage languages page.

Once translations are published, they are made available to Virtual Agent topics that use keywords dynamically. However, language-specific intent matching is not available until model groups are also translated and published.

## O que Fazer Depois

You may need to [map a topic to secondary models or a language-specific model](https://servicenow-prod.fluidtopics.net/4KA~1snvqYL_DlUXla3DjA "Map a Virtual Agent topic to a secondary model in the model group or to a standalone, single-language NLU model for each supported language.").

When
translations are done, you can [test
localized NLU models](https://servicenow-prod.fluidtopics.net/T2i_QW76Zc8faBzmzTD9iQ "Test a translated Virtual Agent topic and the localized NLU model to ensure that it works as expected in a conversation.").
* **[Map a topic to a secondary NLU model](https://servicenow-prod.fluidtopics.net/4KA~1snvqYL_DlUXla3DjA)**   
  Map a Virtual Agent topic to a secondary model in the model group or to a standalone, single-language NLU model for each supported language.
* **[Test topic and NLU model translations](https://servicenow-prod.fluidtopics.net/T2i_QW76Zc8faBzmzTD9iQ)**   
  Test a translated Virtual Agent topic and the localized NLU model to ensure that it works as expected in a conversation.