GETTING STARTED
Kore.ai XO Platform
Virtual Assistants Overview
Natural Language Processing (NLP)
Concepts and Terminology
Help & Learning Resources
Quick Start Guide
Accessing the Platform
Navigating the Kore.ai XO Platform
Building a Virtual Assistant
Using Workspaces
Release Notes
Current Version
Previous Versions
Deprecations
Request a Feature
CONCEPTS
Design
Storyboard
Overview
FAQs
Conversation Designer
Overview
Dialog Tasks
Mock Scenes
Dialog Tasks
Overview
Navigate Dialog Tasks
Build Dialog Tasks
Nodes & Connections
Overview
Node Types
Intent Node
Dialog Node
Entity Node
Entity Rules
Form Node
Confirmation Node
Message Nodes
Logic Node
Bot Action Node
Service Node
Webhook Node
Script Node
Process Node
Agent Transfer
Node Connections Setup
Context Object
Sub-Intent Scoping
User Prompts
Voice Call Properties
Dialog Task Management
Event Handlers
Supported Entity Types
Supported Company Names
Supported Colors
Knowledge Graph
Introduction
Knowledge Extraction
Build Knowledge Graph
Create Node Structure
Build the Graph
Add FAQs
Add FAQs from an Existing Source
Run a Task
Traits, Synonyms, and Stop Words
Manage Variable Namespaces
Update Knowledge Graph
Introduction
Move Question and Answers Between Nodes
Edit and Delete Terms
Edit Questions and Responses
Knowledge Graph Analysis
Knowledge Graph Import and Export
Prepare Data for Import
From a CSV File
From a JSON File
Importing Knowledge Graph
Exporting Knowledge Graph
Auto-Generate Knowledge Graph
Alert Tasks
Small Talk
Digital Skills
Overview
Digital Forms
Digital Views
Introduction
Widgets
Panels
Train
NLP Optimization
ML Engine
Overview
Model Validation
FM Engine
KG Engine
Traits Engine
Ranking and Resolver
Training Validations
NLP Configurations
NLP Guidelines
Intelligence
Introduction
Default Standard Responses
Contextual Memory
Contextual Intents
Interruption Management
Multi-intent Detection
Amending Entities
Default Conversations
Conversation Driven Dialog Builder
Sentinment Management
Tone Analysis
Test & Debug
Overview
Talk to Bot
Utterance Testing
Batch Testing
Conversation Testing
Health and Monitoring
Deploy
Channels
Publishing
Versioning
Analyze
Introduction
Overview Dashboard
Conversations Dashboard
Users Dashboard
Performance Dashboard
Custom Dashboards
Introduction
Custom Meta Tags
Create Custom Dashboard
NLP Insights
Conversations History
Conversation Flows
Analytics Dashboard Filters
Usage Metrics
Containment Metrics
Smart Bots
Universal Bots
Introduction
Universal Bot Definition
Universal Bot Creation
Training a Universal Bot
Universal Bot Customizations
Enabling Languages
Store
Manage Assistant
Plan & Usage
Overview
Usage Plans
Support Plans
Invoices
Authorization
Multilingual Virtual Assistants
Get Started
Supported Components & Features
Manage Languages
Manage Translation Services
Multiingual Virtual Assistant Behavior
Masking PII Details
Variables
Collections
IVR Settings
General Settings
Assistant Management
Manage Namespace
Data as Service
Data Table
Table Views
App Definitions
Sharing Data Tables or Views
HOW TOs
Build a Travel Planning Assistant
Travel Assistant Overview
Create a Travel Virtual Assistant
Design Conversation Skills
Create an ‘Update Booking’ Task
Create a Change Flight Task
Build a Knowledge Graph
Schedule a Smart Alert
Design Digital Skills
Configure Digital Forms
Configure Digital Views
Train the Assistant
Use Traits
Use Patterns
Manage Context Switching
Deploy the Assistant
Configure Agent Transfer
Use Bot Functions
Use Content Variables
Use Global Variables
Use Web SDK
Build a Banking 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
Composite Entities
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
Intent Scoping using Group Node
Analyze the Assistant
Create a Custom Dashboard
Use Custom Meta Tags in Filters
APIs & SDKs
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
BotKit SDK Tutorial - Blue Prism
Widget SDK Tutorial
Web SDK Tutorial
ADMINISTRATION
Introduction to Admin Console
Administration Dashboard
User Management
Add Users
Manage Groups
Manage Roles
Assistant Management
Enrollment
Invite Users
Send Bulk Invites
Import User Data
Synchronize Users from AD
Security & Control
Using Single-Sign On
Security Settings
Cloud Connector
Analytics
Billing
  1. Home
  2. Docs
  3. Virtual Assistants
  4. Builder
  5. Dialog Task
  6. Dialog Node

Dialog Node

The Dialog Node lets you start a new dialog task within an existing dialog task if the user intent changes.

For example, let us consider a travel assostant that has the following three dialog tasks: 

  • Flight Availability
  • Book a Flight
  • Book a Hotel

While handling a user’s intention to check for Flight Availability, your Virtual Assistant can detect a new user intention to Book a Flight. When this detection occurs, the VA can switch from checking flight availability to booking a flight, by invoking the dialog task that specifically handles the Book a Flight intent. 

Key Features

The key features of dialog nodes are listed below:

  • The ability to carry data from the current dialog task to the target dialog task as entity pre-assignments, described in a later section.
  • When a target dialog task is invoked, the current dialog flow begins at the root intent of the new dialog task. If you write transitions for the dialog node, then the flow returns to the source dialog task after completing the target. If you do not write transitions, the dialog task ends after executing the target dialog task. This differs from an optional User Intent node, where the dialog flow processes a related user intent and then continues in the same dialog task thereafter.

