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
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
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
Global Variables
Content Variables
Using Bot Functions
Configure Agent Transfer
  1. Home
  2. Docs
  3. Bots
  4. Bot Settings
  5. Conversation Sessions

Conversation Sessions

Conversation sessions are defined as an uninterrupted interaction between the bot and the user. These sessions are used in multiple analytics dashboards in Bot Builder as well as Bot Admin Console platforms.

Kore.ai virtual assistant platform allows you to customize how these Conversation Sessions are to be created and closed.

Conversation Sessions are different from Billing Sessions, refer here for more on Billing Sessions.

Overview

A Conversation Session is defined as an uninterrupted volley between the end-user and the bot.

  • Before the release of v7.2 of the platform – a new session was created after the inactivity duration (set as 15 mins) has elapsed since the end-users’ last interaction.
  • Post v7.2 – after the inactivity duration (set as 15 mins) has elapsed
    • if the end-user comes back and continues with the same intent, then the current session continues;
    • if the end-user comes back with a new intent or with an invalid input for the existing intent, a new session is created.
  • Post v8.0 platform gives you an option to:
    • Proactively close the sessions after inactivity – for details on Manage Sessions refer here.
    • Not proactively close the sessions after inactivity – retain the v7.2 behavior described above;

Conversation Sessions are created for all interactions with the virtual assistant or bot. These include:

  • All conversations that include one or more messages from the user marked as interactive sessions. These include all end-user interactions across all channels and events including providing authorization details.
  • All bot initiated conversion sessions like onConnect event messages are recorded as non-interactive sessions. These sessions will be updated as Interactive sessions as soon as a user message is received. Non-interactive sessions are not considered for calculating the billing sessions.
  • Developer interactions are also included as conversation sessions. A flag differentiates the user sessions from developer sessions and billing sessions are not created for these developer sessions.

Note: inclusion of non-interactive and developer interactions in conversation sessions was done with ver8.0.

Manage Sessions

This feature was released with v8.0 of the platform.

Using the Manage Sessions option from Settings -> Config Settings, you can define the Conversation Session Behavior:

  • Do not proactively close the sessions after inactivity – this option will close the session only when the user returns after 15 minutes of inactivity and provides a new intent. This was the default behavior before the release of ver8.0 of the platform. This option will be deprecated in future releases.
  • Proactively close the sessions after inactivity – this option will close the session after a defined duration of inactivity. You can set the following parameters:
    • Inactivity Duration – this is set to 15 minutes by default and decides when the session should close. You can set it to any value between 5-60 minutes.
    • Pre-closure Behavior – you can choose to close the session without informing the user or inform the user about the session closure by sending out a message. This message can be customized using the Manage response link.

Implementation

When does a Conversation Session start?

Conversation Sessions will be created for all interactions:

  • All end-user interactions across all channels and events – Conversation sessions will be created for On_connect – Run a script, Run a Message, Trigger a Dialog scenario. There are two categories of these conversation sessions:
    • Interactive sessions are conversations that include one or more messages from the user.
    • Non-interactive sessions are conversations with no messages from the user. All bot initiated conversion sessions will start as ‘Non-interactive’. These sessions will be updated as Interactive sessions as soon as a user message is received. The non-interactive sessions will not be considered for calculating the billing sessions.
  • Developer interactions will also be considered for creating conversation sessions but these will be marked as different from the user sessions and will not be considered for Billing Sessions.

When does a Conversation Session close?

  • The platform will proactively close inactive sessions after the specified time of inactivity as set in the Manage Sessions option described above.
  • When the following utterances are detected – “Discard”
  • When the chat window is refreshed ie “refresh: true” is detected.

What happens when a Conversation Session closes?

  • Post-session closure, the following information or variables will be cleared:
    • Conversation session;
    • Bot User Session (developer-defined variables without custom TTL)
    • Dialog Context (Topic File and Conversation Details)
    • If configured, before closing the conversation session, the platform will proactively send a session closure message to the users on supported channels.
  • For “refresh: true”:
    • Complete session information is cleared;
    • A new conversation session is created.
  • For “discard all
    • The Dialog context, Current and Historic Tags are cleared;
    • The Sentiment Tones are reset;
    • The same Conversation Session will be continued
  • For “discard
    • The current Dialog context will be cleared;
    • The Current Tags will be replaced with the last updated ‘tags’ in the Historic Tags, and the Historic Tags would be cleared;
Menu