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
Bot Store
Overview
Creating a Kore.ai Bot Account
Adding a Kore.ai Bot
Choosing a Channel for a Bot
Interacting with a Kore.ai Bot
Setting Up Web Service Alerts
Setting Up RSS Alerts
Setting Up the Kore.ai Webhook Bot
Custom Kore.ai Bots
Bots for your Customers FAQs
Bots for your Workforce FAQs
Adding Bots
Contacting Kore.ai Support
Setting Up Filters
Bot Store Settings
How Tos
Context Switching
Using Traits
Schedule a Smart Alert
Configure Agent Transfer
Configuring Digital Views
Custom Dashboard
Patterns for Intents & Entities
Build Knowledge Graph
  1. Home
  2. Docs
  3. Bots
  4. Bot Building
  5. Creation
  6. Design

Design

Before you jump in to develop a Bot, it would be a good idea to spend some time in understanding what the Bot would be and how it would help you and your business. This understanding would bring clarity and efficiency to the Bot development.

Chatbots are artificial intelligence systems that the users interact with via text or voice interface. These interactions can be straightforward, like asking a bot about the weather report, or more complex, like tracing missing entry in your bank account.  Further, the interactions can be structured with user choosing options from a list of items presented or unstructured freestyle flow similar to a conversation with involving a human agent.

Whatever be the type of user interaction, good design helps in building an efficient bot. A good design allows for answering most of the user queries, anticipates all the conversation flows and expects the unexpected.

Post ver 7.2 release, platform has an option to help you design your conversations using the Storyboard feature. It is an intuitive conversation designer that simplifies and streamlines the bot blueprinting process, without the need to have external flow charts, tracking and versioning tools. See here for more.

Platform Recommendations: The following steps can be considered while designing a Bot:

  • Understanding the user needs to set the scope of the Bot. The business sponsors, business analysts, and product owners play an important role in identifying the user requirement by gathering market requirements and assessing internal needs.
  • Setting the chatbot goals helps create a well-defined use case. This would involve converting the above-identified scope to a use case. It would be advisable to involve the Bot developer in this phase.
  • Designing a chatbot conversation to define chatbot behavior in every possible scenario in its interaction with the user. Simulating conversations go a long way in identifying every possible scenario.

Once the bot capabilities and ideal use case are well-defined, Bot developer can begin the process of configuring bot tasks, define intents and entities, and build the conversational dialog.

Things to keep in mind while designing a chatbot: Try to answer the following questions (some if not all):

  • Who is the target audience? Technical help bots targetted for a tech-savvy customer need a different design when compared help bots for a layperson like, say, a bank customer. Hence assessing the target audience is always important.
  • What bot persona will resonate the most with this group? This will help define how the Bot will talk and act in every situation.
  • What is the purpose of the bot? The goal i.e. the customer query that the Bot needs to address will define the end point of any conversation.
  • What pain points would the bot solve? The purpose and scope of Bots can be set by identifying what the Bot will address and when the human agent needs to take over.
  • What benefits would the bot provide for us or our customer? The main benefit of using a Bot would be time-saving. The user need not waste their time waiting for a human agent to be available for answering their query. You, as the business owner, need not worry about not being there to cater to all customer needs.
  • What tasks do I want my bot to perform? Simulation of user conversation would help identify the tasks that need to be catered by the Bot.
  • What channels would the bot “live” in? This would to some extent drive the way the Bot would be presented, the various options available for the chatbot would be limited by the channel/medium it would be used.
  • What languages should my bot speak? When catering to a multi-lingual community the language support would be imperative and building the dictionary simultaneously would be useful.
Menu