GETTING STARTED
Kore.ai XO Platform
Virtual Assistants Overview
Natural Language Processing (NLP)
Concepts and Terminology
Quick Start Guide
Accessing the Platform
Navigating the Kore.ai XO Platform
Building a Virtual Assistant
Help & Learning Resources
Release Notes
Current Version
Recent Updates
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
Node Types
Overview
Intent Node
Dialog Node
Dynamic Intent Node
GenAI Node
GenAI Prompt
Entity Node
Form Node
Confirmation Node
Message Nodes
Logic Node
Bot Action Node
Service Node
Webhook Node
Script Node
Process Node
Agent Transfer
Node Connections
Node Connections Setup
Sub-Intent Scoping
Entity Types
Entity Rules
User Prompts or Messages
Voice Call Properties
Knowledge AI
Introduction
Knowledge Graph
Introduction
Terminology
Build a Knowledge Graph
Manage FAQs
Knowledge Extraction
Import or Export Knowledge Graph
Prepare Data for Import
Importing Knowledge Graph
Exporting Knowledge Graph
Auto-Generate Knowledge Graph
Knowledge Graph Analysis
Answer from Documents
Alert Tasks
Small Talk
Digital Skills
Overview
Digital Forms
Digital Views
Introduction
Widgets
Panels
Session and Context Variables
Context Object
Intent Discovery
Train
NLP Optimization
ML Engine
Overview
Model Validation
FM Engine
KG Engine
Traits Engine
Ranking and Resolver
Training Validations
NLP Configurations
NLP Guidelines
LLM and Generative AI
Introduction
LLM Integration
Kore.ai XO GPT Module
Prompts & Requests Library
Co-Pilot Features
Dynamic Conversations Features
Intelligence
Introduction
Event Handlers
Contextual Memory
Contextual Intents
Interruption Management
Multi-intent Detection
Amending Entities
Default Conversations
Conversation Driven Dialog Builder
Sentinment Management
Tone Analysis
Default Standard Responses
Ignore Words & Field Memory
Test & Debug
Overview
Talk to Bot
Utterance Testing
Batch Testing
Conversation Testing
Conversation Testing Overview
Create a Test Suite
Test Editor
Test Case Assertion
Test Case Execution Summary
Glossary
Health and Monitoring
NLP Health
Flow Health
Integrations
Actions
Actions Overview
Asana
Configure
Templates
Azure OpenAI
Configure
Templates
BambooHR
Configure
Templates
Bitly
Configure
Templates
Confluence
Configure
Templates
DHL
Configure
Templates
Freshdesk
Configure
Templates
Freshservice
Configure
Templates
Google Maps
Configure
Templates
Here
Configure
Templates
HubSpot
Configure
Templates
JIRA
Configure
Templates
Microsoft Graph
Configure
Templates
Open AI
Configure
Templates
Salesforce
Configure
Templates
ServiceNow
Configure
Templates
Stripe
Configure
Templates
Shopify
Configure
Templates
Twilio
Configure
Templates
Zendesk
Configure
Templates
Agents
Agent Transfer Overview
Custom (BotKit)
Drift
Genesys
Intercom
NiceInContact
NiceInContact(User Hub)
Salesforce
ServiceNow
Configure Tokyo and Lower versions
Configure Utah and Higher versions
Unblu
External NLU Adapters
Overview
Dialogflow Engine
Test and Debug
Deploy
Channels
Publishing
Versioning
Analyze
Introduction
Dashboard Filters
Overview Dashboard
Conversations Dashboard
Users Dashboard
Performance Dashboard
Custom Dashboards
Introduction
Custom Meta Tags
Create Custom Dashboard
Create Custom Dashboard Filters
LLM and Generative AI Logs
NLP Insights
Task Execution Logs
Conversations History
Conversation Flows
Conversation Insights
Feedback Analytics
Usage Metrics
Containment Metrics
Universal Bots
Introduction
Universal Bot Definition
Universal Bot Creation
Training a Universal Bot
Universal Bot Customizations
Enabling Languages
Store
Manage Assistant
Team Collaboration
Plan & Usage
Overview
Usage Plans
Templates
Support Plans
Invoices
Authorization
Conversation Sessions
Multilingual Virtual Assistants
Get Started
Supported Components & Features
Manage Languages
Manage Translation Services
Multiingual Virtual Assistant Behavior
Feedback Survey
Masking PII Details
Variables
Collections
IVR Settings
General Settings
Assistant Management
Manage Namespace
Data
Overview
Data Table
Table Views
App Definitions
Data as Service
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
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
Migrate External Bots
Google Dialogflow Bot
APIs & SDKs
API Reference
API Introduction
Rate Limits
API List
koreUtil Libraries
SDK Reference
SDK Introduction
Web SDK
How the Web SDK Works
SDK Security
SDK Registration
Web Socket Connect and RTM
Tutorials
Widget SDK Tutorial
Web SDK Tutorial
BotKit SDK
BotKit SDK Deployment Guide
Installing the BotKit SDK
Using the BotKit SDK
SDK Events
SDK Functions
Tutorials
BotKit - Blue Prism
BotKit - Flight Search Sample VA
BotKit - Agent Transfer
  1. Docs
  2. Virtual Assistants
  3. Builder
  4. Dialog Task
  5. Dynamic Intent Node

