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


---

# Map a topic to a secondary NLU model

# Map a topic to a secondary NLU model {#ariaid-title1}

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

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.

## 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.").

If you're using ServiceNow
NLU, review [NLU model mapping in Virtual Agent Designer](https://servicenow-prod.fluidtopics.net/XsfyPGIW5NlsEIZTrrLtXQ "ServiceNow model groups help you to manage the localization of both topics and Natural Language Understanding (NLU) models more easily. You can map Virtual Agent topics to a new or existing model group directly from Virtual Agent.") for an understanding of NLU model groups.

If necessary, add secondary languages to the model group in NLU Workbench to create language-specific versions of the model. 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).

Role required: virtual_agent_admin or admin

## Warum und wann dieser Vorgang ausgeführt wird

If you select a secondary model for a language that is part of a different model group, the mapping changes for the entire topic. Secondary models must be part of the same model group as the primary language. You can select a different model and intent for a secondary language when it is the only language in the model (and therefore the primary language).  
Abbildung : 1. Updated model group mappings message ![A mapping change alert says, "We updated mappings for these languages: English, French, German, Spanish."]()  
Abbildung : 2. Topic mapped to a model group with primary and secondary languages

For more information, see [NLU model mapping in Virtual Agent Designer](https://servicenow-prod.fluidtopics.net/XsfyPGIW5NlsEIZTrrLtXQ "ServiceNow model groups help you to manage the localization of both topics and Natural Language Understanding (NLU) models more easily. You can map Virtual Agent topics to a new or existing model group directly from Virtual Agent.").

## Prozedur

1. Navigate to AllConversational InterfacesVirtual AgentDesigner.
2. Slide the discovery type toggle switch to NLU/keyword toggle, and open a topic.
3. Open the Languages tab, and then select the NLU language mapping tab.  
   The first column is the NLU mapping that is based on your current session language. For example, if you're using English, the first column is English.
4. In the Language to edit list, select the language to map.  
   The languages listed are based on the NLU languages that you enabled in Virtual Agent settings. After you select a language, a column displays in the Intent mapping section and, if applicable, in the Entity mapping section. For example, if you select Français, a French language column displays.

5. Update the Intent mapping section.
   1. In the Model row, select an NLU model for the language that you selected.
   2. In the Intent row, select an NLU intent for the language that you selected.
   {#map-nlu-language-model__substeps_vpj_tp2_lpb}
6. If applicable, update the Entity mapping section.  
   For each language, map an entity from the model to an input node in the topic. In a conversation, these nodes are populated automatically with the entity value.
7. Click Save.

## Nächste Maßnahme

[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.")