GETTING STARTED
Kore.ai XO Platform
Virtual Assistants Overview
Natural Language Processing (NLP)
Concepts and Terminology
Quick Start Guide
Accessing the Platform
Navigating the Kore.ai XO Platform
Building a Virtual Assistant
Help & Learning Resources
Release Notes
Current Version
Recent Updates
Previous Versions
Deprecations
Request a Feature
CONCEPTS
Design
Storyboard
Overview
FAQs
Conversation Designer
Overview
Dialog Tasks
Mock Scenes
Dialog Tasks
Overview
Navigate Dialog Tasks
Build Dialog Tasks
Node Types
Overview
Intent Node
Dialog Node
Dynamic Intent Node
GenAI Node
GenAI Prompt
Entity Node
Form Node
Confirmation Node
Message Nodes
Logic Node
Bot Action Node
Service Node
Webhook Node
Script Node
Process Node
Agent Transfer
Node Connections
Node Connections Setup
Sub-Intent Scoping
Entity Types
Entity Rules
User Prompts or Messages
Voice Call Properties
Knowledge AI
Introduction
Knowledge Graph
Introduction
Terminology
Build a Knowledge Graph
Manage FAQs
Knowledge Extraction
Import or Export Knowledge Graph
Prepare Data for Import
Importing Knowledge Graph
Exporting Knowledge Graph
Auto-Generate Knowledge Graph
Knowledge Graph Analysis
Answer from Documents
Alert Tasks
Small Talk
Digital Skills
Overview
Digital Forms
Digital Views
Introduction
Widgets
Panels
Session and Context Variables
Context Object
Intent Discovery
Train
NLP Optimization
ML Engine
Overview
Model Validation
FM Engine
KG Engine
Traits Engine
Ranking and Resolver
Training Validations
NLP Configurations
NLP Guidelines
LLM and Generative AI
Introduction
LLM Integration
Prompts & Requests Library
Co-Pilot Features
Dynamic Conversations Features
Kore.ai XO GPT Model
Intelligence
Introduction
Event Handlers
Contextual Memory
Contextual Intents
Interruption Management
Multi-intent Detection
Amending Entities
Default Conversations
Conversation Driven Dialog Builder
Sentinment Management
Tone Analysis
Default Standard Responses
Ignore Words & Field Memory
Test & Debug
Overview
Talk to Bot
Utterance Testing
Batch Testing
Conversation Testing
Conversation Testing Overview
Create a Test Suite
Test Editor
Test Case Assertion
Test Case Execution Summary
Glossary
Health and Monitoring
NLP Health
Flow Health
Integrations
Actions
Actions Overview
Asana
Configure
Templates
Azure OpenAI
Configure
Templates
BambooHR
Configure
Templates
Bitly
Configure
Templates
Confluence
Configure
Templates
DHL
Configure
Templates
Freshdesk
Configure
Templates
Freshservice
Configure
Templates
Google Maps
Configure
Templates
Here
Configure
Templates
HubSpot
Configure
Templates
JIRA
Configure
Templates
Microsoft Graph
Configure
Templates
Open AI
Configure
Templates
Salesforce
Configure
Templates
ServiceNow
Configure
Templates
Stripe
Configure
Templates
Shopify
Configure
Templates
Twilio
Configure
Templates
Zendesk
Configure
Templates
Agents
Agent Transfer Overview
Custom (BotKit)
Drift
Genesys
Intercom
NiceInContact
NiceInContact(User Hub)
Salesforce
ServiceNow
Configure Tokyo and Lower versions
Configure Utah and Higher versions
Unblu
External NLU Adapters
Overview
Dialogflow Engine
Test and Debug
Deploy
Channels
Publishing
Versioning
Analyze
Introduction
Dashboard Filters
Overview Dashboard
Conversations Dashboard
Users Dashboard
Performance Dashboard
Custom Dashboards
Introduction
Custom Meta Tags
Create Custom Dashboard
Create Custom Dashboard Filters
NLP Insights
Task Execution Logs
Conversations History
Conversation Flows
Conversation Insights
Feedback Analytics
Usage Metrics
Containment Metrics
Universal Bots
Introduction
Universal Bot Definition
Universal Bot Creation
Training a Universal Bot
Universal Bot Customizations
Enabling Languages
Store
Manage Assistant
Team Collaboration
Plan & Usage
Overview
Usage Plans
Templates
Support Plans
Invoices
Authorization
Conversation Sessions
Multilingual Virtual Assistants
Get Started
Supported Components & Features
Manage Languages
Manage Translation Services
Multiingual Virtual Assistant Behavior
Feedback Survey
Masking PII Details
Variables
Collections
IVR Settings
General Settings
Assistant Management
Manage Namespace
Data
Overview
Data Table
Table Views
App Definitions
Data as Service
HOW TOs
Build a Travel Planning Assistant
Travel Assistant Overview
Create a Travel Virtual Assistant
Design Conversation Skills
Create an ‘Update Booking’ Task
Create a Change Flight Task
Build a Knowledge Graph
Schedule a Smart Alert
Design Digital Skills
Configure Digital Forms
Configure Digital Views
Train the Assistant
Use Traits
Use Patterns
Manage Context Switching
Deploy the Assistant
Use Bot Functions
Use Content Variables
Use Global Variables
Use Web SDK
Build a Banking Assistant
Design Conversation Skills
Create a Sample Banking Assistant
Create a Transfer Funds Task
Create a Update Balance Task
Create a Knowledge Graph
Set Up a Smart Alert
Design Digital Skills
Configure Digital Forms
Configure Digital Views
Add Data to Data Tables
Update Data in Data Tables
Add Data from Digital Forms
Train the Assistant
Composite Entities
Use Traits
Use Patterns for Intents & Entities
Manage Context Switching
Deploy the Assistant
Configure an Agent Transfer
Use Assistant Functions
Use Content Variables
Use Global Variables
Intent Scoping using Group Node
Analyze the Assistant
Create a Custom Dashboard
Use Custom Meta Tags in Filters
Migrate External Bots
Google Dialogflow Bot
APIs & SDKs
API Reference
API Introduction
Rate Limits
API List
koreUtil Libraries
SDK Reference
SDK Introduction
SDK Security
SDK Registration
Web Socket Connect and RTM
Installing the BotKit SDK
Using the BotKit SDK
SDK Events
SDK Functions
SDK Tutorials
BotKit - Blue Prism
BotKit - Flight Search Sample VA
BotKit - Agent Transfer
Widget SDK Tutorial
Web SDK Tutorial
ADMINISTRATION
Introduction to Admin Console
Administration Dashboard
User Management
Add Users
Manage Groups
Manage Roles
Data Tables and Views
Assistant Management
Enrollment
Invite Users
Send Bulk Invites
Import User Data
Synchronize Users from AD
Security & Control
Using Single-Sign On (SSO)
Two-Factor Authentication (2FA)
Security Settings
Cloud Connector
Analytics
Billing
  1. Home
  2. Docs
  3. Virtual Assistants
  4. How Tos
  5. Travel Planing Assistant
  6. Create a Change Flight Task

