About Information Tasks

This section describes the process to create a Bot information task. An information task executes an event in the corresponding Bot system, website, or web application and provides data accessible to the user by a hyperlink. This topic describes the process to create a new information task using the Kore.ai Bot Builder tool.

A Bot is a web site, web application, or system that you want to trigger and send an alert message to a Kore.ai account, or to initiate an action task for that Bot. For example, a Kore.ai task using the Bot for Twitter can be used to initiate a message every time you get a new follower on Twitter without having to open Twitter. When the message is displayed in the Kore.ai account, the user could initiate an action task, to follow the new follower. With an information task, you can define a report of all new followers by specific time periods and provide a link to the data as part of a regularly schedule report.

Before you can define an information task, you must first select or define a Bot for the corresponding task. For more information, see Creating a New Bot.

Kore.ai provides many built-in Bots with predefined tasks. For more information, see Adding a Kore.ai Bot.

Note: Only users with paid individual accounts, and users that are members of a space or company currently enrolled in a Kore.ai Premium plan can deploy custom Bots created in Bot Builder to other users.

Process for Defining Information Tasks

The steps that you need to complete to define an information task consists of four basic steps.

Step 1:General Tab Settings for an Information Task – The first step is to define how the task is displayed to the end-user such as the task name, connection mode, descriptions, and other advanced settings for NLP ignore words, search keywords, error messages, task confirmation messages, mapping restrictions, and Kore.ai Bot Store settings.

Step 3:API Request Tab – Information Task Request – REST – If required for your task, you can define a request object to, for example, provide a dynamic drop-down choice for the end-user to select from to complete the task. On the information task API Request tab, you can define API Parameters, optional API task Initializer, API Request pre- or post-processor, and the API Request. You will also need to add a Response Sample expected from your API Request payload.

Step 4:Defining the Bot Response for an Information Task – The Bot response provides a message to the end-user to inform the end-user of the status or completion of the task. On the Bot Response tab for a task, you can define the message to display to the end-user from the API request payload. You can define a default response for all channels, and optionally define channel-specific messages.

In Bot Builder, you can define the following report types for the Bot Response.

Table Report – The report is displayed in a table format with a variable-width columns.

Card Layout Report – The report is displayed as a list of cards, or text boxes with variable formatted data, including images.

Card Layout with Actions Report – The report is displayed as a list of cards, or text boxes with variable formatted data, including images, plus an option to associate action tasks to the report, such as Add to Cart.

Card Layout with Group By Report – The report is displayed as a list of cards, or text boxes with variable formatted data that can be group by a parameter key, such as date, size, or location. The card report includes images, plus an option to associate action tasks to the report, such as Add to Cart.

Shopping Cart Layout with Actions – The report is displayed as a list of shopping cart options, or text boxes with variable formatted data, including images, plus an option to associate action tasks to the report, such as Add to Cart.

Weather Info Report – The report is specifically designed to show a serial data string of weather info by date, day of the week, or forecast period.