Builder

Knowledge Graph

A component of Kore.ai’s XO Platform, the Knowledge Graph (KG), helps you turn static FAQ text into an intelligent, personalized conversational experience. It goes beyond the usual practice of capturing FAQs as flat question-answer pairs, allowing you to either build an ontology structure or leverage Kore.ai’s LLM to simplify knowledge…

Confirmation Nodes

The Confirmation Node allows you to prompt the user for a Yes or No answer. It helps when you want to verify information or allow the user to make a choice. For example, in the Book Flight Bot, you can use a confirmation node to prompt the user to respond…

Dialog Node

The Dialog Node lets you start a new dialog task within an existing dialog task if the user intent changes. For example, let us consider a travel assistant that has the following three dialog tasks: Flight Availability, Book a Flight, Book a Hotel. While handling a user’s intention to check…

Using Session and Context Variables in Tasks

When you define tasks, you can access session variables provided by the Bots Platform, or custom variables that you define, as well as the context object that defines the scope of the variable. For example, some API requests may require you to set session variables before request execution, or a dialog…

User Prompts

After creating an Entity, Confirmation, or Message node in the Dialog Builder, Kore.ai lets you do the following: Modify the default message or user prompt displayed to the end-user. Add new prompts or messages. Add channel-specific prompts or messages. Prompt Types Dialog Tasks support two types of user prompts: Standard:…

Context Object

The Context object is the container object that persists data for dialog execution and across all intents i.e. dialog tasks, action, alert & info tasks, and FAQs. Kore.ai’s natural language processing (NLP) engine populates the intent identified, entities extracted, and history into this object. Keys from the Context object are…

Custom Meta Tags

While analyzing your Virtual Assistant’s performances, you might want to give preference to or discard a particular scenario. For example, you might want to track how many people are booking tickets to Chicago. Or you might want to track how a specific user, a premium customer, requests are being fulfilled.…

User Intent Node

As a bot developer, you typically create a task to resolve one primary user intent. Yet, user conversations can branch into related intents (follow-up or sub-intents) as a part of the primary intent. Let us take a look into this sample conversation for a flight booking assistant: VA: Hi, how…

Managing Dialogs

Your bot can have many dialog tasks with related components. You can use the Dialog Editor to create, review, and edit a single dialog task for a bot. However, to better visualize and understand relationships and settings for all dialog tasks in a bot, you must use the Manage Components…

Message (Bot Response) Nodes

The Message Node is used to deliver a message to the user. Message nodes commonly follow an API, web service call, or webhook event to define their results as a formatted response. You can format bot responses as below: Plain text: Type a message in plain text. You can use…