---
sourceDocument: Australia Conversational Interfaces
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/conversational-interfaces

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Conversational Interfaces

ft:clusterId :

    - convint

bundleId :

    - convint

workflow :

    - Platform


---

# Using multiple active conversations in Virtual Agent

# Using multiple active conversations in Virtual Agent {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 min. de leitura

Virtual Agent features the ability to have multiple conversations at the same time, separated and directed by chosen context.

## Overview of Multiple active conversations for Virtual Agent {#c_multiple-active-conversations-va__section_d4p_xvg_xwb}

Virtual Agent messages commonly follow one conversation with a shared history that persists on all VA clients, and thus all portals. For example, if you're conversing with Virtual Agent in a Service Portal (SP) portal context, the same conversation is shown in an Employee Service Center (ESC) portal. The multiple active conversations feature expands the reach of Virtual Agent by eliminating the one-conversation limit. By configuring their Virtual Agent conversations based on context, customers can choose to share or restrict any or all content between concurrent conversations on differing portals.

Each Virtual Agent conversation is fully independent, with no overlap between chats. For example, a conversation in SP will be entirely different from ESC. Each conversation also has its own transcript. You must set up context values for Natural Language Understanding (NLU) chats, while Large Language Model (LLM) chats are automatically configured for multiple active conversations based on each portal. An administrator can activate an LLM assistant for each portal by
using guided setup configurations. (For more information on configuring Virtual Agent conversations, see [Conversational Interfaces Guided Setup](https://servicenow-prod.fluidtopics.net/z2uhO9T4v_O0hTwUl8P41g "Use the Conversational Interfaces Guided Setup to create a personalized setup process for just the conversational interface features you need. The Conversational Interfaces Guided Setup starts with a survey and creates a personalized task list based on your survey responses.").)

## Benefits of multiple active conversations {#c_multiple-active-conversations-va__section_gv5_cmy_wwb}

Previously, if a user was engaged in a conversation with a virtual agent, the chat would take place in a single context. Switching contexts involved a risk of exposing sensitive information by carrying over the entire chat history
to the other portal. For example, if you have an HR conversation in the HR portal, then brought up an IT request, the chat continues in the IT portal. However, this request also brings the HR conversation history into the IT portal
with it. Alternatively, admins can activate the skip_load_history system parameter to avoid exposure risk, but the initial conversation closes when the chat continues on the IT portal.

To exclude conversation history between portals, use the following procedure:  
1. Navigate to AllService PortalAgent Chat.
2. Select the Agent Chat Configuration for which you want to set the context value.
3. In the Server Script window, add the line <kbd class="ph userinput">skip_load_history: true</kbd> to load conversations without the conversation history.

{#c_multiple-active-conversations-va__ol_sdn_kzk_3xb}  
Nota:  
The script syntax may differ depending on the configuration.

The multiple active conversations feature bypasses the skip_load_history method, and enables continuous engagement with Virtual Agent chat, by routing selected notifications and topics to their configured contexts only. Users don't need scripting or extensive customization, and they can conduct conversations without interruption or
information exposure in the wrong context. With portals and notification contexts aligned, users receive information appropriate to their context, including incident updates and other relevant data.

## Considerations for using multiple active conversations {#c_multiple-active-conversations-va__section_t3r_331_xwb}

Implementing multiple active conversations should happen in the following order: Admins should define portal consumer context values, set or update a default context, activate the multiple active conversations system, and finally,
configure notifications sent to portals. However, if the delivered Service Portal context is sufficient, admins can skip configuring and setting values.

Topics can be created within a portal context. If the portal context maps to consumer account context, then topics map to consumer account contexts.
* **[Set NLU portal consumer context values for multiple active conversations](https://servicenow-prod.fluidtopics.net/czGgE~Eoz6lumpmbrT8x8A)**   
  Use context values to determine which portals receive certain messages and notifications for users in that portal.
* **[Set a default NLU context value for multiple active conversations](https://servicenow-prod.fluidtopics.net/ePJGNseCkvy18Uj_7L_RXQ)**   
  Use consumer account context values to define where Virtual Agent messages are directed by default when using the multiple active conversations feature.
* **[Activate multiple active conversations in Virtual Agent](https://servicenow-prod.fluidtopics.net/U8f9tKCt6lS5s6nM7IVWVA)**   
  Use the multiple active conversations system, in combination with defined context values and a default portal, to handle concurrent conversations with Virtual Agent.
* **[Route Virtual Agent NLU notifications through multiple portals](https://servicenow-prod.fluidtopics.net/rXsLe5yOVNZpZZFaG_mACA)**   
  Send notifications and other Virtual Agent messages through as many portals as desired.