1. Home
  2. Kore.ai Conversational Platform
  3. Bot Builder Tool
  4. Getting Started with Building Bots

Getting Started with Building Bots

This section contains topics that describe what bots are, the process on how to create and publish bots, and how to enable and use Natural Language Processing for your customized bots created in the Kore.ai Bot Builder tool. If you are new to Bot Builder, you should first get familiar with the terms and concepts we use. For more information, see Bot Concepts.

Building your First Bot

Once you get access to the Kore.ai Bot Builder Platform, you can build your first bot within no time. Building bots in Kore.ai involve the following major steps:

Step 1: Define a New Bot

In Bot Builder, on the left navigation menu, click New bot, and then define the basic settings such as name, color, and display icon. Configure authentication for your chatbot to access third-party web services, with support for various authorization types. For more information, see Defining a Standard Bot.

Step 2: Create Bot Tasks

Define one or more tasks for the bot. Tasks refer to different types of simple and complex “jobs” that a developer designates the chatbot to perform to fulfill the user intents. For example, the most common tasks types that a travel bot might perform could be Book tickets, Find hotels, and Provide weather forecast, which caters to different user intents. For more information, see Defining Bot Tasks.

Step 3: Optimize the Bot for Natural Language Processing

Test how the NLP engine recognizes and responds to user inputs for each bot. Train the bot using machine learning to improve utterance recognition. You can fine-tune the NLP engine and the bot’s configuration by adding additional utterances, synonyms, and patterns for a task or intents. For more information, see Optimizing Bots for Natural Language Processing.

Step 4: Add Channels

Define the channels on which you want to enable the bot. Channels refer to various communication platforms where a bot can live such as SMS, email, mobile apps, websites, messaging apps and more. With the Bot Builder, you can design chatbot tasks once, and deploy across 20+ channels by merely checking a box. For more information, see Adding Channels to your Bot.

Step 5: Publish All or Selected Tasks

Publish your bot tasks to your account, a Kore.ai space, or your company account. When you publish tasks, it initiates a publishing request to Bots Admin who can review and approve/ disapprove their deployment. For more information, see Publishing Tasks.

Working with Kore.ai Bot Builder

When you sign in to Kore.ai Bot Builder, the landing page shows all your bots as well as the bots shared with you for development. Click the name of a bot to open it. To create a new bot, click the New Bot button on the top right-hand side of the page.

When you open a bot, the Bot Tasks page opens. It consists of tabs for each task type that you can create in the platform. Click a tab to see the list of tasks in your bot.

  • Dialog Tasks – Consists of multiple sub-intents and component nodes to conduct a complex conversational flow between a user and the bot.
  • Alert Tasks – Monitors a web service for events and then sends a notification message to the user when the event occurs. You can use this task type for scheduled polling or near real-time notification using webhooks.
  • Information Tasks – Provides a report of data by asking the user for input parameters and then executing a web service call. The formatted data is presented to the user as a link to a report that a user can click to display the data, for example, Show my tickets, or 3-day Weather Forecast.
  • Action Tasks – Queries a user on demand for input parameters, and then executes a web service call along with a confirmation message, for example, Create New Ticket, or Get Weather for this Location.
  • Knowledge Graph – Turns static FAQ pages into intelligent, personalized conversational experience. Build an ontology of crucial terms, add questions to the right nodes in the hierarchy and leave the task of responding to users to the bot, thus enabling your Support staff to engage with more complex tasks.
  • Creating Flows – Associates one task to another task of the same or different Bot. For example, a flow for a Twitter tweet notification could be to Create New Follower.

To create a new task, hover over a task type tab, and then click the plus icon. For example, if you want to create a Knowledge Graph, hover over the Knowledge Collection tab, and then click the plus icon that appears.

The Bot Tasks page shows the following details for each task: Name, Description, TypeLast Updated, Status, and Version. When you hover over a task name, the Settings DIYSettingsIcon icon opens.

Status

Bot tasks and flows pass through the following stages:

  • In Progress: Bot developers have begun configuring the task but haven’t yet defined all the required configurations. This status applies only to Alert, Action, and Information tasks.
  • Configured – The task configuration is complete but the Bot Owner hasn’t yet published the task.
  • Awaiting Approval – The Bot Owner has published the task thus initiating a request to the Bots Admin, but the Bots Admin hasn’t yet approved the publishing request.
  • Published – The task is published for a personal, enterprise, or public use.
  • Upgrade in Progress – Bot developers have created an upgrade version of the published task to change any configurations, but the configuration is not yet complete.
  • Rejected – The Bots Admin rejects the publishing request. An email is sent to the developer with comments from the Bots Admin.
  • Suspended – The Bots Admin suspended use of a deployed bot in an enterprise. An email is sent to the developer with comments from the Bots Admin.

Important Notes:

  • Once a task is published, it cannot be deleted. However, if the Bots Admin suspends the task, you can delete the task.
  • You can also upgrade a published task and make the new task a mandatory or optional upgrade.

Version

The Version for a task displays the published version number. The first version is 1, and subsequent minor upgrades are represented as decimals such as 1.1, 1.2, till 1.9. Major upgrades are represented as whole numbers, for example, 1, 2, 3, 4. When an upgrade is configured, but not yet published, the Version is set to Draft.

Settings

