Chatbot Overview
Conversational Bots
Intents & Entities
Intelligent Bots
Kore.ai's Approach
Kore.ai Conversational Platform
Bot Concepts and Terminology
Natural Language Processing (NLP)
Bot Types
Bot Tasks
Starting with Kore.ai Platform
How to Access Bot Builder
Working with Kore.ai Bot Builder
Building your first Bot
Getting Started with Building Bots
Using the Dialog Builder Tool
Creating a Simple Bot
Release Notes
Latest Updates
Older Releases
Deprecations
Bot Builder
Creating a Bot
Design
Develop
Storyboard
Dialog Task
User Intent Node
Dialog Node
Entity Node
Supported Entity Types
Composite Entities
Supported Time Zones
Supported Colors
Supported Company Names
Message Nodes
Confirmation Nodes
Service Node
Custom Authentication
2-way SSL for Service nodes
Script Node
Agent Transfer Node
WebHook Node
Connections & Transitions
Managing Dialogs
Prompt Editor
Alert Tasks
Alert Tasks
Ignore Words and Field Memory
UI Forms
Digital Views
Knowledge Graph
Terminology
Building
Generation
Importing and Exporting
Analysis
Knowledge Extraction
Small Talk
Action & Information Task
Action Tasks
Information Tasks
Establishing Flows
Natural Language
Overview
Machine Learning
ML Model
Fundamental Meaning
NLP Settings and Guidelines
Knowledge Graph Training
Traits
Ranking and Resolver
NLP Detection
Bot Intelligence
Overview
Context Management
Session and Context Variables
Context Object
Dialog Management
Sub-Intents
Amend Entity
Multi-Intent Detection
Sentiment Management
Tone Analysis
Sentiment Management
Default Conversations
Default Standard Responses
Channel Enablement
Test & Debug
Talk to Bot
Utterance Testing
Batch Testing
Record Conversations
Publishing your Bot
Analyzing your Bot
Overview
Dashboard
Custom Dashboard
Conversation Flows
Bot Metrics
Advanced Topics
Bot Authorization
Language Management
Collaborative Development
IVR Integration
Data Table
Universal Bots
Defining
Creating
Training
Customizing
Enabling Languages
Smart Bots
Defining
Sample Bots
Github
Asana
Travel Planning
Flight Search
Event Based Bot Actions
koreUtil Libraries
Bot Settings
Bot Functions
General Settings
PII Settings
Customizing Error Messages
Bot Management
Bot Versioning
Using Bot Variables
API Guide
API Overview
API List
API Collection
SDKs
SDK Overview
SDK Security
SDK App Registration
Web SDK Tutorial
Message Formatting and Templates
Mobile SDK Push Notification
Widget SDK Tutorial
Widget SDK – Message Formatting and Templates
Web Socket Connect & RTM
Using the BotKit SDK
Installing
Configuring
Events
Functions
BotKit SDK Tutorial – Agent Transfer
BotKit SDK Tutorial – Flight Search Sample Bot
Using an External NLP Engine
Bot Administration
Bots Admin Console
Dashboard
User Management
Managing Users
Managing Groups
Managing Role
Bots Management
Enrollment
Inviting Users
Bulk Invites
Importing Users
Synchronizing Users from AD
Security & Compliance
Using Single Sign-On
Security Settings
Cloud Connector
Analytics
Billing
Bot Store
Overview
Creating a Kore.ai Bot Account
Adding a Kore.ai Bot
Choosing a Channel for a Bot
Interacting with a Kore.ai Bot
Setting Up Web Service Alerts
Setting Up RSS Alerts
Setting Up the Kore.ai Webhook Bot
Custom Kore.ai Bots
Bots for your Customers FAQs
Bots for your Workforce FAQs
Adding Bots
Contacting Kore.ai Support
Setting Up Filters
Bot Store Settings
How Tos
Creating a Simple Bot
Configure UI Forms
Creating a Banking Bot
Transfer Funds Task
Update Balance Task
Context Switching
Using Traits
Schedule a Smart Alert
Configuring Digital Views
Custom Dashboard
Custom Tags to filter Bot Metrics
Patterns for Intents & Entities
Build Knowledge Graph
Global Variables
Content Variables
Using Bot Functions
Configure Agent Transfer
  1. Home
  2. Docs
  3. Bots
  4. Intelligence
  5. Sub-Intents

Sub-Intents

Human conversations are dynamic in that they tend to switch between intents and entities, often combining multiple things into one.

Kore.ai Bots Platform offers Sub Intents that can be defined at the task level, and are the easiest way to shape dialog without having to manage context manually. This will enable conversations to seamlessly branch into related intents as part of the primary intent, and work only within this context. An output context is added to the parent intent and an input context of the same name is added to the newly created child intent. Thus the child intent can only be matched when the parent intent was matched during a previous portion of the conversation.

Follow up Intents come in handy when during the course of a dialog, a user utterance or intent cannot be attended to immediately. You can access such intents that come up during the execution of a different task, but that were never acted upon. These are stored in the FollowupIntents array. You can then opt to ask users, at the end of the dialog flow, to select and perform tasks from a list of identified follow-up intents. You can also access this list to further train and refine their dialog flows.

Sub Intents

