GETTING STARTED
Kore.ai XO Platform
Virtual Assistants Overview
Natural Language Processing (NLP)
Concepts and Terminology
Quick Start Guide
Accessing the Platform
Navigating the Kore.ai XO Platform
Building a Virtual Assistant
Help & Learning Resources
Release Notes
Current Version
Recent Updates
Previous Versions
CONCEPTS
Design
Storyboard
Overview
FAQs
Conversation Designer
Overview
Dialog Tasks
Mock Scenes
Dialog Tasks
Overview
Navigate Dialog Tasks
Build Dialog Tasks
Node Types
Overview
Intent Node
Dialog Node
Dynamic Intent Node
GenAI Node
GenAI Prompt
Entity Node
Form Node
Confirmation Node
Message Nodes
Logic Node
Bot Action Node
Service Node
Webhook Node
Script Node
Process Node
Agent Transfer
Node Connections
Node Connections Setup
Sub-Intent Scoping
Entity Types
Entity Rules
User Prompts or Messages
Voice Call Properties
Knowledge AI
Introduction
Knowledge Graph
Introduction
Terminology
Build a Knowledge Graph
Manage FAQs
Knowledge Extraction
Import or Export Knowledge Graph
Prepare Data for Import
Importing Knowledge Graph
Exporting Knowledge Graph
Auto-Generate Knowledge Graph
Knowledge Graph Analysis
Answer from Documents
Alert Tasks
Small Talk
Digital Skills
Overview
Digital Forms
Digital Views
Introduction
Widgets
Panels
Session and Context Variables
Context Object
Intent Discovery
Train
NLP Optimization
ML Engine
Overview
Model Validation
FM Engine
KG Engine
Traits Engine
Ranking and Resolver
Training Validations
NLP Configurations
NLP Guidelines
LLM and Generative AI
Introduction
LLM Integration
Kore.ai XO GPT Module
Prompts & Requests Library
Co-Pilot Features
Dynamic Conversations Features
Intelligence
Introduction
Event Handlers
Contextual Memory
Contextual Intents
Interruption Management
Multi-intent Detection
Amending Entities
Default Conversations
Conversation Driven Dialog Builder
Sentinment Management
Tone Analysis
Default Standard Responses
Ignore Words & Field Memory
Test & Debug
Overview
Talk to Bot
Utterance Testing
Batch Testing
Conversation Testing
Conversation Testing Overview
Create a Test Suite
Test Editor
Test Case Assertion
Test Case Execution Summary
Glossary
Health and Monitoring
NLP Health
Flow Health
Integrations
Actions
Actions Overview
Asana
Configure
Templates
Azure OpenAI
Configure
Templates
BambooHR
Configure
Templates
Bitly
Configure
Templates
Confluence
Configure
Templates
DHL
Configure
Templates
Freshdesk
Configure
Templates
Freshservice
Configure
Templates
Google Maps
Configure
Templates
Here
Configure
Templates
HubSpot
Configure
Templates
JIRA
Configure
Templates
Microsoft Graph
Configure
Templates
Open AI
Configure
Templates
Salesforce
Configure
Templates
ServiceNow
Configure
Templates
Stripe
Configure
Templates
Shopify
Configure
Templates
Twilio
Configure
Templates
Zendesk
Configure
Templates
Agents
Agent Transfer Overview
Custom (BotKit)
Drift
Genesys
Intercom
NiceInContact
NiceInContact(User Hub)
Salesforce
ServiceNow
Configure Tokyo and Lower versions
Configure Utah and Higher versions
Unblu
External NLU Adapters
Overview
Dialogflow Engine
Test and Debug
Deploy
Channels
Publishing
Versioning
Analyze
Introduction
Dashboard Filters
Overview Dashboard
Conversations Dashboard
Users Dashboard
Performance Dashboard
Custom Dashboards
Introduction
Custom Meta Tags
Create Custom Dashboard
Create Custom Dashboard Filters
LLM and Generative AI Logs
NLP Insights
Task Execution Logs
Conversations History
Conversation Flows
Conversation Insights
Feedback Analytics
Usage Metrics
Containment Metrics
Universal Bots
Introduction
Universal Bot Definition
Universal Bot Creation
Training a Universal Bot
Universal Bot Customizations
Enabling Languages
Store
Manage Assistant
Team Collaboration
Plan & Usage
Overview
Usage Plans
Templates
Support Plans
Invoices
Authorization
Conversation Sessions
Multilingual Virtual Assistants
Get Started
Supported Components & Features
Manage Languages
Manage Translation Services
Multiingual Virtual Assistant Behavior
Feedback Survey
Masking PII Details
Variables
Collections
IVR Settings
General Settings
Assistant Management
Manage Namespace
Data
Overview
Data Table
Table Views
App Definitions
Data as Service
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
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
Migrate External Bots
Google Dialogflow Bot
APIs & SDKs
API Reference
API Introduction
Rate Limits
API List
koreUtil Libraries
SDK Reference
SDK Introduction
Web SDK
How the Web SDK Works
SDK Security
SDK Registration
Web Socket Connect and RTM
Tutorials
Widget SDK Tutorial
Web SDK Tutorial
BotKit SDK
BotKit SDK Deployment Guide
Installing the BotKit SDK
Using the BotKit SDK
SDK Events
SDK Functions
Tutorials
BotKit - Blue Prism
BotKit - Flight Search Sample VA
BotKit - Agent Transfer
  1. Home
  2. Docs
  3. Virtual Assistants
  4. Test your Bot
  5. Talk to Bot

