--- 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 --- # Localizing Virtual Agent conversations # Localizing Virtual Agent conversations {#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 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. Use the ServiceNow Localization Framework to standardize and track the translation process for Virtual Agent topics. The framework enables you to define the business process for translating your conversations. Use it to configure the following: * How localization requests are fulfilled.Options include machine translation, a translation management system (TMS), and exporting and importing files. * Who is responsible for each step in the process.Virtual Agent uses the following roles: * Localization requestor * Localization fulfiller * Localization editor {#localize-va-topic__ul_czg_hps_gpb} * Business rules for the process: * Auto translation and publication * Approval required for translation and publication {#localize-va-topic__ul_yyx_jps_gpb} {#localize-va-topic__ul_cjz_bns_gpb} To learn more, see [Localization Framework](https://www.servicenow.com/docs/access?context=localization-framework-landing&version=australia&pubname=australia-platform-administration&ft:locale=en-US). To learn more about localization roles, see [Localization roles for Virtual Agent](https://servicenow-prod.fluidtopics.net/FpQyON9fERKsdSntNsrdGg#localization-roles-va "Assign localization roles according to a user's scope in the localization process. Users may request translations, fulfill translation requests, and edit translations, based on their role."). ## Localizing topics {#localize-va-topic__section_okx_3wv_mpb} The localization process flow depends on the method of topic discovery that you are using for your topics. The following types of topic discovery are supported using the Localization Framework. * Keyword topic discoveryWhen you use the Localization Framework, the chat conversation and the keywords associated with the topic are translated. * Natural Language Understanding (NLU) topic discovery If your topics use NLU, both the topic and the model group must be localized. When you request a translation from Virtual Agent Designer, the topic and any optional keywords are translated. You must request translation for model groups from NLU Workbench. For more information about that process, 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). Once the topic and secondary models are localized, you may need to [map the models to the topic](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.") before publishing them. {#localize-va-topic__ul_qyh_vwv_mpb} ## Prerequisites {#localize-va-topic__section_prerequisites_p13_hph_fpb} Importante: Currently, translatable strings such as topic text and bot responses cannot contain embedded quotes. Strings that contain embedded quotes cannot be localized. Do the following before you begin managing translations: * Activate the ServiceNow plugin for each language you want to support. The Localization Framework is also installed by default. For more information, see [Activate a language](https://www.servicenow.com/docs/access?context=t_ActivateALanguage&version=australia&pubname=australia-platform-administration&ft:locale=en-US). * Configure the translation mode that you want to use in the Localization Framework. You can configure machine translation, a translation management system (TMS), or send via email. For more information, see [Translation modes](https://www.servicenow.com/docs/access?context=translation-modes&version=australia&pubname=australia-platform-administration&ft:locale=en-US). * If you are using Natural Language Understanding (NLU), enable languages in Virtual Agent settings. For more information, see [Enable NLU languages in Virtual Agent settings](https://servicenow-prod.fluidtopics.net/xK_32mye7Suo7k~nRHeZ3Q "If you plan to use language-specific NLU models, you must enable the installed languages in the Supported NLU Languages list. A language is enabled if the Enabled column displays true. English language is enabled by default."). * If necessary, add secondary languages to your NLU model group. For more information, see [Multilingual model management](https://www.servicenow.com/docs/access?context=multilingual-model-managent&version=australia&pubname=australia-intelligent-experiences&ft:locale=en-US). * Assign localization roles to team member groups.Users are assigned different roles based on their responsibilities for the translation process. For more information, see [Localization roles for Virtual Agent](https://servicenow-prod.fluidtopics.net/FpQyON9fERKsdSntNsrdGg#localization-roles-va "Assign localization roles according to a user's scope in the localization process. Users may request translations, fulfill translation requests, and edit translations, based on their role."). {#localize-va-topic__ul_zkv_ncp_fpb} ## Manage languages by model {#localize-va-topic__section_o4c_tgm_jrb} If NLU is enabled for your instance, you can view and manage translations by model and language. Navigate to AllConversational InterfacesVirtual AgentDesigner, and then click Manage languages. Choose a model and a language, and then you can do the following: * View translation status * Request translations * View or edit translations * Test translations {#localize-va-topic__ul_lmg_zbn_jrb} Click Manage NLU translations for easy access to the model management page in NLU Workbench. For more information, see [Localize Virtual Agent topics that use NLU topic discovery](https://servicenow-prod.fluidtopics.net/zYusU43jX_cF_5hd9yb~qg "Use the ServiceNow Localization Framework to manage the process of localizing Virtual Agent conversations that use Natural Language Understanding (NLU)."). * **[Enable NLU languages in Virtual Agent settings](https://servicenow-prod.fluidtopics.net/xK_32mye7Suo7k~nRHeZ3Q)** If you plan to use language-specific NLU models, you must enable the installed languages in the Supported NLU Languages list. A language is enabled if the Enabled column displays true. English language is enabled by default. * **[Localize Virtual Agent topics that use keyword topic discovery](https://servicenow-prod.fluidtopics.net/~K5mnaLHWPn4u0FOcHgGpQ)** Use the ServiceNow Localization Framework to manage the process of localizing Virtual Agent conversations and keywords. * **[Localize Virtual Agent topics that use NLU topic discovery](https://servicenow-prod.fluidtopics.net/zYusU43jX_cF_5hd9yb~qg)** Use the ServiceNow Localization Framework to manage the process of localizing Virtual Agent conversations that use Natural Language Understanding (NLU). * **[Edit translations for Virtual Agent topics](https://servicenow-prod.fluidtopics.net/Z0iVajBiCkaKGD6H~3sYWg)** A Virtual Agent admin user can edit and publish translations directly in Virtual Agent Designer. * **[Request bulk translations for multiple topics](https://servicenow-prod.fluidtopics.net/e7ro25Q_7crTP1JEbStirQ)** If you need to translate many Virtual Agent topics across multiple models at one time, you can use the \[sys_cs_topic\] table list view to request translations. * **[Authoring Virtual Agent conversations for localization](https://servicenow-prod.fluidtopics.net/CzWPuxxVaDG_EqVZu3EF~w)** Use localization methods in your Virtual Agent scripts to ensure that the content can be translated. Localization methods are designed to show the original text when no translation is found. These methods can be applied to your code before you have created translations. * **[Language support for NLU services](https://servicenow-prod.fluidtopics.net/PkObSqX_gxoaEXyNWO2KEA)** Entity extraction is supported on ServiceNow® NLU models for specific languages only. The remaining languages support intent matching only. If you are using IBM Watson Assistant, supported languages vary. * **[Localization roles for Virtual Agent](https://servicenow-prod.fluidtopics.net/FpQyON9fERKsdSntNsrdGg#localization-roles-va)** Assign localization roles according to a user's scope in the localization process. Users may request translations, fulfill translation requests, and edit translations, based on their role. * **[Virtual Agent translation tables](https://servicenow-prod.fluidtopics.net/gobnr_fakSqkjvCSeugF~g)** Virtual Agent uses the \[sys_translated_text\] and \[sys_ui_message\] tables to store translated text.