Dynamic Intent Node

The Dynamic Intent node lets you dynamically trigger any of the flows in the bot by defining the intent’s display name using variables. The target intent can be either a Dialog Task or a FAQ. You can use this node to proactively disambiguate an intent and choose different intents based on the user or conversation context.

In the case of linked bots associated with Universal Bots, you can also use this node to trigger flows present in any other linked bots of the corresponding Universal Bot. This feature allows you to invoke reusable or utility flows in one linked bot from another, for example, user authentication, OTP verification, etc. It simplifies switching between tasks in different linked bots of a Universal Bot.

Key Points

  • The target task can be within the current bot, or if connected to a Universal Bot, it can be in any of the other linked bots of the Universal Bot.
  • You can define the display name of the target intent using Context or Environment variables.
  • The Platform resolves the context or environment variable during runtime to identify the target intent.
  • If the variable fails to provide a valid Dialog Task or FAQ Name, the current task will be discarded, and the Task Failure Event will be triggered.

Setting up a Dynamic Intent node in a dialog task involves adding the node at the appropriate location in the dialog flow and configuring various properties of the node, as explained below.

Add the Node

  1. Open the dialog task to which you want to add the dynamic intent node.
  2. Use the “+” button next to the node under which you want to add the dynamic intent node, choose Dynamic Intent, and then click New Dynamic Intent.
    The Dynamic Intent window is displayed with the Component Properties tab selected by default.
    Dynamic Intent Node

Configure the Node

Component Properties

The settings made within this section affect this node across all instances in all dialog tasks.
Node's Component Properties

General Settings

In this section, you can provide Name, Display Name, and Description for the node. The node name cannot contain spaces.

Target Intent Name

In this section, you can define the display name of the intent (Dialog Task or FAQ) that you want to switch to. Use context variable or environment variable to define the display name as follows:

  • Context Variable – {{context.targetTaskName}}
  • Environment Variable – {{env.targetTaskName}}
    Where targetTaskName is a variable that contains the target intent’s display name as the value.

Example Scenarios:

  • If the target intent is present within the same bot: The variable must use a valid display name of an intent within the bot. The target intent can be associated with a Dialog Task or FAQ. Consider the following intent display names – reset_password, apply_paid_leave, or how often should I reset my password. In the Target Intent Name field, you can use either the display name reset_password as static text or the context variable {{context.targetTaskName}} where the variable targetTaskName contains the display name reset_password as the value.
  • If the target intent is present in a different linked bot (the target bot and the current bot are linked to a common Universal Bot): The variable must refer to the target linked bot name and the display name of the intent within the target bot, separated by a ‘dot’. Consider the following intent display names – HRBot.apply_paid_leave, ITBot.reset_password, or ITBot.how often should I reset my password. In the Target Intent Name field, you can use either the display name ITBot.reset_password as static text or the context variable {{context.targetTaskName}} where the variable targetTaskName contains the display name ITBot.reset_password as the value.

Target Intent Error Transition

In this section, you can select the flow of execution to be followed in case the Platform fails to resolve the defined target intent:

  • Ignore this node and continue with the execution of the following node in the transition; this option is selected by default.
  • Trigger Task failure event

Instance Properties

Under the Instance Properties tab, you can configure the instance-specific fields for this Dynamic Intent intent node. These settings are applicable only for this instance and will not affect any other instances of this node.
Node's Instance Properties

Entity Pre-Assignments

In this section, you can assign values for the entities or context variables of the target dialog task. Provide the name of the entity or context variable of the target intent and define the value to be assigned from the current task’s context.

Key/Value should prefix with context for getting values from the context object.
Key: Entity name
Value: context.path of the value which needs to be assigned to the entity

Note: This setting is ignored if the target intent is FAQ.

Entity Post-Assignments

In this section, you can assign values for the entities and context variables of the current task after returning from the target task. Provide the name of the entity or context variable of the current task and define the value to be assigned from the target task’s context.

Key/Value should prefix with context for getting values from the context object.
Key: Entity name
Value: context.path of the value which needs to be assigned to the entity

Transition Options

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

  • Initiate the target intent execution from within the current context
  • End the current task and initiate the target task

Advanced Controls

In this section, you can add Custom Meta Tags to the conversation flow to profile VA-user conversations and derive business-critical insights from usage and execution metrics. You can add tags for the following:

  • Message – Define custom tags to be added to the current message in the conversation.
  • User – Define custom tags to be added to the user’s profile information.
  • Session – Define custom tags to be added to the current conversation session.

For more information on custom tags, see Custom Meta Tags.

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 conditional statements based on the values of any Entity or Context Objects in the dialog task, or you can use intents for transitions. See Adding IF-Else Conditions to Node Connections for a detailed setup guide.
Node's Connections