When you select the Settings DIYSettingsIcon icon for a task or flow, you can:

  • View: Displays read-only task or flow settings.
  • Edit: Displays the task or flow for modification.
  • Edit Basic Settings (Only Published tasks): Click to open the Basic Settings page for the task. Settings on this page can be made to the task without having to upgrade the task.
  • Clone: Create a copy of the task with a new name using the syntax CopyOf – CurrentName (Clone#). For example, for an alert task named Test, the cloned name is CopyOf – Test (57) where 57 represents a unique hexadecimal value for the clone created.
  • Upgrade: Creates a copy of a published task used to edit, and when configured, can be deployed to end-users as an upgrade to the original task.
  • Publish (Only tasks in Status Configured): Publish to make the bot available to your company marketplace or space.
  • Version History: Displays the Version History page for a published task.
  • Map Any Task, Map Action Task (Only for tasks with Status set to Published): After a task is published, you can optionally map one or more action tasks to an alert task. For example, when a JIRA alert indicates a new issue, you can map an action task that allows the user to assign the JIRA issue to another JIRA user. You can also map an alert task in one bot, to an action task in another bot. For example, a JIRA alert task can be mapped with an Asana action task. When you map an alert task with an action task, it becomes a flow.
  • Add Command, Manage Command (Only for Published web service action tasks): Displays the Add Bot Command or Modify Bot Command dialog for action tasks.
  • Delete (Only flows, and unpublished tasks): Click to permanently delete a task or flow. Published tasks cannot be deleted.
  • View Logs: Opens the Logs page where you can review system and auditing event logs for a task.
  • Show older versions: In the Flows section, if a Flow was modified and saved, click to expand the Older Version Flows panel for that Flow.
  • Release Lock: When you create or edit a task, a 30-minute lock is automatically added to prevent other developers from accessing this task, for example, while you are still editing the task. Select Release Lock if you want to remove the 30-minute lock prior to the lock expiring.

Status Tracker: Managing Export and Training Jobs

You can keep track of all export and training jobs in the Bot Builder from a single location called the Status Tracker Dock. You can access the dock from the bottom of the bot menu.

When you start an export or training job, the platform starts providing the updates for it in the dock without holding you at the same screen so that you can continue working with any other aspects of the bot.

Export and Training Items Tracked in the Dock
Export or Training Item Details Shown Description
Bot Export
  • Percentage of export
  • Completion status of the export – Success or Failure.
  • Download link on successful completion of the download.
  • Download link for the ‘log’ file.
Shows the status of the export initiated by the user. Each user export status will be tracked separately in their login.
Analyze CSV export
  • Percentage of export
  • Completion status of the export – Success or Failure.
  • Download link on successful completion of the download.
Shows the status of the export initiated by the user. Each user export status will be tracked separately in their login.
ML Utterances Export
  • Percentage of export
  • Completion status of the export – Success or Failure.
  • Download link on successful completion of the download.
Shows the status of the export initiated by the user. Each user export status will be tracked separately in their login.
Batch Testing Execution
  • Completion status of the batch test execution- Success or Failure.
Shows the status of the batch testing executing initiated by the user. Each user export status will be tracked separately in their login.
Bot Variables Export
  • Percentage of export
  • Completion status of the export – Success or failure.
  • Download link on successful completion of the download.
Shows the status of the export initiated by the user. Each user export status will be tracked separately in their login.
Training of Configured Model
  • Completion status of the training Success or Failure.
Shows the status of the language-specific ML training of the entire bot to all the bot users no matter who initiated the training.
Training of Published Model
  • Completion status of the training- Success or failure.
This is the training that gets initiated on approving a bot publish request from Bot Admin Console. Or, when the bot is approved with ‘auto publish’ setting.

Shows the same status of the entire bot to all the bot users no matter who initiated the training.

Note: During the progress of an export or training job, the Platform doesn’t accept requests for another similar job. For example, if you are downloading a bot until the bot download completes with a success or failure, the platform doesn’t allow you to initiate another bot download.

Once a job is completed either successfully or otherwise, you can initiate another similar job again. In such cases, the dock automatically clears the previous entry and shows the progress of the latest job.

Next Steps

If you are new to Bot Builder, you should probably start with creating a simple alert task that can provide a notification message in your Kore.ai messaging account, or any other channel you define for that task. For more information, see About Alert Tasks.

Otherwise, you can try out any of our other task types.

  • Dialog Tasks – Consists of multiple sub-intents and component nodes to conduct a complex conversational flow between a user and the bot.
  • Alert Tasks – Monitors a web service for events and then sends a notification message to the user when the event occurs. You can use this task type for scheduled polling or near real-time notification using webhooks.
  • Information Tasks – Provides a report of data by asking the user for input parameters and then executing a web service call. The formatted data is presented to the user as a link to a report that a user can click to display the data, for example, Show my tickets, or 3-day Weather Forecast.
  • Action Tasks – Queries a user on demand for input parameters, and then executes a web service call along with a confirmation message, for example, Create New Ticket, or Get Weather for this Location.
  • Knowledge Graph – Turns static FAQ pages into intelligent, personalized conversational experience. Build an ontology of crucial terms, add questions to the right nodes in the hierarchy and leave the task of responding to users to the bot, thus enabling your Support staff to engage with more complex tasks.
  • Creating Flows – Associates one task to another task of the same or different Bot. For example, a flow for a Twitter tweet notification could be to Create New Follower.

Articles

Was this article helpful to you? Yes 23 No 2