Virtual Assistants Overview
Natural Language Processing (NLP)
Concepts and Terminology
Quick Start Guide
Accessing the Platform
Working with the Builder
Building a Virtual Assistant
Using Workspaces
Release Notes
Current Version
Previous Versions

Dialog Tasks
Dialog Builder
Node Types
Intent Node
Dialog Node
Entity Node
Form Node
Confirmation Node
Message Nodes
Logic Node
Bot Action Node
Service Node
Webhook Node
Script Node
Group Node
Agent Transfer
User Prompts
Voice Call Properties
Dialog Task Management
Connections & Transitions
Component Transition
Context Object
Event Handlers
Knowledge Graph
Knowledge Extraction
Build Knowledge Graph
Add Knowledge Graph to Bot
Create the Graph
Build Knowledge Graph
Add FAQs
Run a Task
Build FAQs from an Existing Source
Traits, Synonyms, and Stop Words
Manage Variable Namespaces
Move Question and Answers Between Nodes
Edit and Delete Terms
Edit Questions and Responses
Knowledge Graph Training
Knowledge Graph Analysis
Knowledge Graph Import and Export
Importing Knowledge Graph
Exporting Knowledge Graph
Creating a Knowledge Graph
From a CSV File
From a JSON file
Auto-Generate Knowledge Graph
Alert Tasks
Small Talk
Digital Skills
Digital Forms
ML Engine
Model Validation
FM Engine
KG Engine
Traits Engine
Ranking and Resolver
NLP Configurations
NLP Guidelines
Contextual Memory
Contextual Intents
Interruption Management
Multi-intent Detection
Amending Entities
Default Conversations
Sentinment Management
Tone Analysis
Test & Debug
Talk to Bot
Utterence Testing
Batch Testing
Conversation Testing
Conversations Dashboard
Performance Dashboard
Custom Dashboards
Meta Tags
Dashboards and Widgets
Conversation Flows
NLP Metrics
Containment Metrics
Usage Metrics
Smart Bots
Universal Bots
Universal Bot Definition
Universal Bot Creation
Training a Universal Bot
Universal Bot Customizations
Enabling Languages
Manage Assistant
Plan & Usage
Usage Plans
Support Plans
Multilingual Virtual Assistants
Masking PII Details
IVR Settings
General Settings
Assistant Management
Data Table
Table Views
App Definitions
Sharing Data Tables or Views

Build a Flight Status Assistant
Design Conversation Skills
Create a Sample Banking Assistant
Create a Transfer Funds Task
Create a Update Balance Task
Create a Knowledge Graph
Set Up a Smart Alert
Design Digital Skills
Configure Digital Forms
Configure Digital Views
Add Data to Data Tables
Update Data in Data Tables
Add Data from Digital Forms
Train the Assistant
Use Traits
Use Patterns for Intents & Entities
Manage Context Switching
Deploy the Assistant
Configure an Agent Transfer
Use Assistant Functions
Use Content Variables
Use Global Variables
Web SDK Tutorial
Widget SDK Tutorial
Analyze the Assistant
Create a Custom Dashboard
Use Custom Meta Tags in Filters

API Reference
API Introduction
API List
API Collection
koreUtil Libraries
SDK Reference
SDK Introduction
SDK Security
SDK Registration
Web Socket Connect and RTM
Using the BotKit SDK

Assistant Admin Console
Administration Dashboard
User Management
Add Users
Manage Groups
Manage Roles
Assistant Management
Invite Users
Send Bulk Invites
Import User Data
Synchronize Users from AD
Security & Compliance
Using Single-Sign On
Security Settings
Cloud Connector
  1. Home
  2. Docs
  3. Virtual Assistants
  4. Builder
  5. Dialog Task
  6. Grouping Nodes

Grouping Nodes

Grouping nodes are primarily used for defining a group of nodes and representing the same in the dialog canvas. Note that it is not a part of the dialog flow.

The Group Node can be used to improve the user experience with follow-ups, digressions, and amending entity values. For a use case example, refer here.