Create a Change Flight Task

This document is part of the documentation related to creating a sample travel assistant. 

Assistant Capabilities

The assistant we build will perform basic travel booking tasks, as follows:

  • Check the status of a flight, based on the flight number provided by the user, as seen here.
  • Update a flight booking, as discussed here.
  • Perform a flight change, based on the current flight and new flight preference provided by the user. as discussed in this present article.

Add the Change Flight Dialog Task / Intent

  • The Change Flight  task will prompt the user to enter their Current and New Flight Numbers.  numbers.
  • Next it would prompt for the Seat preference.
  • It will then make a service call to update the booking appropriately.
  • The message indicating success or failure is displayed before the end of the dialog.

To add this Dialog Task, follow the steps below:

  1. Open the Travel Planning Assistant, with the two pre-configured tasks – Check Flight Status and Update Booking.
  2. Navigate to the Build > Conversational Skills -> Dialog Task page from the left menu.
  3. Click Create Dialog from the top right. The Create Dialog screen will open.
  4. Enter the following details:
    1. Intent Name – Enter the Intent name, this is the phrase that triggers the dialog. The intent name should be simple and not more than 3-4 words. For example, Change Flight.
    2. Under More Options, you can add a description and other dialog-related details. Let’s retain the default settings.
    3. You can also include utterances to train this intent.
    4. Select Try Conversation Driven Dialog Builder option.
  5. Click Proceed.

    Note: For instructions related to the Legacy Dialog Builder, refer here

  6. Close the User Intent Property Panel.

Add Entity nodes

An Entity Node is typically used to gather information from the user.

Here we will be using it to capture the user input for the Current Flight (to change from) and New Flight (to change to). 

Add an Entity Node to retrieve the Current Flight to change from, 

  1. Click the + below to the User Intent node
  2. Select the Entity option
  3. Click the + New entity. The Property Panel for the Entity Node is displayed. If not click on the newly added entity node to open
  4. Enter the following details:
    1. Name: CurrentFlight
    2. Display Name: Current Flight
    3. Type: String
    4. User Prompts: Enter the following text:
      Enter the Current Flight that you want to change from
    5. Close the CurrentFlight Entity Property Panel.

 