Note: These conditions apply only for this instance and will not affect this node when used in any other dialog.

Dynamic Intent Node

The Dynamic Intent node lets you dynamically trigger any of the flows in the bot by defining the intent’s display name using variables. The target intent can be either a Dialog Task or a FAQ. You can use this node to proactively disambiguate an intent and choose different intents based on the user or conversation context.

In the case of linked bots associated with Universal Bots, you can also use this node to trigger flows present in any other linked bots of the corresponding Universal Bot. This feature allows you to invoke reusable or utility flows in one linked bot from another, for example, user authentication, OTP verification, etc. It simplifies switching between tasks in different linked bots of a Universal Bot.

Key Points

  • The target task can be within the current bot, or if connected to a Universal Bot, it can be in any of the other linked bots of the Universal Bot.
  • You can define the display name of the target intent using Context or Environment variables.
  • The Platform resolves the context or environment variable during runtime to identify the target intent.
  • If the variable fails to provide a valid Dialog Task or FAQ Name, the current task will be discarded, and the Task Failure Event will be triggered.

Setting up a Dynamic Intent node in a dialog task involves adding the node at the appropriate location in the dialog flow and configuring various properties of the node, as explained below.

Add the Node

  1. Open the dialog task to which you want to add the dynamic intent node.
  2. Use the “+” button next to the node under which you want to add the dynamic intent node, choose Dynamic Intent, and then click New Dynamic Intent.
    The Dynamic Intent window is displayed with the Component Properties tab selected by default.
    Dynamic Intent Node

Configure the Node

Component Properties

The settings made within this section affect this node across all instances in all dialog tasks.
Node's Component Properties

General Settings

In this section, you can provide Name, Display Name, and Description for the node. The node name cannot contain spaces.

Target Intent Name

In this section, you can define the display name of the intent (Dialog Task or FAQ) that you want to switch to. Use context variable or environment variable to define the display name as follows:

  • Context Variable – {{context.targetTaskName}}
  • Environment Variable – {{env.targetTaskName}}
    Where targetTaskName is a variable that contains the target intent’s display name as the value.

Example Scenarios:

  • If the target intent is present within the same bot: The variable must use a valid display name of an intent within the bot. The target intent can be associated with a Dialog Task or FAQ. Consider the following intent display names – reset_password, apply_paid_leave, or how often should I reset my password. In the Target Intent Name field, you can use either the display name reset_password as static text or the context variable {{context.targetTaskName}} where the variable targetTaskName contains the display name reset_password as the value.
  • If the target intent is present in a different linked bot (the target bot and the current bot are linked to a common Universal Bot): The variable must refer to the target linked bot name and the display name of the intent within the target bot, separated by a ‘dot’. Consider the following intent display names – HRBot.apply_paid_leave, ITBot.reset_password, or ITBot.how often should I reset my password. In the Target Intent Name field, you can use either the display name ITBot.reset_password as static text or the context variable {{context.targetTaskName}} where the variable targetTaskName contains the display name ITBot.reset_password as the value.

Target Intent Error Transition

In this section, you can select the flow of execution to be followed in case the Platform fails to resolve the defined target intent:

  • Ignore this node and continue with the execution of the following node in the transition; this option is selected by default.
  • Trigger Task failure event

Instance Properties

Under the Instance Properties tab, you can configure the instance-specific fields for this Dynamic Intent intent node. These settings are applicable only for this instance and will not affect any other instances of this node.
Node's Instance Properties

Entity Pre-Assignments

In this section, you can assign values for the entities or context variables of the target dialog task. Provide the name of the entity or context variable of the target intent and define the value to be assigned from the current task’s context.

Key/Value should prefix with context for getting values from the context object.
Key: Entity name
Value: context.path of the value which needs to be assigned to the entity

Note: This setting is ignored if the target intent is FAQ.

Entity Post-Assignments

In this section, you can assign values for the entities and context variables of the current task after returning from the target task. Provide the name of the entity or context variable of the current task and define the value to be assigned from the target task’s context.

Key/Value should prefix with context for getting values from the context object.
Key: Entity name
Value: context.path of the value which needs to be assigned to the entity

Transition Options

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

  • Initiate the target intent execution from within the current context
  • End the current task and initiate the target task

Advanced Controls

In this section, you can add Custom Meta Tags to the conversation flow to profile VA-user conversations and derive business-critical insights from usage and execution metrics. You can add tags for the following:

  • Message – Define custom tags to be added to the current message in the conversation.
  • User – Define custom tags to be added to the user’s profile information.
  • Session – Define custom tags to be added to the current conversation session.

For more information on custom tags, see Custom Meta Tags.

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 conditional statements based on the values of any Entity or Context Objects in the dialog task, or you can use intents for transitions. See Adding IF-Else Conditions to Node Connections for a detailed setup guide.
Node's Connections

Note: These conditions apply only for this instance and will not affect this node when used in any other dialog.
메뉴