GETTING STARTED
Kore.ai XO Platform
Virtual Assistants Overview
Natural Language Processing (NLP)
Concepts and Terminology
Help & Learning Resources
Quick Start Guide
Accessing the Platform
Navigating the Kore.ai XO Platform
Building a Virtual Assistant
Using Workspaces
Release Notes
Current Version
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
Nodes & Connections
Overview
Node Types
Intent Node
Dialog Node
Entity Node
Entity Rules
Form Node
Confirmation Node
Message Nodes
Logic Node
Bot Action Node
Service Node
Webhook Node
Script Node
Process Node
Agent Transfer
Node Connections Setup
Context Object
Sub-Intent Scoping
User Prompts
Voice Call Properties
Dialog Task Management
Event Handlers
Supported Entity Types
Supported Company Names
Supported Colors
Knowledge Graph
Introduction
Knowledge Extraction
Build Knowledge Graph
Create Node Structure
Build the Graph
Add FAQs
Add FAQs from an Existing Source
Run a Task
Traits, Synonyms, and Stop Words
Manage Variable Namespaces
Update Knowledge Graph
Introduction
Move Question and Answers Between Nodes
Edit and Delete Terms
Edit Questions and Responses
Knowledge Graph Analysis
Knowledge Graph Import and Export
Prepare Data for Import
From a CSV File
From a JSON File
Importing Knowledge Graph
Exporting Knowledge Graph
Auto-Generate Knowledge Graph
Alert Tasks
Small Talk
Digital Skills
Overview
Digital Forms
Digital Views
Introduction
Widgets
Panels
Train
NLP Optimization
ML Engine
Overview
Model Validation
FM Engine
KG Engine
Traits Engine
Ranking and Resolver
Training Validations
NLP Configurations
NLP Guidelines
Intelligence
Introduction
Default Standard Responses
Contextual Memory
Contextual Intents
Interruption Management
Multi-intent Detection
Amending Entities
Default Conversations
Conversation Driven Dialog Builder
Sentinment Management
Tone Analysis
Test & Debug
Overview
Talk to Bot
Utterance Testing
Batch Testing
Conversation Testing
Health and Monitoring
Deploy
Channels
Publishing
Versioning
Analyze
Introduction
Overview Dashboard
Conversations Dashboard
Users Dashboard
Performance Dashboard
Custom Dashboards
Introduction
Custom Meta Tags
Create Custom Dashboard
NLP Insights
Conversations History
Conversation Flows
Analytics Dashboard Filters
Usage Metrics
Containment Metrics
Smart Bots
Universal Bots
Introduction
Universal Bot Definition
Universal Bot Creation
Training a Universal Bot
Universal Bot Customizations
Enabling Languages
Store
Manage Assistant
Plan & Usage
Overview
Usage Plans
Support Plans
Invoices
Authorization
Multilingual Virtual Assistants
Get Started
Supported Components & Features
Manage Languages
Manage Translation Services
Multiingual Virtual Assistant Behavior
Masking PII Details
Variables
Collections
IVR Settings
General Settings
Assistant Management
Manage Namespace
Data as Service
Data Table
Table Views
App Definitions
Sharing Data Tables or Views
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
Configure Agent Transfer
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
APIs & SDKs
API Reference
API Introduction
API List
API Collection
koreUtil Libraries
SDK Reference
SDK Introduction
SDK Security
SDK Registration
Web Socket Connect and RTM
Using the BotKit SDK
BotKit SDK Tutorial - Blue Prism
Widget SDK Tutorial
Web SDK Tutorial
ADMINISTRATION
Introduction to Admin Console
Administration Dashboard
User Management
Add Users
Manage Groups
Manage Roles
Assistant Management
Enrollment
Invite Users
Send Bulk Invites
Import User Data
Synchronize Users from AD
Security & Control
Using Single-Sign On
Security Settings
Cloud Connector
Analytics
Billing
  1. Home
  2. Docs
  3. Virtual Assistants
  4. Advanced Topics
  5. Sentiment Management

Sentiment Management

Emotion tones are critical indicators in understanding the attitudes and opinions of users interacting with Virtual Assistants. Sentiment Management allows the developer to define and trigger events based on the user’s emotion or sentiment.

Notes

  • This feature was introduced in v7.0.
  • This feature is not supported in all languages. Click here for details.

 

Negative emotion scenarios like anger or disgust are typically considered factors that would determine a transfer of the conversation to a live agent.

The Natural Language Processing (NLP) interpreter can parse user utterances for specific words and phrases, and then provide an average tone score based on the connotation, word placement, and any added modifiers. (Click here for more on Tone Analysis)

The tone or sentiment scores are stored as context and used to drive the flow of a dialog task through conditional transition statements. You can use these scores to steer user-assistant conversations or seamlessly invoke escalation to a live agent.

Configuration

You can define multiple sentiment events from under Build > Intelligence > Sentiment Management. Click New Event to define an event based on which to capture the user’s emotion.

The following parameters can be configured for a sentiment event:

  • Event Name – Name of the event.
  • Event Trigger – Defines how often the sentiment must be checked. It can be set to:
    • On Task Completion – Sentiment is checked only after completion of a task.
    • After Every User Utterance– Sentiment is checked after every utterance from the end-user. The event is evaluated before proceeding with the conversation using the incoming utterance.
  • Emotion Configurations
    • The Session-level tone value is a consolidated tone value across all user messages in a conversation session.
    • The Message-level tone value is a tone value calculated for a given message from the user.
    • Select the required emotions to be captured from a list of six tones, anger, disgust, fear, sadness, joy, and positive.
    • Select if the tone should be considered at the Session level or Message level
    • Define the range to be considered for each of these tones, the range can be between -3 to +3. (Click here for more on Tone Analysis).
    • When multiple emotions are selected, the event is triggered when ALL the tone rules are met. In case you want the event to trigger when any tone rule is met, add them as separate rules.
      Note: Post v8.1, the Platform can identify the emojis in user utterance and set the tone accordingly.

Event Flow

Emotion tones are continuously updated whenever a message is received from the users and as such the sentiment events are also continuously evaluated. When an event’s criteria are met, the Platform triggers the defined behavior.

  • If the configuration used is to Initiate a task, then the current task is discarded and the VA switches to the new task according to the event configuration.
    • Any other implicitly paused tasks will also be discarded.
    • Tasks that are kept on hold using Hold and Resume settings are resumed as per Hold and Resume configuration.
    • If the dialog selected to trigger for the sentiment event is not available for any reason, then a standard response is displayed. Refer to the standard response with the title Dialog task required for conversation is not available for more information. (more on standard responses).
  • If the configuration used is to Run a Script, then the Platform executes the script and continues with the task execution. In case of any errors executing the script associated with the sentiment event, then a standard response is displayed. You may refer to the standard response titled Error in continuing the conversation due to incorrect bot definition for more information. (more on standard responses).
  • In case of a conflict between a sentiment event and direct intent invocation by the user, sentiment event is given precedence.
  • When tone criteria for two or more sentiment events are satisfied at the same instance, then the Platform prefers the sentiment event with the highest order of precedence used in defining the events.

Reset Tone

By default, sentiment values are reset at the beginning of every user conversation session.

Apart from the beginning of the conversation session, the Platform resets the sentiment values (i.e. tone scores) once the associated events are triggered. The reset behavior is based on the type of event trigger:

  • If a script is run, then the values are reset after successful execution of the script.
  • In case a dialog task is triggered, the values are transferred to the new dialog task’s (triggered by the sentiment event) context and reset in the original global context.
Menu