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
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
Kore.ai XO GPT Module
Prompts & Requests Library
Co-Pilot Features
Dynamic Conversations Features
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
LLM and Generative AI Logs
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
Web SDK
How the Web SDK Works
SDK Security
SDK Registration
Web Socket Connect and RTM
Tutorials
Widget SDK Tutorial
Web SDK Tutorial
BotKit SDK
BotKit SDK Deployment Guide
Installing the BotKit SDK
Using the BotKit SDK
SDK Events
SDK Functions
Tutorials
BotKit - Blue Prism
BotKit - Flight Search Sample VA
BotKit - Agent Transfer
  1. Home
  2. Docs
  3. Virtual Assistants
  4. How Tos
  5. Scheduling a Smart Alert

Scheduling a Smart Alert

In this How-To, we will explore a scenario in a Bot, say traveling Bot, where the user needs to be provided with weather updates daily for a preferred location. We will be using an Alert task to achieve the same. We will also see how auto subscription can be enabled on this Alert task, making it smart.

For details on what Alert task is and how it is implemented in the Kore.ai Bots platform, refer here.

Problem Statement

A registered user of a Bot needs to be sent a weather update in the form of an alert, on a pre-specified time of the day and/or at a specified interval of time.

In this document, we will show how an Alert Task can be used to cater to such situations and take appropriate action.

Pre-requisites

  • Basic Bot building knowledge.
  • A working Bot, we are using a Banking Bot.
  • Access to a web service that gives a weather updates. We are using a REST service hosted at: http://api.openweathermap.org. If you want to use this service, you need register to their free alert service as we will be using the API key to access their APIs.

Implementation

Setting Alert Task

Alert tasks can be used to deliver timely, relevant, and personalized information from enterprise systems to customers and employees by polling the relevant service in real-time or according to a user-defined schedule.

Steps:

  1. From Build -> Conversational Skills add an Alert Task.
  2. On the task details page:
    1. Enter a Task Name, say Get Daily Weather
    2. Choose the Connection Type, we will go with Webservice
    3. Choose the Connection Mode, we will be using REST
    4. Click Create & Proceed
  3. You will be directed to the Alert Settings page
    1. Review and modify the General Settings if needed. For our use case, we do not need to modify any settings here.
    2. Select the API Request tab
      1. Ensure that the Content Type is set to JSON
      2. We do not need to set Authorization Provider for our use case. Configure the same if the API you are using has any authorization requirements.
      3. Set Parameter to gather the preferred City from the User. Ensure that it is set as a Mandatory field. This is the API requirement.
      4. We will not need any Initializer requirements for our use case. Use this in case any JavaScript needs to be executed before the request is sent.
      5. Under Request click Add API to add the service API that needs to be invoked. We are using a GET method from the following API: http://api.openweathermap.org/data/2.5/weather?q={cityname}&APPID=<your-app-id>
        • The APPID in the above url is assigned to you by OpenWeather when you sign up. You can find it from the API keys section after you login to your account.
        • Notice that the Parameters list is populated automatically with the parameters entered earlier.
        • Save the API.
        • Test the API to ensure that the configuration is proper. Enter a sample city name, when prompted and ensure you get a success message and a proper Response.
      6. Save the response.
    3. Next we need to format the Bot Response. For our use case, we will be parsing the weather description, temperature and humidity details returned by the API call to be presented to the user.
      We are using the following rich text to achieve the same:

      Todays weather details: <%=weather[0].description%>
      Temperature: <%=main.temp%>
      Humidity: <%=main.humidity%>


      The values returned by the API call can be accessed from the Variable Keys option. Clicking Variable Keys opens the Request/Response Keys window. The various variables available are categorized. Expand Response Keys section to access the response from API call and select the key for the value you want to display and click OK, the key will be inserted in the editor in the appropriate format, for example for the following selection –<%=weather[0].description%>

    4. Save the Message Definition.
    5. Select Setttings tab and expand the Schedule section. Use this section to configure an initial schedule, these are the options that are provided to the user to choose from for the initial setup.
      For example, in this example, we have set the schedule to be at 10:30 am daily followed by an update every 4 hrs. The user may choose just once at 10:30 am and not get the further updates.
    6. Finish Setup

Execution

Before publishing and sharing the Bot with a user, you can test it from the Talk to bot feature.

  1. Launch Talk to bot.
  2. Initiate the schedule task, Get Daily Weather (name of the Alert Task we configured).
  3. You will be prompted to enter city name.
  4. Next you will be prompted to enter a specific time, you can enter a time or enter “every x minutes”.
  5. As you can see if the time you enter does no match the scheduled time configured, the nearest time will be presented. Same is the case with the frequency setting.
  6. This is a one-time setup. From this point onwards whenever you launch Talk to Bot for this Bot, you will be given the Weather Alert at the specified time.
  7. The user can trigger the task using the Alert Task name, just like any other Dialog Task and set up the alert manually. The experience User will have when they start using your Bot will be similar to the above-mentioned flow.

Smart Alert

You can set the alert for the user automatically by adding the Alert Subscription Service type Service node in, say, a welcome dialog task. NOTE: Only published Alert Tasks are available for Alert subscription.

  1. Add a Service Node in the Dialog which will act as the trigger for the Alert Task.
  2. Set the Service Type to be Alert Subscription Service.
  3. Click Define Request and select the already configured Alert Task, in this case, Get Daily Weather.
    NOTE: Only published Alert Tasks are available for Alert subscription.
  4. You will be navigated to the Smart/Automatic Alerts window
  5. Set up the Alert Parameters as required.
  6. Set the Alert Frequency
  7. You can set the Alert Expiry values based upon either the duration of the subscription or the number of notifications sent, these will come in handy in case your subscription to the service is limited. Here we have set the Number of Notification to a maximum value.
  8. You can also define the Alert Upgrade behavior in case the Alert task is updated and published.
  9. Save
  10. You can trigger this task from Welcome or onConnect Event, so the user can enter their preferred city and time.
  11. On setup, the first time this service node is hit the subscription will be in effect without user intervention.

