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 Colors
Supported Company Names
Form Node
Logic Node
Message Nodes
Confirmation Nodes
Service Node
Custom Authentication
2-way SSL for Service nodes
Script Node
Agent Transfer Node
WebHook Node
Grouping Nodes
Connections & Transitions
Managing Dialogs
User Prompts
Alert Tasks
Alert Tasks
Ignore Words and Field Memory
Digital 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
Model Validation
Fundamental Meaning
NLP Settings and Guidelines
Knowledge Graph Training
Traits
Ranking and Resolver
NLP Detection
Advanced NLP Configurations
Bot Intelligence
Overview
Context Management
Session and Context Variables
Context Object
Dialog Management
Sub-Intents & Follow-up 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
Manage Sessions
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
How Tos
Creating a Simple Bot
Creating a Banking Bot
Transfer Funds Task
Update Balance Task
Context Switching
Using Traits
Schedule a Smart Alert
Configure Digital Forms
Add Form Data into Data Tables
Configuring Digital Views
Add Data to Data Tables
Update Data in Data Tables
Custom Dashboard
Custom Tags to filter Bot Metrics
Patterns for Intents & Entities
Build Knowledge Graph
Using nlMeta
Global Variables
Content Variables
Using Bot Functions
Configure Agent Transfer
  1. Home
  2. Docs
  3. Bots
  4. Advanced Topics
  5. Universal Bot
  6. Customizing the Universal Bot’s Default Dialog Task

Customizing the Universal Bot’s Default Dialog Task

Universal bots come with a built-in dialog task that triggers automatically for unidentified intents. You can customize this dialog task, or import another, but cannot replace it with other standard responses. You can add more nodes to the default dialog task to build a custom experience

Default Dialog Task

Before you Begin

This article assumes that you understand the fundamentals of creating dialog tasks using the Kore.ai Bots Platform and therefore focuses on the aspects specific to the universal bots. To refer to the fundamentals of dialog tasks, read Dialog Tasks.

Default Dialog Nodes

Nodes that can be added to universal bot are limited compared to the standard bots. Below is the list of nodes that can be added to the default dialog task in the universal bot:

  • Send a message
  • Ask a question
  • Ask for an entity
  • Make a service call
  • Run a JavaScript
  • Initiate Agent Transfer
  • Enable WebHook connections

Customize the Default Dialog

Follow these steps to customize the default dialog message:

  1. Open the universal bot for which you want to configure new channels.
  2. Hover over the left navigation panel and click Natural Language -> Default Conversation.
  3. On the Natural Language window, click Default Dialog.
  4. Listed will be the default dialog – Intent Not Identified.
  5. Click to open the dialog. You will see an Intent and Message node already configured.
  6. You can customize the default dialog like any other dialog task adding the above-mentioned nodes.

Customizing the Default Dialog for an Enabled Language

If the Kore.ai NLP engine cannot recognize the user intent, the universal bot responds to the users with the default dialog. You must create language-specific versions of the default dialog for each enabled language so that such bot responses go in the users’ preferred language. Otherwise, the universal bot responds applies the default bot language regardless of the user’s preferred language. Learn more.

Event Handlers

Before you Begin

This article assumes that you understand the fundamentals of Event Handler functionality using the Kore.ai Bots Platform and therefore focuses on the aspects specific to the universal bots. To refer to the fundamentals of Event Handling, read Event Based Bot Actions.

With the release of ver8.0 of the platform, the ‘Events’ in the Universal Bot support triggering of the Dialog Tasks from the linked bots. For events that support the execution of tasks, you can choose the linked bot and a task from the linked bot.

The linked task will be executed at the trigger of the event. If the linked bot task is not available at the run time or in the language that the end-user is having the conversation in, then the end-user would be presented with the relevant Standard Response ‘Dialog task required for conversation is not available’

Variable Management

While building Universal bots you might want to propagate few values to the linked bots, like:

  • the environment details, when building multi-lingual bots, while migrating the universal bot from one environment to another.
  • the tenant values for scoping the bot intents.

Before you Begin

This article assumes that you understand the fundamentals of creating variables using the Kore.ai Bots Platform and therefore focuses on the aspects specific to the universal bots. To refer to the fundamentals of variable management, read Using Bot Variables.

Variable Declaration

As with Standard bots, you can

  • Define Global and Content variables.
  • Enable the propagation of the variable value to a selected linked bot.
  • You can access these variables in the script using {{env.<variable-name}} and {{content.<variable-name>>}}
  • In case the variable name is defined in both linked and universal bot, Universal bot variable value would take precedence.

Sentiment Management

Before you Begin

This article assumes that you understand the fundamentals of Sentiment functionality using the Kore.ai Bots Platform and therefore focuses on the aspects specific to the universal bots. To refer to the fundamentals of Sentiment Management, refer here.

With the release of ver8.1 of the platform, the Sentiment Based Events in the Universal Bot support triggering of the Dialog Tasks from the linked bots. For events that support the execution of tasks, you can choose the linked bot and a task from the linked bot.

The linked task will be executed at the trigger of the event. If the linked bot task is not available at the run time or in the language that the end-user is having the conversation in, then the end-user would be presented with the relevant Standard Response ‘Dialog task required for conversation is not available’.

Menu