Builder

Conversation-driven Dialog Builder

Conversation Builder is a new dialog task editor which allows you to design and build a dialog task using conversational elements. It leverages the features of Storyboard and the Flow-based Dialog Task Builder. While the Storyboard helps in designing and visualizing the user conversations, the bot needs to be developed…

Data as Service

Kore.ai’s Data offering lets you define Data Tables, Table Views, and manipulate them from your Virtual Assistant. This section deals with the manipulation aspect using the Service Node within a Dialog Task of your Virtual Assistant. For details on the data definition, refer here. Service Call – Table From the…

Taxonomy-based KG

The Kore.ai platform provides a Taxonomy-based model in the Knowledge Graph to enhance the path qualification. The default Knowledge Graph model works on a two-step model i.e. path qualification and followed by question matching. The path need not be fully qualified at all times. Even a partial path match (above…

Dialog Task – Legacy Builder

In a bid to improve useability and user experience, the dialog builder was given a makeover. You are given a choice to upgrade to the new builder or continue with the legacy builder, though we encourage you to go for the upgrade. This document deals with using the legacy dialog…

VA Action Node

The VA Action Node can be used for any action that the Virtual Assistant is expected to perform without interaction with the user. It is a collection service, script, webhook, and Logic nodes. Set-Up Setting up a VA action node in a dialog task involves the following steps: Add Node…

Alert Task – Advanced Settings

As seen here, in the Advanced Settings section, you can define alert task settings for enabling and limiting the initial set of alert messages displayed to the end-user when the task is set up, define alert message reminders, and if required, prevent duplicate messages sent to the user. Defined Advanced…

Alert Task – Configuring the Schedule

As seen here, alert tasks only reach out to a web service for data when the Bot makes a request. For each task, you need to define when, and how often the web service is queried for data for an alert message. You can define the scheduling options presented to…

Alert Task – Defining Filters

As we have seen here, you can define filters for end-users to limits the results of an alert task to the results an end-user needs. For example, you can define a filter for the name, or account, or business. When the alert is set up by the end-user, and the…

Alert Task – Message Definition

For some Alert tasks, as seen here, you can define the look and feel of the data presented to the end-user when the alert is displayed based on the payload delivered by the webhook. Defining the Message Definition You can define two kinds of bot responses for a task: The default…

Alert Task – Report Templates

For some Alert tasks, as seen here, you may want to display the bot response to the end-user as a link that can display the payload response using a template, such as a table, contact card, or formatted for a specific message type such as a weather report. Note: This…