--- title: Create a Virtual Agent Bot Interconnect shell topic to call Virtual Agent secondary topics description: 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. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/conversational-interfaces/virtual-agent/create-va-topic-sn-primary-secondary-config.html release: australia product: Virtual Agent classification: virtual-agent topic_type: task last_updated: "2026-03-12" reading_time_minutes: 2 breadcrumb: [Using ServiceNow Virtual Agent as a secondary bot with Virtual Agent Bot Interconnect, Using Virtual Agent Bot Interconnect in your configuration, Build and deploy, Virtual Agent, Conversational Interfaces] --- # Create a Virtual Agent Bot Interconnect shell topic to call Virtual Agent secondary topics 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. ## Before you begin 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 ## About this task 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 Virtual Agent topic. For example, for two secondary topics, **order a drink** and **book a ticket**, create two Virtual Agent Bot Interconnect topics. Name the two new topics to match the secondary topics. 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. If you have two secondary Virtual Agent topics named **order a drink** and **book a ticket**, add both phrases to the Bot Interconnect topic as keywords, or as utterances to the Bot Interconnect topic's corresponding intent. ## Procedure 1. Navigate to **All** > **Conversational Interfaces** > **Assisant Designer**. 2. Select the **Asset library** tab. 3. [Create a topic](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/conversational-interfaces/virtual-agent/create-virtual-agent-topic.md) 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. 4. On the **Flow** tab, drag a Topic Block utility node onto the canvas. 5. Select the node, and then fill in the form as follows:
| 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 `sn_va_bot_ic.va_api_bot_interconnect_integration_handler` - If the secondary bot is configured in asynchronous mode, enter `sn_va_bot_ic.va_api_bot_interconnect_async_integration_handler` |
| Action Type | Enter `subflow`. |
| Async Response Transformer | If the secondary bot is configured in asynchronous mode, enter `sn_va_bot_ic.va_api_bot_interconnect_async_response_handler` |