Docs

Where to find what

This document is aimed at giving you an overview of the virtual assistant platform as a guide to the various feature offerings. Legacy UI The legacy Bot Builder has the left navigation menu which slides out on hover. New UI The new Bot builder has the elements categorized into main…

Subscription Plans

The Kore.ai Platform supports e-commerce journeys for subscriptions to various plans. It supports a pay-as-you-go model where you can start using the platform with free sessions. After the free sessions, you can reload your accounts with reasonable amounts (starting from $100), and be charged only for the consumed sessions. Usage…

Bot Action Node

The Bot Action Node can be used for any action that the bot is expected to perform without interaction with the user. It can be used as a container for service, script, webhook, logic and process nodes. This node type has been introduced in v. 9.0 of the XO Platform.…

Store

The Store is an online collection of bots that run on the Kore.ai XO Platform. The purpose of the store is to enable you as a bot developer to explore the bot’s capabilities and import them into your account.You must have a Kore.ai XO Platform account to use template bots…

Using nlMeta

At times one wants to control the flow of the virtual assistant by taking an alternate path to improve the user’s experience. Consider the following scenarios: The NLP engine might have identified an intent based on the user utterance. But a different task might be more suitable based on additional…

Alert Task – Advanced Settings

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. Learn more about Alert Tasks.…

Alert Task – Configuring the Schedule

As seen here, alert tasks only reach out to a web service for data when the VA 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

You can define filters for end-users to limit 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 filter applied, only alert messages…

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. Message Definition Overview To define the messages shown to a user when displaying an Alert Task,…

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…