Add an Entity Node to retrieve the New Flight to change to

  1. Repeat the above steps to add another entity with the following details:
    1. Name: NewFlight
    2. Display Name: New Flight 
    3. Type: String
    4. User Prompts: Enter the following text
      Enter the New Flight that you want to change to. 
  2. Close the NewFlight Entity Property Panel.

 

Add a Seat Selection Entity Node

  1. Repeat the above steps to add another entity with the following details:
    1. Name: Seat
    2. Display Name: Seat
    3. Type: List of items (Enumerated). We need to provide the list of values that the user can select.
      1. Click the Settings (gear) icon that appears next to the field.
      2. Opt for Static List.
      3. Enter the following options under separate rows as the Display name  e.g.: 21A, 25C, 32F. Value and Synonym columns will auto-populate, leave them as is.
      4. Define the percentage of Auto-correction to be applied to match the user’s input to a value in the list.
      5. Click Save.

      6. Under Display List of Values, select Yes, use channel specific standard formatting for default messages and show an available list of values to the end user.
    4. User Prompts: Enter the following text
      Please select a seat.

      Note: You can use Javascript in the User Prompt to display available seats. In this case you would need to set the Type as ‘String’. For the purpose of this use case, we have chosen to list fixed values, which is why we have set the Type to ‘List of Items’.

    5. Close the Seat Entity Property Panel.

Add a Bot Action – Service Node

A Service Node allows you to make a backend API call. It is included in the Bot Actions node. Here the service node is used to call an API to update the provided booking based on the user’s input, with the new flight and the selected seat.

To add a Bot Action – Service Node:

  1. Click the + below the Seat Entity node
  2. Select Bot Action, click to open properties, name it UpdateBooking, and close the properties window.
  3. To add a service node, click the + next to the Update Booking Bot Action node to expand it
  4. Click the + within the Bot Action layout, and select Service.
  5. Click + New Service
  6. The Property Panel for the Service Node is displayed, if not click on the newly created entity node to open it.
  7. Enter the following details:
    1. Name: UpdateBookingService
    2. Display Name: Update Booking Service
  8. Under Request Definition: click Define Request. Here is an example request to enter:
    https://5c3c633d29429300143fe4d2.mockapi.io:{{context.entities.CurrentFlight}}./BookingDetails/{{context.entities.NewFlight}}./BookingDetails/{{context.entities.Seat}}.

Add a Message Node

A Message Node is used to display a message from the VA to the user. Here we will be using the Message node to confirm the update to the user..

  1. Click the + below the UpdateBooking Bot Action node. 
  2. Select Message and click + New message. The Property Panel for the Message Node is displayed. If not click on the newly added dialog node to open
  3. Enter the following details:
    1. Name: FlightChangeConfirmation
    2. Display Name: Flight Change Confirmation
    3. Bot Responses: The flight {{context.entities.CurrentFlight}} has been changed to flight  {{context.entities.NewFlight}} seat {{context.entities.Seat}}
  4. On the Bot Response Property Panel, open the connections tab by clicking the Connections icon.
  5. Change the Default connection from Not Connected to End of Dialog.
  6. Close the Property Panel.

The completed task might look similar to the illustration below:

Test the Assistant

To test the Dialog task, you can use the Talk to Bot feature at the bottom right corner of the Platform.

Enter the following utterance (intent name)

Change Flight

Follow the instructions:

  • Enter the Current Flight;
  • Enter the New Flight;
  • Select the Seat;
  • See the success message.

Create a Change Flight Task

This document is part of the documentation related to creating a sample travel assistant. 

Assistant Capabilities

The assistant we build will perform basic travel booking tasks, as follows:

  • Check the status of a flight, based on the flight number provided by the user, as seen here.
  • Update a flight booking, as discussed here.
  • Perform a flight change, based on the current flight and new flight preference provided by the user. as discussed in this present article.

Add the Change Flight Dialog Task / Intent

  • The Change Flight  task will prompt the user to enter their Current and New Flight Numbers.  numbers.
  • Next it would prompt for the Seat preference.
  • It will then make a service call to update the booking appropriately.
  • The message indicating success or failure is displayed before the end of the dialog.

