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. Home
  2. Docs
  3. Virtual Assistants
  4. Builder
  5. Dialog Task
  6. User Intent Node

User Intent Node

As a bot developer, you typically create a task to resolve one primary user intent. Yet, user conversations can branch into related intents (follow-up or sub-intents) as a part of the primary intent.

Let us take a look into this sample conversation for a flight booking assistant:

VA: Hi, how may I help you today?
User: Hey, what flight options have I got from LA to NYC?
VA: Sure, let me know the travel date.
User: Wait a minute, will it rain in NYC this Sunday?

The primary intent of this conversation is to book a flight ticket. But the user wants to know the weather forecast before completing the booking, which is a valid use case.

User Intent Nodes help you add a root intent, a follow-up or sub-intents to your dialog tasks. The flow for a follow-up intent is built within the same dialog task using transitions, and cannot be linked to external tasks. When the execution of a follow-up intent is completed, the conversation flow continues within the same dialog tasks based on the transitions you add.

Note: To start a new Dialog Task from an existing one, you can use the Dialog Task nodes.

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

Add the Node

  1. Open the dialog task to which you want to add the user intent node.
  2. Add a user intent node in the designated place. For steps on adding nodes, please read more here.
  3. The user intent window is displayed with the Component Properties tab selected by default.

Configure the Node

Component Properties

Note: The configurations you set up or edit in the Component Properties tab reflects in all the dialog tasks that use this node. These settings are the same for Intent and Sub-intent nodes.
  1. On the Component Properties tab, under the General Settings, you can modify
    1. The Name,
    2. The Display Name,
    3. The Description.

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.

You can add tags to build custom profiles of your VA’s conversations. You can define a key and a value for each of 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.

Here is an example of a dialog task that is connected as a subintent in a more complex one.

NLP Properties

The NLP Properties are related to the underlying intent associated with a dialog. You can add these properties here or in the NLP – Training section. They are used to train the machine learning model to help improve intent identification for the dialog task. These properties are not used to execute this node in the flow.

To improve intent identification for the dialog task, add or define the following properties: 

  1. Machine Learning settings to provide user utterances to improve the detection of this intent. Learn more.
  2. Patterns and Rules to capture this intent if the user’s utterance contains these specific patterns or matches the rule. Learn more.
  3. Bot Synonyms or related phrases for the user intent. Learn more.
  4. Manage Context tags as preconditions to identify the intent and define the output context to be set when this task is initiated. Learn more.

Connections Properties

Click the Connections tab and set the transition properties to determine the node in the dialog task to execute next.

Primary Intent nodes only allow you to select the next node to trigger.

If the Intent node you are working with does not represent the primary intent within the dialog task (if it follows another node), 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. For details on how to work with connection conditions, please see Adding IF-Else Conditions to Node Connections.

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

User Intent Node

As a bot developer, you typically create a task to resolve one primary user intent. Yet, user conversations can branch into related intents (follow-up or sub-intents) as a part of the primary intent.

Let us take a look into this sample conversation for a flight booking assistant:

VA: Hi, how may I help you today?
User: Hey, what flight options have I got from LA to NYC?
VA: Sure, let me know the travel date.
User: Wait a minute, will it rain in NYC this Sunday?

The primary intent of this conversation is to book a flight ticket. But the user wants to know the weather forecast before completing the booking, which is a valid use case.

User Intent Nodes help you add a root intent, a follow-up or sub-intents to your dialog tasks. The flow for a follow-up intent is built within the same dialog task using transitions, and cannot be linked to external tasks. When the execution of a follow-up intent is completed, the conversation flow continues within the same dialog tasks based on the transitions you add.

Note: To start a new Dialog Task from an existing one, you can use the Dialog Task nodes.

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

Add the Node

  1. Open the dialog task to which you want to add the user intent node.
  2. Add a user intent node in the designated place. For steps on adding nodes, please read more here.
  3. The user intent window is displayed with the Component Properties tab selected by default.

Configure the Node

Component Properties

Note: The configurations you set up or edit in the Component Properties tab reflects in all the dialog tasks that use this node. These settings are the same for Intent and Sub-intent nodes.
  1. On the Component Properties tab, under the General Settings, you can modify
    1. The Name,
    2. The Display Name,
    3. The Description.

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.

You can add tags to build custom profiles of your VA’s conversations. You can define a key and a value for each of 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.

Here is an example of a dialog task that is connected as a subintent in a more complex one.

NLP Properties

The NLP Properties are related to the underlying intent associated with a dialog. You can add these properties here or in the NLP – Training section. They are used to train the machine learning model to help improve intent identification for the dialog task. These properties are not used to execute this node in the flow.

To improve intent identification for the dialog task, add or define the following properties: 

  1. Machine Learning settings to provide user utterances to improve the detection of this intent. Learn more.
  2. Patterns and Rules to capture this intent if the user’s utterance contains these specific patterns or matches the rule. Learn more.
  3. Bot Synonyms or related phrases for the user intent. Learn more.
  4. Manage Context tags as preconditions to identify the intent and define the output context to be set when this task is initiated. Learn more.

Connections Properties

Click the Connections tab and set the transition properties to determine the node in the dialog task to execute next.

Primary Intent nodes only allow you to select the next node to trigger.

If the Intent node you are working with does not represent the primary intent within the dialog task (if it follows another node), 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. For details on how to work with connection conditions, please see Adding IF-Else Conditions to Node Connections.

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

Menu