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
Storyboard
Dialog Task
User Intent Node
Dialog Node
Entity Node
Supported Entity Types
Composite Entities
Supported Time Zones
Supported Colors
Supported Company Names
Message Nodes
Confirmation Nodes
Service Node
Custom Authentication
2-way SSL for Service nodes
Script Node
Agent Transfer Node
WebHook Node
Connections & Transitions
Managing Dialogs
Prompt Editor
Alert Tasks
Alert Tasks
Ignore Words and Field Memory
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
ML Model
Fundamental Meaning
NLP Settings and Guidelines
Knowledge Graph Training
Traits
Ranking and Resolver
NLP Detection
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
koreUtil Libraries
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
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
Configuring Digital Views
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. Test your Bot
  5. Talk to Bot

Talk to Bot

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

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

A messaging window for the bot is displayed and connected to the NLP interpreter as shown in the following illustration for the Flight Management Bot.

Note: The Talk to Bot Run Bot Dialog 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 bot is displayed, if defined. In the Message section, enter text to begin interacting and testing your bot, 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 bot, try different variations of user prompts and ensure the NLP interpreter is processing the synonyms (or lack of synonyms) properly. If the bot returns unexpected results, consider adding or modifying synonyms for your tasks and task field names as required. For more information, see Natural Language Processing.

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.

  • NL Analysis: Describes the bot 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 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:

  • processing: The Bots Platform begins processing of the node
  • processed:  The node and node connections are processed, the following node is found but the dialog has not yet moved to that node.
  • 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 Bot topic.

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.

System Commands

System Commands allow you to take control of the user-bot conversation during evaluation. These can also be injected into the bot using JavaScript code. The following commands can be used:

  • You can terminate current task/intent using commands like “Discard“, “Terminate“, “End” etc. Any previous tasks that were on hold would be resumed.
  • You can terminate all tasks/intents for that particular session using commands like “Discard All“, “Terminate Everything“, “Clean All” etc.  You can also use the Refresh icon at the top of Talk to Bot window for the same purpose.
  • You can define your own discard commands using a custom concept named ~bot_commands_override_discard (see here for how). When the words in this concept are detected in the user utterance then the current task will be discarded without any further checks. Only these words will cause a discard to happen, and these must be the only words on the user utterance. An explicit reference to “all” in these command variations will ensure termination of all tasks, else only the current task will be terminated.

Be aware that if the bot recognizes any of these commands (except those defined in the custom concept) as a valid intent or entity value then priority would be given to the intent/entity recognized and the bot would process these phrases accordingly. The priority being – first intent then entity and lastly system command.

Record

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

Menu