There are three ways to define Sub Intents:

  • Add an Intent Node within the Dialog Task – This intent will not be available for any other dialog and since it is within the dialog it is within its context. (more…)
  • Use an existing Dialog Task – This intent can be used over multiple dialogs. You can define the Dialog as Sub Intent only dialog and it can not be invoked by user utterance nor will it appear in the list of available tasks when the user says help. (more…)
  • As linked Tasks – the above two options can be used when the sub intent is part of the dialog flow. For cases where the sub intent can be invoked by the user anywhere within the dialog, use the Manage Sub Intents and Exceptions option.

Linked Task Exceptions 

To facilitate exceptions in switching between specific tasks, you can utilize the Linked Tasks Exceptions in Dialog Tasks. When you link a Dialog task to another, you can define customized Hold and Resume properties to transition to that particular task. Additionally, you can write one or more conditional expressions using any entity values or context to ensure the Hold and Resume rules come in to effect only if those conditions are met.

As a part of defining the exceptions, you can also define entity pre-assignments and post-assignments.

  • Using pre-assignments, you can map the parameters in the current context that need to be pre-populated in the next intent. You can pass the current context values to the entities present in the linked task or define custom variables to pass the current context values.
  • Using post-assignments, you can map the context values in the linked task back to the main task from where the linked task was invoked. You can pass the linked task context values to the entities present in the main task or define custom variables to pass the linked task context values.
    Note: Post-assignment will be applicable only when the main task is resumed.

Adding Exceptions

Follow these steps to add exceptions to transition to a specific task:

  1. Open the Dialog task whose settings you want to customize.
  2. From the top right-hand corner of the Dialog Builder, click the more options icon and select Manage Interruption Behavior.
  3. On the Manage Interruption Behavior page, click the Add sub-intents or exceptions link.
  4. In the Add sub-intents or exceptions page, from the Tasks drop-down list, select a task to link. You can select multiple tasks.
  5. Define the Hold and Resume settings from the list of options below and click Save.
  6. The Manage Interruption Behavior page opens with the selected tasks listed under Exceptions.

You can optionally add conditional expressions within which the transition should take place and map parameters for the selected task.

Adding Conditional Expressions

Follow these steps to add conditional expressions:

  1. Click the name of the task under Exceptions.
  2. Under Interruption Precondition, click Add If Condition.
  3. Select the Entity or Context option based on which you want to define the condition.
  4. Select an Entity or enter a Context, as per your selection.
  5. Select a connector from the list of options: Exists, equals to, greater than equals to, less than equals to, not equal to, greater than, or less than.
  6. Under the value column, enter a comparative value.
  7. To add more conditions, click Add If, and repeat steps 1-6. You can add any number of conditions. When you write multiple conditions, all the specified conditions must be met for the Hold and Resume settings to take effect.

Important Notes:

  • Using exceptions, you can link the same target task to a source task multiple times by defining different preconditions. When you do so, the platform executes the exceptions in the order they are defined.
  • When none of the preconditions meet an exception, the platform adds the intent to the Follow-up Intents array.
  • The platform evaluates the preconditions only when it encounters a user intent and tries to determine whether to execute it or not. It doesn’t evaluate the preconditions when developers initiate the linked task through transitions or when the end user chooses to run the task at the end of the dialog.

Parameter Mapping

To add entity pre-assignments, follow these steps after you enter conditional expressions for an exception:

  1. On the Exception Task window, under Parameter Mapping section Entity pre-assignment lists the entities needed for the on-hold task.
  2. Enter a direct value or a context reference next to an entity for which you want to pass a value.
  3. To pass values through a variable, click Add Key/Value and enter a variable name a value.

To add entity post-assignments, follow these steps after you enter conditional expressions for an exception:

  1. On the Exception Task window, under Entity post-assignment section you can see the list of entities in the current task.
  2. Enter a direct value or a context reference next to an entity for which you want to pass a value.
  3. To pass values to a variable, click Add Key/Value and enter a variable name a value.
    Note: Post-assignment will be applicable only when the main task is resumed.

Follow-up Intents

Follow-up intents refer to intents that came up in user conversations during the execution of another task, but the bot hasn’t attended to. As a part of Dialog task execution, the bot captures all unattended interruptions and make them accessible to the bot in the FollowupIntents array.

However, the bot doesn’t capture Follow-up Intents if you select the Do not Hold and Resume option at the node, task, or bot level, whichever is applicable to the task flow.

You can enable the Dialog task to present all the Follow-up tasks to the user at the end of the dialog so they can choose to execute any of them. To do so, follow these steps:

  1. Open the Dialog task whose settings you want to customize.
  2. On the top right-hand corner of the Dialog Builder, click the more options icon and then click Dialog Settings.
  3. The Follow-up Task sections shows the following options:

    • Yes, at the end of this dialog ask the user to select and perform a task from ‘Follow-up task’ list: Select this option to show all the unattended intents to the user at the end of the dialog. To customize the message sent to the user, click Manager Response next to the option.
    • No, ‘Follow-up task’ list will be handled as part of the node connections: This is the default option. If this option is active, the bot doesn’t present the Follow-up intents to the users at the end of the dialog. However, a developer can access this using the FollowupIntents array.
Menu