{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":4905,"path":"conversational-interfaces/virtual-agent/create-primary-va-topic-ms-pva.md","title":"Create a Virtual Agent Bot Interconnect shell topic to call Microsoft Power Virtual Agents topics","bundle":null,"doc_type":null,"release":"australia","body":"\n# Create a Virtual Agent Bot Interconnect shell topic to call Microsoft Power Virtual Agents topics\n\nTo access topics in the Power Virtual Agents secondary bot, you must create at least one Virtual Agent Bot Interconnect topic.\n\n## Before you begin\n\nCreate one or more topics in Microsoft Power Virtual Agents.\n\n[Add the Direct Line secret key to your Virtual Agent Bot Interconnect instance](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/conversational-interfaces/virtual-agent/add-dl-secret-key-sn-instance.md).\n\nRole required: virtual\\_agent\\_admin or admin\n\n## About this task\n\nThere are two ways to integrate Microsoft Power Virtual Agents topics with Bot Interconnect:\n\n-   Create one Virtual Agent Bot Interconnect topic per Power Virtual Agents topic.\n\n    For NLU/Keyword topics, each Virtual Agent topic is named the same a single Power Virtual Agents topic. For example, you have two Power Virtual Agents topics, **order a drink** and **book a ticket**. Create two Virtual Agent topics with the same names.\n\n    For LLM topics, each Bot Interconnect topic has the same name and description as the corresponding Power Virtual Agents topic.\n\n-   For NLU/Keyword topics, pap multiple Power Virtual Agents topics to a single Virtual Agent Bot Interconnect topic.\n\n    Create one Virtual Agent topic for your Power Virtual Agents topics and name it accordingly. For example, **PVA ordering issues**. The Power Virtual Agents topics map to the topic as keywords or utterances, depending on topic discovery. For example, if you have two Power Virtual Agents topics, **order a drink** and **book a ticket**, add both phrases to the topic as keywords or as utterances to the topic's corresponding intent.\n\n\n## Procedure\n\n1.  Navigate to **All** &gt; **Conversational Interfaces** &gt; **Assistant Designer**.\n\n2.  Select the **Asset library** tab.\n\n3.  Set the topic discovery toggle switch to **LLM** or **NLU/Keyword**, depending on which type you want to create.\n\n4.  [Create a topic](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/conversational-interfaces/virtual-agent/create-virtual-agent-topic.md) for your Power Virtual Agents topics.\n\n    In case of NLU topics, include the Power Virtual Agents topic names as either keywords or utterances in the corresponding ServiceNow Virtual Agent 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 Power Virtual Agents topic.\n\n5.  On the **Flow** tab, drag a Topic Block utility node onto the canvas.\n\n6.  Select the node, and then fill in the form as follows:\n\n<table id=\"table_oq1_5px_ksb\"><thead><tr><th>\n\nProperty\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nTopic Block\n\n</td><td>\n\nSelect **Bot Interconnect** topic block for NLU topics and **Bot Interconnect - LLM** topic block for LLM topics.\n\n</td></tr><tr><td>\n\nAction Name\n\n</td><td>\n\nEnter: `sn_va_bot_ic.direct_line_bot_interconnect_integration_handler`\n\n</td></tr><tr><td>\n\nAction Type\n\n</td><td>\n\nEnter `subflow`.\n\n</td></tr><tr><td>\n\nAdditional Params \\(String\\)\n\n</td><td>\n\nFollow these steps:1.  Select the script icon \\[Omitted image \"icon-script.png\"\\] Alt text: Script icon..\n2.  In the Additional Params \\(String\\) window, add this code:\n\n    ```\n(function execute() {\n    return JSON.stringify({'quick': false});\n})()\n    ```\n\n3.  Select **Save**.\n\n\n</td></tr></tbody>\n</table>7.  Select **Save**.\n\n8.  Select **Publish**.\n\n\n## What to do next\n\nTest your configuration. You can execute the topics that are available in the secondary bot from channels where Bot Interconnect is deployed.\n\n**Note:** Conversations always remain open in Power Virtual Agents.\n\n**Parent Topic:**[Using Microsoft Power Virtual Agents as a secondary bot with Virtual Agent Bot Interconnect](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/conversational-interfaces/virtual-agent/using-va-api-ms-powerva.md)\n\n**Previous topic:**[Add the Direct Line secret key to your Virtual Agent Bot Interconnect instance](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/conversational-interfaces/virtual-agent/add-dl-secret-key-sn-instance.md)\n\n**Next topic:**[Using ServiceNow Virtual Agent as a secondary bot with Virtual Agent Bot Interconnect](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/conversational-interfaces/virtual-agent/using-sn-secondary-bot-with-sn-primary.md)\n\n"}}