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
Bot Builder
Creating a Bot
Design
Develop
Dialog Task
Working with User Intent Node
Working with the Dialog Node
Working with Entity Node
Supported Entity Types
Working with Composite Entities
Supported Time Zones
Supported Colors
Supported Company Names
Working with Message Nodes
Working with the Confirmation Nodes
Working with Service Node
Implementing Custom Authentication
Enabling 2-way SSL for Service nodes
Working with Script Node
Working with Agent Transfer Node
Working with WebHook Node
Defining Connections & Transitions
Managing Dialogs
Prompt Editor
Action & Information Task
Working with Action Tasks
Working with Information Tasks
Establishing Flows
Alert Tasks
Working with Alert Tasks
Managing Ignore Words and Field Memory
Knowledge Tasks
Knowledge Ontology
Building Knowledge Graph
Importing and Exporting Bot Ontology
Knowledge Extraction
Natural Language
Overview
Machine Learning
ML Model
Fundamental Meaning
Knowledge Graph Training
Traits
Ranking and Resolver
NLP Detection
NLP Settings and Guidelines
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
Talking to Bot
Utterance Testing
Batch Testing
Recording Conversations
Publishing your Bot
Analyzing your Bot
Overview
Dashboard
Conversation Flows
Bot Metrics
Advanced Topics
Bot Authorization
Language Management
Collaborative Development
IVR Integration
Universal Bots
Defining
Creating
Customizing
Enabling Languages
Smart Bots
Defining
Sample Bots
Github
Asana
Travel Planning
Flight Search
Event Based Bot Actions
Bot Settings
Bot Functions
General Settings
PII Settings
Customizing Error Messages
Bot Management
Using Bot Variables
API Guide
API Overview
API List
API Collection
SDKs
SDK Overview
SDK Security
SDK App Registration
Kore.ai Web SDK Tutorial
Message Formatting and Templates
Mobile SDK Push Notification
Web Socket Connect & RTM
Using the BotKit SDK
Installing the BotKit SDK
BotKit SDK Configuration
Events for the BotKit SDK
Functions for the BotKit SDK
BotKit SDK Tutorial – Agent Transfer
BotKit SDK Tutorial – Flight Search Sample Bot
Using an External NLP Engine
Bot Administration
Bots Admin Console
User Management
Managing Users
Managing Groups
Managing Role
Bots Management
Enrollment
Inviting Users
Sending Bulk Invites to Enroll Users
Importing Users and User Data
Synchronizing Users from Active Directory
Security & Compliance
Overview
Using Single Sign-On
Cloud Connector
Analytics
Billing
How Tos
Context Switching
Using Traits
Live Agent Transfer
Schedule a Smart Alert
Configure Agent Transfer
  1. Home
  2. Docs
  3. Bots
  4. Intelligence
  5. Amend Entity

Amend Entity

This feature has been introduced in v6.4 release

Time and again, we come across situations wherein the users change their preferences during task execution.

For example, while booking a flight, the user might change the date of travel and at times even the destination.

Amend Entity is a feature for such scenarios. Using this feature, you can allow the users to amend entity values and also control the post-amendment dialog behavior.

The entity amendment process can be divided into three stages:

  • Amend Identification: Identifying that the end user wants to amend is driven by bot’s built-in NLP capabilities.
  • Amending Entities: On identifying the intention to amend, the current task is put on hold and the amend flow is triggered. Three kinds of amend flows are possible based upon the user utterance:
    • when the user refers to the entity name (or entity synonyms), then they will be prompted for the entity value. For example, user utterance “I want to change the destination” triggers the prompt for destination entity. If the same entity node is present multiple times in the dialog, then the latest entity node for which the user has already provided input will be amended.
    • when the user gives the entity value then the entity will be updated accordingly. For example, user utterance “I want to fly to JFK” changes the destination entity value. If the value is compatible with two or more entities in the dialog, then the user will be prompted to select an entity to amend.
    • when the user refers to both the entity and its value, then the entity is updated. For example, user utterance “change my destination to JFK” will change the destination entity value.
  • Post Amendment Behavior: After an entity is successfully amended, there are three possible dialog execution flows that your bot can be configured for:
    • The dialog can be re-executed from the node that is amended by evaluating that entity’s connections.
    • The dialog can resume from the node where amend was identified or made.
    • The dialog can be resumed from a specified node present in the dialog.

Implementation

On the Kore.ai platform, Amend Entity behavior can be defined at two levels:

  • Bot level, and
  • Task level.

Bot Level

To Set Bot Level Amend Entity Behavior

  1. From Natural Language -> Intelligence option select Amend Entity. By default amend entities is disabled.
  2. Once you Allow amend entities, various Dialog Resumption options are available:
    • Re-execute dialog from amended entity – use this option to resume the dialog by evaluating the amended entity’s connections. You can further choose to:
      • Clear entity values captured downstream – to clear all entities captured between the identified entity and the amend
      • Skip display of previously displayed messages – messages from Message nodes alone.
    • Resume dialog from amend identification nodeuse this option to resume the dialog from the node where the amend was identified.

Task Level

To set Task Level Amend Entity Behavior

Amend entity behavior can be set at the Task level also. The configurations defined at the task level will override the bot level configurations.

  1. From the Dialog Task page, click the Ellipses  icon and select the Manage Amend Behaviour.
  2. This opens the Manage Amend Behaviour dialog.
  3. By default, Use bot level settings is selected and the Bot level setting is displayed
  4. Select Customize for this task to override the Bot level settings
    • Do not allow amend entities will not allow the user to amend entity values for this task,
    • Allow amend entities will further give you three Dialog Resumption options:
      • Re-execute dialog from amended entityAmend entity behavior can be set at the Task level also. The configurations defined at the task level will override the bot level configurations.
        • Clear entity values captured downstream – to clear all entities captured between the identified entity and the amend
        • Skip display of previously displayed messages – messages from Message nodes alone.
      • Resume dialog from amend identification nodeuse this option to resume the dialog from the node where the amend was identified.
      • Jump to a specific node in the dialoguse this option to select a node from the current dialog where the task flow needs to jump. You can use this option to add custom behavior before resuming with the dialog. Context object will contain the details of the entities amended, along with the previous and current values. You may use this information to customize the dialog

Additional Notes

  • Amend functionality is not applicable for universal bot’s default language. However, when a linked bot is in progress, amend settings of the linked bot will be honored.
  • Identification of the amend requests is driven by the platform’s in-built training data and it is currently supported only for the Dialog task conversations in English.
  • The scope of this feature currently includes only the replacement of previously populated entities. It does not include other scenarios like partial modifications, deletions, additions to entity values.
Menu