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


---

# Create a Virtual Agent Bot Interconnect shell topic to call Virtual Agent secondary topics

# Create a Virtual Agent
Bot Interconnect shell topic to call Virtual Agent secondary
topics {#ariaid-title1}

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

To use ServiceNow®
Virtual Agent as a secondary bot with Virtual Agent
Bot Interconnect, you must create at least one shell topic in Bot Interconnect.

## Vorbereitungen

Create and publish topics in the secondary instance of ServiceNow Virtual Agent.

Enable synchronous or asynchronous mode on the secondary ServiceNow
Virtual Agent instance.

Role required: virtual_agent_admin or admin

## Warum und wann dieser Vorgang ausgeführt wird

There are two ways to integrate secondary Virtual Agent topics with Bot Interconnect:

* Create one Virtual Agent Bot Interconnect topic per secondary Virtual Agent topic.

  In case of NLU topics, each Bot Interconnect topic has the same name as the corresponding secondary Virtual Agent topic. For example, if you have two secondary Virtual Agent topics named order a drink and book a ticket, then you would create two Virtual Agent
  Bot Interconnect topics also named order a drink and book a ticket.

  In case of LLM topics, each Bot Interconnect topic has the same name and description as the corresponding secondary Virtual Agent topic.
* Map multiple secondary Virtual Agent topics to a single Virtual Agent Bot Interconnect topic. This scenario is applicable only for NLU topics.

  Create one Virtual Agent
  Bot Interconnect topic and name it accordingly. For example, SVA ordering issues. In this scenario, the secondary Virtual Agent topics are mapped to the Bot Interconnect shell topic as either keywords or utterances, depending on your method of topic discovery. So if you have two secondary Virtual Agent topics named order a drink and book a ticket, you would add both phrases to the Bot Interconnect topic as keywords or you would add them as utterances to the Bot Interconnect topic's corresponding intent.
{#create-va-topic-sn-primary-secondary-config__ul_y22_czw_ksb}

## Prozedur

1. Navigate to AllConversational InterfacesVirtual AgentDesigner.
2. [Create a topic](https://servicenow-prod.fluidtopics.net/l7I4pYbsOhW0Uro3rwhTCg "Use Virtual Agent Designer to create and modify Virtual Agent topics (conversations). Build your topic to meet a specific objective or goal, such as fulfilling a user's request or helping a user complete a task.") in your primary instance of Virtual Agent.  
   In case of NLU topics, include the secondary Virtual Agent topic names as either keywords or utterances in the corresponding Bot Interconnect intent. In case of LLM topics, the topic name and description of the Bot Interconnect topic should match the topic name and description of the secondary Virtual Agent topic.
3. On the Flow tab, drag a Topic Block utility node onto the canvas.
4. Select the node, and then fill in the form as follows:  
   {#create-va-topic-sn-primary-secondary-config__table_oq1_5px_ksbxxx__entry__2}

   | Property | Description |
   |-|-|
   | Topic Block | Select Bot Interconnect topic block for NLU topics and Bot Interconnect - LLM topic block for LLM topics. |
   | Action Name | * If the secondary bot is configured in synchronous mode, enter <kbd class="ph userinput">sn_va_bot_ic.va_api_bot_interconnect_integration_handler</kbd> * If the secondary bot is configured in asynchronous mode, enter <kbd class="ph userinput">sn_va_bot_ic.va_api_bot_interconnect_async_integration_handler</kbd> {#create-va-topic-sn-primary-secondary-config__ul_f3x_lyt_vxb} |
   | Action Type | Enter <kbd class="ph userinput">subflow</kbd>. |
   | Async Response Transformer | If the secondary bot is configured in asynchronous mode, enter <kbd class="ph userinput">sn_va_bot_ic.va_api_bot_interconnect_async_response_handler</kbd> |
   [Tabelle : 1. Topic Block Properties form]

   {#create-va-topic-sn-primary-secondary-config__table_oq1_5px_ksbxxx}
5. Click Save.
6. Click Publish.
**Vorheriges Thema:** [Create an auth token in the ServiceNow secondary instance](https://servicenow-prod.fluidtopics.net/pEyCHbPtRGVLM8QgRgcqhQ "To use ServiceNow Virtual Agent as a secondary bot with Virtual Agent Bot Interconnect, create an authentication token in the secondary instance.")  
**Nächstes Thema:** [Enable live agent connection on the primary instance](https://servicenow-prod.fluidtopics.net/ErBTiSkjvyWls56~V9nkSQ "Enable live agent connection on the primary instance to route an interaction to a live agent on the secondary instance.")