Scheduling a Smart Alert

In this How-To, we will explore a scenario in a Bot, say traveling Bot, where the user needs to be provided with weather updates daily for a preferred location. We will be using an Alert task to achieve the same. We will also see how auto subscription can be enabled on this Alert task, making it smart.

For details on what Alert task is and how it is implemented in the Kore.ai Bots platform, refer here.

Problem Statement

A registered user of a Bot needs to be sent a weather update in the form of an alert, on a pre-specified time of the day and/or at a specified interval of time.

In this document, we will show how an Alert Task can be used to cater to such situations and take appropriate action.

Pre-requisites

  • Basic Bot building knowledge.
  • A working Bot, we are using a Banking Bot.
  • Access to a web service that gives a weather updates. We are using a REST service hosted at: http://api.openweathermap.org. If you want to use this service, you need register to their free alert service as we will be using the API key to access their APIs.

Implementation

Setting Alert Task

Alert tasks can be used to deliver timely, relevant, and personalized information from enterprise systems to customers and employees by polling the relevant service in real-time or according to a user-defined schedule.

Steps:

  1. From Build -> Conversational Skills add an Alert Task.
  2. On the task details page:
    1. Enter a Task Name, say Get Daily Weather
    2. Choose the Connection Type, we will go with Webservice
    3. Choose the Connection Mode, we will be using REST
    4. Click Create & Proceed
  3. You will be directed to the Alert Settings page
    1. Review and modify the General Settings if needed. For our use case, we do not need to modify any settings here.
    2. Select the API Request tab
      1. Ensure that the Content Type is set to JSON
      2. We do not need to set Authorization Provider for our use case. Configure the same if the API you are using has any authorization requirements.
      3. Set Parameter to gather the preferred City from the User. Ensure that it is set as a Mandatory field. This is the API requirement.
      4. We will not need any Initializer requirements for our use case. Use this in case any JavaScript needs to be executed before the request is sent.
      5. Under Request click Add API to add the service API that needs to be invoked. We are using a GET method from the following API: http://api.openweathermap.org/data/2.5/weather?q={cityname}&APPID=<your-app-id>
        • The APPID in the above url is assigned to you by OpenWeather when you sign up. You can find it from the API keys section after you login to your account.
        • Notice that the Parameters list is populated automatically with the parameters entered earlier.
        • Save the API.
        • Test the API to ensure that the configuration is proper. Enter a sample city name, when prompted and ensure you get a success message and a proper Response.
      6. Save the response.
    3. Next we need to format the Bot Response. For our use case, we will be parsing the weather description, temperature and humidity details returned by the API call to be presented to the user.
      We are using the following rich text to achieve the same:

      Todays weather details: <%=weather[0].description%>
      Temperature: <%=main.temp%>
      Humidity: <%=main.humidity%>


      The values returned by the API call can be accessed from the Variable Keys option. Clicking Variable Keys opens the Request/Response Keys window. The various variables available are categorized. Expand Response Keys section to access the response from API call and select the key for the value you want to display and click OK, the key will be inserted in the editor in the appropriate format, for example for the following selection –<%=weather[0].description%>

    4. Save the Message Definition.
    5. Select Setttings tab and expand the Schedule section. Use this section to configure an initial schedule, these are the options that are provided to the user to choose from for the initial setup.
      For example, in this example, we have set the schedule to be at 10:30 am daily followed by an update every 4 hrs. The user may choose just once at 10:30 am and not get the further updates.
    6. Finish Setup

Execution

Before publishing and sharing the Bot with a user, you can test it from the Talk to bot feature.

  1. Launch Talk to bot.
  2. Initiate the schedule task, Get Daily Weather (name of the Alert Task we configured).
  3. You will be prompted to enter city name.
  4. Next you will be prompted to enter a specific time, you can enter a time or enter “every x minutes”.
  5. As you can see if the time you enter does no match the scheduled time configured, the nearest time will be presented. Same is the case with the frequency setting.
  6. This is a one-time setup. From this point onwards whenever you launch Talk to Bot for this Bot, you will be given the Weather Alert at the specified time.
  7. The user can trigger the task using the Alert Task name, just like any other Dialog Task and set up the alert manually. The experience User will have when they start using your Bot will be similar to the above-mentioned flow.

Smart Alert

You can set the alert for the user automatically by adding the Alert Subscription Service type Service node in, say, a welcome dialog task. NOTE: Only published Alert Tasks are available for Alert subscription.

  1. Add a Service Node in the Dialog which will act as the trigger for the Alert Task.
  2. Set the Service Type to be Alert Subscription Service.
  3. Click Define Request and select the already configured Alert Task, in this case, Get Daily Weather.
    NOTE: Only published Alert Tasks are available for Alert subscription.
  4. You will be navigated to the Smart/Automatic Alerts window
  5. Set up the Alert Parameters as required.
  6. Set the Alert Frequency
  7. You can set the Alert Expiry values based upon either the duration of the subscription or the number of notifications sent, these will come in handy in case your subscription to the service is limited. Here we have set the Number of Notification to a maximum value.
  8. You can also define the Alert Upgrade behavior in case the Alert task is updated and published.
  9. Save
  10. You can trigger this task from Welcome or onConnect Event, so the user can enter their preferred city and time.
  11. On setup, the first time this service node is hit the subscription will be in effect without user intervention.
Menu