Talk to Bot

After you have defined your assistant and configured one or more tasks, you should test your settings before you publish your NLP-enabled assistant. Bot owners and developers can chat with the assistant in real-time to test recognition, performance, and flow as if it were a live session.

Testing a Virtual Assistant

To test your tasks in a messaging window, click the Talk to Bot icon located on the lower right corner on the XO Platform.

A messaging window for the assistant is displayed and connected to the NLP interpreter as shown in the following illustration for a Flight Details Assistant .

Note: The Talk to Bot icon is not enabled until and unless at least one task is created.

When you first open the window, the Bot Setup Confirmation Message field definition for the assistant is displayed, if defined. In the Message section, enter text to begin interacting and testing your assistant , for example, Book a flight. The NLP interpreter begins processing the task, verifying authentication with the user and the web service, and then prompting for required task field information. When all the required task fields are collected, it executes the task. While testing your assistant , try different variations of user prompts and ensure the NLP interpreter is processing the synonyms (or lack of synonyms) properly. If the assistant returns unexpected results, consider adding or modifying synonyms for your tasks and task field names as required. For more information, see Natural Language Processing.

Debugging and Troubleshooting

You can open a debug window to view the natural language processing, logs, and session context, and variables of the chat. To open the debug, click the Debug icon   located on the top right-hand side of the Talk to Bot chat window. The Debug window consists of the following tabs: Debug Log, NL Analysis, Session Context & Variables.

The Debug window lets you explore the following:

  • NL Analysis: Describes the tasks loading status, and for each utterance presents a task name analysis and recognition scores.
  • Debug Log: Lists the processing or processed Dialog task components, which include Script Node, Service Node, and Webhook Node logs along with a date timestamp.
  • Session Context & Variables: Shows both context object and session variables used in the dialog task processing.

Debug Log

Debug Log provides the sequential progression of a dialog task and context and session variables captured at every node. The Debug log supports the following statuses:

  • initiated: The XO Platform initiates the various nodes in a dialog task. For example, script, service, and webhook execution is initiated.
  • execution: indicates execution of nodes has started. For example, script, service, and webhook execution has started.
  • execution successful: indicates execution of nodes is successful.For example, script, service, and webhook execution is successful.
  • process completed: indicates execution process for the script, service and webhook node is completed.
  • expand: You can expand the node and click the Show More to view node debug log details.
  • node details: shows the node details in the script format. You can copy, open the script in a full screen view or close the script view.
  • parsing: The XO Platform begins to parse the user prompt.
  • parsing successful:  the user prompt is parsed successfully.
  • waitingForUserInput: The user was prompted for input
  • pause: The current dialog task is paused while another task is started.
  • resume: The current dialog with paused status continues at the same point in the flow after completion of another task that was started.
  • waitingForServerResponse: The server request is pending an asynchronous response.
  • error: An error occurred, for example, the loop limit is reached, a server or script node execution fails.
  • end: The dialog reached the end of the dialog flow.

NL Analysis

NL Analysis tab shows the task name analysis and recognition scores of each user utterance.  It presents a detailed tone analysis, intent detection, and entity detection performed by the Kore.ai NLP engine. As a part of intent detection, the NL Analysis tab shows the outcomes of Machine Learning, Fundamental Meaning, and Knowledge Graph engines. For a detailed discussion on the scores, see Training Your Assistant topic.

NER information in the conversational context is available on this tab. This information can be used for causes like node transition.

Note: This is available only in Standard Bots.

Session Context and Variables

The Session Context & Variables tab displays dynamically the populated Context object and session variables updated at each processed component in Dialog Builder. The following is an example of the Session & Context Variables panel in Debug Log. For more information about the parameters, see Using Session and Context Variables in Tasks and Context Object.

The same NER information, that is visible in the NL Analysis tab, can be seen in this tab too under Custom Variables.The platform shows below details in the nerInfo object:

  1. componentId
  2. entityNERConfidenceScore
  3. entityName
  4. Value

Note that this feature is available only for Standard bots.

System Commands

System Commands allow you to take control of the user-bot conversation during evaluation. These can also be injected into the assistant using JavaScript code. See here for more.

Record Session

Record option allows you to record conversations to help in regression testing scenarios.