To add a Group node to the dialog task, follow the below steps:

  1. Open the Dialog Task where you want to add the Group node.
  2. Group the nodes. For steps in grouping nodes, refer here.
  3. You can rename, configure, or delete a group.
  4. Once created, you can not add or remove specific nodes from the group.
    • Any node you add is added outside the group.
    • Any node you delete is deleted from the entire dialog.
    • Deleting a group will not delete the nodes within the group from the dialog.

Configure Node

The Group Node functionality includes the following:

  • Scoping of Intents – ability to define the sub-intents to be made available when the user is waiting at any of the nodes in the group;
  • Sub-intent Training – the ability to train the sub-intent;
  • Sub-intents Properties – ability to define the behavior of the sub-intent.

For a use case example, with step-by-step instructions in achieving the intent scoping, refer here

Scoping of Intents

Using Group Nodes you can scope the sub-intents that are to be allowed to be identified from the user utterance and executed while the user is at one of the nodes within the group.

  1. Hover over the group you want to scope the intents for and click the settings (gear) icon.
  2. From the Group Node window, select Add Intent to add intents that should be part of this group’s scope.
  3. From the Add Intent window, select the intent to be scoped as sub-intent for this Group node. This would be the intent that a user might ask for when the conversation is at any of the nodes in this group. For example, asking “How is the weather at XYZ city” when prompted for the destination entity or asking for “Flight times” when prompted for the travel date.
  4. You can choose to add new sub-intents using the Create Intent button.
  5. Once added you can train, set behavioral properties and/or delete a scoped intent.

Training of Intents

Once added, each of the sub-intent can be trained for recognition within this group. This would ensure that the sub-intent is identified in the group’s context.

  1. From the Group settings page, select the sub-intent you want to train.
  2. You can train the sub-intent with the following:
    • Machine Learning – Add the user utterances that should identify this sub-intent. You can also use the NER approach to annotate entities in the utterances.
    • Patterns – Identify patterns in the user utterance related to this sub-intent
    • Rules – Define intent identification rules to trigger this intent
  3. You can also set the Intent Preconditions i.e. the sub-intent would get identified only when any of the preconditions defined are available in the context at the time of intent detection. These pre-conditions will be considered as instance levels and would take precedence over the component level pre-conditions.

Properties of Intents

The fulfillment section can be used to define the actions when this particular sub-intent is identified from the user input. It includes the following properties:

  • Context Variables – Set the key-value pairs to define the session or context variables to be updated when this sub-intent is identified.
    If you want to reset the values, you need to use the keyword “null”, spaces would be ignored by the platform.
  • Message – Optionally, define a message to be presented to the user when this sub-intent is identified. As with other responses, you can define the message as plain text, JavaScript format, specify, and set Voice Call Properties, where applicable.
  • Context Output – Define the context tags to be set when this intent is identified. The intent name is always set as output context by the system.
    If you want to reset the values, you need to use the keyword “null”, spaces would be ignored by the platform.
  • Transition Flow – Use this option to define how the dialog should resume after executing this sub-intent. Two behaviors you can define:
    • Jump To A Node – The dialog will resume from the node selected here.
    • Resume The Dialog – The dialog will resume from the node where this intent was identified.



Following are the changes in sub-intent behavior within a group

  • For every sub-intent identified, the context object will be updated with an array of objects with the identified sub-intent details with the latest on the top. The following information is captured:
    • Name of the sub-intent;
    • Entities that are identified along with the sub-intent;
    • Name of the group to which the sub-intent belongs, where applicable;
    • Name of the node at which the sub-intent is identified.
      "identifiedSubIntents": [
          "intent": "Change Destination",
          "entities": {
            "destcity": "Delhi"
          "groupName": "Entity Group",
          "identifiedAt": "to_date"
          "intent": "Weather Report",
          "groupName": "Entity Group",
          "identifiedAt": "destcity"
  • The intent would be executed if the sub-intent identified from the user utterance is within the group scope and all the input preconditions are satisfied and the transition flow directs to the concerned node.
  • The execution of sub-intent would involve:
    • Updation of the context variables as per the defined mapping
    • Setting the Output Context as per the defined mapping
    • Presenting the message to the user, if applicable
  • The current dialog execution should continue as per the transition flow defined
    • Jump to the specified node; or
    • Resume from the point where the sub-intent was identified.