---
sourceDocument: Yokohama Conversational Interfaces
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/conversational-interfaces

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Conversational Interfaces

ft:clusterId :

    - convint

bundleId :

    - convint

workflow :

    - Platform


---

# Set a default NLU context value for multiple active conversations

# Set a default NLU context value for multiple active conversations {#ariaid-title1}

Release version: Yokohama  
Updated January 30, 2025  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Use consumer account context values to define where Virtual Agent messages are directed by default when using the multiple active conversations feature.

## Before you begin

Define values for portal consumer contexts. For more information, see [Set NLU portal consumer context values for multiple active conversations](https://servicenow-prod.fluidtopics.net/ROeW81a2XLm3Fa0EdKv4ig "Use context values to determine which portals receive certain messages and notifications for users in that portal.").

Configure context values that align Virtual Agent and your portals. See [Configure Agent Chat in a portal](https://www.servicenow.com/docs/access?context=configure-va-in-sp&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US) for more information.

Role required: virtual_agent_admin or admin.

## About this task

You can create as many context values as you need. One consumer account context must always be set to <kbd class="ph userinput">Yes</kbd> to provide a default content area. The default acts as a fallback for the chat widget when the
portal setup doesn't include context. The default is also used as the context for mobile conversations, which only support one conversation at a time. Context values are stored in the Conversation Consumer Account Context
\[sys_cs_consumer_account_context\] table. (The CS Consumer Account \[sys_cs_consumer_account\] table [Installed with Virtual Agent](https://servicenow-prod.fluidtopics.net/6ZiD4gntJR1iODqLh3Vd8Q "Various types of components are installed with activation of the Glide Virtual Agent [com.glide.cs.chatbot] plugin, including tables and user roles.") shows whether third-party users in your instance have a context assigned to them.)  
Note:  
These instructions are for configuring Natural Language Understanding (NLU) conversations. Large Language Model (LLM) conversations are configured for multiple active conversations based on portals, with no configuration necessary.

## Procedure

1. Navigate to AllConversational InterfacesSettingsVirtual Agent.
2. Under multiple active conversations, select View settings.  
   Note:  
   The delivered default value for consumer account contexts is `sp`.
3. Select New.
4. On the form, fill in the fields.  
   {#t_set-default-context-value-multiple-active-conversations__table_zxw_5d2_bxb__entry__2}

   | Field | Description |
   |-|-|
   | Name | Name of the context value (also used as reference in the backend). |
   | Short Description | Description for the context (displayed on the Conversational Interfaces card when the default value is shown). |
   | Is Default Consumer Account Context | Option to make this context value the default for your Virtual Agent conversations. Note: Only one consumer account context can be set as the default. Setting a new one as a default automatically resets the last context to `False`. |
   [Table 1. Consumer Account Contexts form]

   {#t_set-default-context-value-multiple-active-conversations__table_zxw_5d2_bxb}
5. Select Save.

## What to do next

Activate the multiple active conversations system. For more information, see [Activate multiple active conversations in Virtual Agent](https://servicenow-prod.fluidtopics.net/t2oyrtz~~ItoFVhgBYhisA "Use the multiple active conversations system, in combination with defined context values and a default portal, to handle concurrent conversations with Virtual Agent.").

*[\>]: and then