To add this Dialog Task, follow the steps below:

  1. Open the Travel Planning Assistant, with the two pre-configured tasks – Check Flight Status and Update Booking.
  2. Navigate to the Build > Conversational Skills -> Dialog Task page from the left menu.
  3. Click Create Dialog from the top right. The Create Dialog screen will open.
  4. Enter the following details:
    1. Intent Name – Enter the Intent name, this is the phrase that triggers the dialog. The intent name should be simple and not more than 3-4 words. For example, Change Flight.
    2. Under More Options, you can add a description and other dialog-related details. Let’s retain the default settings.
    3. You can also include utterances to train this intent.
    4. Select Try Conversation Driven Dialog Builder option.
  5. Click Proceed.

    Note: For instructions related to the Legacy Dialog Builder, refer here

  6. Close the User Intent Property Panel.

Add Entity nodes

An Entity Node is typically used to gather information from the user.

Here we will be using it to capture the user input for the Current Flight (to change from) and New Flight (to change to). 

Add an Entity Node to retrieve the Current Flight to change from, 

  1. Click the + below to the User Intent node
  2. Select the Entity option
  3. Click the + New entity. The Property Panel for the Entity Node is displayed. If not click on the newly added entity node to open
  4. Enter the following details:
    1. Name: CurrentFlight
    2. Display Name: Current Flight
    3. Type: String
    4. User Prompts: Enter the following text:
      Enter the Current Flight that you want to change from
    5. Close the CurrentFlight Entity Property Panel.

 

Add an Entity Node to retrieve the New Flight to change to

  1. Repeat the above steps to add another entity with the following details:
    1. Name: NewFlight
    2. Display Name: New Flight 
    3. Type: String
    4. User Prompts: Enter the following text
      Enter the New Flight that you want to change to. 
  2. Close the NewFlight Entity Property Panel.

 

Add a Seat Selection Entity Node

  1. Repeat the above steps to add another entity with the following details:
    1. Name: Seat
    2. Display Name: Seat
    3. Type: List of items (Enumerated). We need to provide the list of values that the user can select.
      1. Click the Settings (gear) icon that appears next to the field.
      2. Opt for Static List.
      3. Enter the following options under separate rows as the Display name  e.g.: 21A, 25C, 32F. Value and Synonym columns will auto-populate, leave them as is.
      4. Define the percentage of Auto-correction to be applied to match the user’s input to a value in the list.
      5. Click Save.

      6. Under Display List of Values, select Yes, use channel specific standard formatting for default messages and show an available list of values to the end user.
    4. User Prompts: Enter the following text
      Please select a seat.

      Note: You can use Javascript in the User Prompt to display available seats. In this case you would need to set the Type as ‘String’. For the purpose of this use case, we have chosen to list fixed values, which is why we have set the Type to ‘List of Items’.

    5. Close the Seat Entity Property Panel.

Add a Bot Action – Service Node

A Service Node allows you to make a backend API call. It is included in the Bot Actions node. Here the service node is used to call an API to update the provided booking based on the user’s input, with the new flight and the selected seat.

To add a Bot Action – Service Node:

  1. Click the + below the Seat Entity node
  2. Select Bot Action, click to open properties, name it UpdateBooking, and close the properties window.
  3. To add a service node, click the + next to the Update Booking Bot Action node to expand it
  4. Click the + within the Bot Action layout, and select Service.
  5. Click + New Service
  6. The Property Panel for the Service Node is displayed, if not click on the newly created entity node to open it.
  7. Enter the following details:
    1. Name: UpdateBookingService
    2. Display Name: Update Booking Service
  8. Under Request Definition: click Define Request. Here is an example request to enter:
    https://5c3c633d29429300143fe4d2.mockapi.io:{{context.entities.CurrentFlight}}./BookingDetails/{{context.entities.NewFlight}}./BookingDetails/{{context.entities.Seat}}.

Add a Message Node

A Message Node is used to display a message from the VA to the user. Here we will be using the Message node to confirm the update to the user..

  1. Click the + below the UpdateBooking Bot Action node. 
  2. Select Message and click + New message. The Property Panel for the Message Node is displayed. If not click on the newly added dialog node to open
  3. Enter the following details:
    1. Name: FlightChangeConfirmation
    2. Display Name: Flight Change Confirmation
    3. Bot Responses: The flight {{context.entities.CurrentFlight}} has been changed to flight  {{context.entities.NewFlight}} seat {{context.entities.Seat}}
  4. On the Bot Response Property Panel, open the connections tab by clicking the Connections icon.
  5. Change the Default connection from Not Connected to End of Dialog.
  6. Close the Property Panel.

The completed task might look similar to the illustration below:

Test the Assistant

To test the Dialog task, you can use the Talk to Bot feature at the bottom right corner of the Platform.

Enter the following utterance (intent name)

Change Flight

Follow the instructions:

  • Enter the Current Flight;
  • Enter the New Flight;
  • Select the Seat;
  • See the success message.

Menu