Add the Node

Setting up an dialog node in a dialog task involves the following steps:

  1. Open the dialog task that you want to add the node to..
  2. Add a Dialog node in the designated place. Read more about adding nodes..


Configure the Node

Component Properties

Once you place your node on the canvas, the dialog window is displayed with the Component Properties tab selected by default.

The configurations you set up or edit in the Component Properties tab reflect in all the dialog tasks that use this node.

  1. On the Component Properties tab, under the General Settings, you can modify
    1. The Name, 
    2. The Display Name,
    3. The Description.


NLP Properties

  1. From the NLP Properties tab, you can perform actions from the below-listed sections:
    1. Machine Learning settings to provide user utterances to improve the detection for this node.
    2. Patterns & Rules to capture this node if the user’s utterance contains these specific patterns.
    3. Bot Synonyms or related phrases for this node.
    4. Manage Context to control the flow of the conversation: 
      • Set Intent Preconditions: The intent will be detected only if any of the context tags specified as pre-conditions are available in the context at the time of intent detection.
      • Configure Context Output: Define the tags to be set in the context when this intent is initiated. Intent name is automatically set as output context by the system.


Connections Properties

Click the Connections tab and set the transition properties to determine the node in the dialog task to execute next. You can write the conditional statements based on the values of any Entity or Context Objects in the dialog task, or you can use intents for transitions. If you have defined the Transition Property as End of Dialog, then these settings are ignored.

Note: The conditions configured here are applicable only for this instance and will not affect the node when being used in any other dialog.

 

To set up component connection conditions, please follow the steps outlined in Adding IF-Else Conditions to Node Connections.


Instance Properties

Under the Instance Properties tab, you can configure the instance specific fields for the selected intent node. These settings are applicable only if you are connecting an existing intent node and only for the selected node instance and will not affect other dialog tasks that may invoke the node you are working with. Here is how to configure this section:

In the Entity Pre-Assignments section, you can pre-assign values from this session or node data to the entities required by the Dialog Task. Any remaining required values are handled by the sub-intent.  (see below for details) If you want to reset the values, you need to use the keyword “null”, spaces would be ignored by the platform.

In the Entity Post-Assignments section, there is a list of entities available in the current task with an option to add custom variables. These entities are assigned with values from the linked dialogs session data. For example, context.entities. lists the entities from the linked sub-dialog for selection. The values are assigned once the linked dialog execution is complete.

Important Notes:

  • This option is available only if the Transition Options is set to return to the current node on task completion.
  • Currently, there is a limitation when using URL entity types. URL values with http as opposed to https or without the www suffix will not work. If you want to reset the values, you need to use the keyword “null”, spaces would be ignored by the platform.

 

In the Transition Options section, you can define the flow to be followed once the task completes. You can choose from two options:

  • Initiate the linked Dialog Task, and once complete, return to this node. 
  • End the current task and initiate the linked Dialog Task..

Click Advanced Controls to set up the below-listed options:

  1. Interruptions Behavior
    • Use the task level Interruptions Behavior Setting: The VA refers to the Interruptions Behavior settings set at the dialog task level.
    • Customize for this node: By configuring this option you can customize the Interruptions Behavior settings for this node.Read the Interruption Handling and Context Switching article for more information.
  2. Custom Tags defines tags to build custom profiles of your bot conversations. See here for more. You can add tags for the following: 
    1. Message – Define custom tags to be added to the current message in the conversation.
    2. User – Define custom tags to be added to the user’s profile information.
    3. Session – Define custom tags to be added to the current conversation session.

Entity Pre-Assignments

You can pre-populate data for the destination dialog task by:

  • Adding values to the entity keys.
  • Adding additional custom keys and values to pass data from the current dialog task Context object to the destination dialog task as needed.

By default, entity nodes defined in the target dialog task are displayed as key/value pairs. You can then define values for associated entities or add custom keys and values as needed using session and context variables.

Transitioning from the source dialog task to the destination dialog task occurs at the runtime when the user input matches one of any linked dialog tasks. When you map more than one dialog task, you can define which dialog tasks are displayed to the end-users using conditional transitions.

When you call another dialog task, you want to carry information from the first dialog task to the next dialog task. For example, customer information collected in a Book a Flight dialog task is passed to the Book a Hotel dialog task.

You can use the mappedIntents variable in the Context object which holds the reference of the intent nodes as well as the context of the source dialog task as shown in the following JSON syntax:

{ 'title': 'title of the link', 'link':' url for the link' ,'postbackpayload': 'system generated payload'}

For example, a link to GetEmail in the Context object can be:

{

   "title":"GetEmail",

   "link":"https://app.collab.ai/wf/1.1/market/users/bots/st-bb1eb3da-cfa7-5244-b241-b5042d333e76/dialogue/dg-15fd2927-219c-5795-b038-5b830718bea7/execute?nodeId=message2&contextId=dcx-f9bae173-4d69-53e4-9aa7-21e89aae776d&intent=GetEmail",

   "postbackpayload":"MappedDialog_dc-f7b42932-dc06-53ac-92c0-1db706794f91_dg-15fd2927-219c-5795-b038-5b830718bea7_dcx-f9bae173-4d69-53e4-9aa7-21e89aae776d"

}

 

You can access and present these variables in a prompt message to a user to display a list of mapped dialog tasks with the link, or as a list of choices. You can pass the source dialog context to the target dialog task even if the source dialog task is no longer actively using the Context object.

The value for the postbackpayload key is generated by the Platform and is used in some channels, such as Facebook and Slack, which defines when a link or choice is made for a target dialog task.

For more information, refer to Using Session and Context Variables in Tasks and the Context Object.

Menu