While your recording is in progress, you can see a notification at the top of the chat window. Here is where you will also find a STOP option, which you can click on whenever you want to stop recording. 

Once you stop the recording, you can use the recorded conversation to create a test case, for further conversation testing. Learn more.

After clicking on Create Test Case, you can alternatively download the recorded content as a JSON file.

This is what a short conversation with a Kore.ai assistant might look like: 

Talk to Bot

After you have defined your assistant and configured one or more tasks, you should test your settings before you publish your NLP-enabled assistant. Bot owners and developers can chat with the assistant in real-time to test recognition, performance, and flow as if it were a live session.

Testing a Virtual Assistant

To test your tasks in a messaging window, click the Talk to Bot icon located on the lower right corner on the XO Platform.

A messaging window for the assistant is displayed and connected to the NLP interpreter as shown in the following illustration for a Flight Details Assistant .

Note: The Talk to Bot icon is not enabled until and unless at least one task is created.

When you first open the window, the Bot Setup Confirmation Message field definition for the assistant is displayed, if defined. In the Message section, enter text to begin interacting and testing your assistant , for example, Book a flight. The NLP interpreter begins processing the task, verifying authentication with the user and the web service, and then prompting for required task field information. When all the required task fields are collected, it executes the task. While testing your assistant , try different variations of user prompts and ensure the NLP interpreter is processing the synonyms (or lack of synonyms) properly. If the assistant returns unexpected results, consider adding or modifying synonyms for your tasks and task field names as required. For more information, see Natural Language Processing.

Debugging and Troubleshooting

You can open a debug window to view the natural language processing, logs, and session context, and variables of the chat. To open the debug, click the Debug icon   located on the top right-hand side of the Talk to Bot chat window. The Debug window consists of the following tabs: Debug Log, NL Analysis, Session Context & Variables.

The Debug window lets you explore the following:

  • NL Analysis: Describes the tasks loading status, and for each utterance presents a task name analysis and recognition scores.
  • Debug Log: Lists the processing or processed Dialog task components, which include Script Node, Service Node, and Webhook Node logs along with a date timestamp.
  • Session Context & Variables: Shows both context object and session variables used in the dialog task processing.

Debug Log

Debug Log provides the sequential progression of a dialog task and context and session variables captured at every node. The Debug log supports the following statuses:

  • initiated: The XO Platform initiates the various nodes in a dialog task. For example, script, service, and webhook execution is initiated.
  • execution: indicates execution of nodes has started. For example, script, service, and webhook execution has started.
  • execution successful: indicates execution of nodes is successful.For example, script, service, and webhook execution is successful.
  • process completed: indicates execution process for the script, service and webhook node is completed.
  • expand: You can expand the node and click the Show More to view node debug log details.
  • node details: shows the node details in the script format. You can copy, open the script in a full screen view or close the script view.
  • parsing: The XO Platform begins to parse the user prompt.
  • parsing successful:  the user prompt is parsed successfully.
  • waitingForUserInput: The user was prompted for input
  • pause: The current dialog task is paused while another task is started.
  • resume: The current dialog with paused status continues at the same point in the flow after completion of another task that was started.
  • waitingForServerResponse: The server request is pending an asynchronous response.
  • error: An error occurred, for example, the loop limit is reached, a server or script node execution fails.
  • end: The dialog reached the end of the dialog flow.

NL Analysis

NL Analysis tab shows the task name analysis and recognition scores of each user utterance.  It presents a detailed tone analysis, intent detection, and entity detection performed by the Kore.ai NLP engine. As a part of intent detection, the NL Analysis tab shows the outcomes of Machine Learning, Fundamental Meaning, and Knowledge Graph engines. For a detailed discussion on the scores, see Training Your Assistant topic.

NER information in the conversational context is available on this tab. This information can be used for causes like node transition.

Note: This is available only in Standard Bots.

Session Context and Variables

The Session Context & Variables tab displays dynamically the populated Context object and session variables updated at each processed component in Dialog Builder. The following is an example of the Session & Context Variables panel in Debug Log. For more information about the parameters, see Using Session and Context Variables in Tasks and Context Object.

The same NER information, that is visible in the NL Analysis tab, can be seen in this tab too under Custom Variables.The platform shows below details in the nerInfo object:

  1. componentId
  2. entityNERConfidenceScore
  3. entityName
  4. Value

Note that this feature is available only for Standard bots.

System Commands

System Commands allow you to take control of the user-bot conversation during evaluation. These can also be injected into the assistant using JavaScript code. See here for more.

Record Session

Record option allows you to record conversations to help in regression testing scenarios.

While your recording is in progress, you can see a notification at the top of the chat window. Here is where you will also find a STOP option, which you can click on whenever you want to stop recording. 

Once you stop the recording, you can use the recorded conversation to create a test case, for further conversation testing. Learn more.

After clicking on Create Test Case, you can alternatively download the recorded content as a JSON file.

This is what a short conversation with a Kore.ai assistant might look like: 

Menu