---
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


---

# Edit translations for Virtual Agent topics

# Edit translations for Virtual Agent topics {#ariaid-title1}

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

A Virtual Agent admin user can edit and publish translations directly
in Virtual Agent Designer.

## Vorbereitungen

Hinweis:  
An updated Assistant Designer Asset library user interface is available when you install Now Assist in Virtual Agent and turn on the Now Assist Topics skill. This content assumes that you have activated this skill and can see the list view. If this skill is not activated, you see the legacy UI and topics page. For more information, see [Virtual Agent Designer legacy topics page](https://servicenow-prod.fluidtopics.net/ESoB~Pc7f01EoEYPSsLxAg "The Virtual Agent Designer legacy home page lists cards for available topics in your instance.").

Role required: virtual_agent_admin or admin

## Prozedur

1. Do one of the following:
   * Navigate to AllConversational InterfacesVirtual AgentDesigner, open a published topic, and then select the Languages tab.
   * (NLU only) Navigate to AllConversational InterfacesVirtual AgentDesigner, and slide the discovery type toggle switch to NLU/keyword. Select Manage languages from Resources, and then choose a model, language, and topic.
   {#edit-translations-va-topics__choices_cph_n5z_zqb}
2. In the Topic translations column, select Edit.  
   The Edit Translations form opens.
3. On the Edit Translations form, you can do any of the following:
   * Unlock fields and enter translations directly on the form.
   * If it is configured in the Localization Framework, use machine translation to fill in the fields.

     To set up machine translation,
     see [Create a
     translator configuration](https://www.servicenow.com/docs/access?context=create-custom-translator&version=australia&pubname=australia-platform-administration&ft:locale=en-US).
   * Export files to send to a third party for translation.Select Export Source File, and then choose the file type. Select Export File to begin the download.

   * Import translated files received from a translation service.From the
     Export Source file list, select Import Translated File.

   {#edit-translations-va-topics__choices_lmy_3hp_3pb}
4. When translations are ready to publish, select Publish Translations.

## Ergebnisse

Once translations are published, they are made available to Virtual Agent topics that use keywords dynamically.

If your topic uses Natural Language Understanding (NLU), train your localized models. You may also need to map them to the topic. Then test and publish your localized models to ensure that native speakers can access localized intents. For more information, see [Map a topic to a secondary NLU model](https://servicenow-prod.fluidtopics.net/fYWh14NFTYRcB6MBQ6LEnw "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.") and [Test topic and NLU model translations](https://servicenow-prod.fluidtopics.net/mwbWjUVc8qVLsok1IKcCvw "Test a translated Virtual Agent topic and the localized NLU model to ensure that it works as expected in a conversation.").