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. Builder
  5. Dialog Task
  6. Confirmation Nodes

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 if they would like to know the weather forecast at the destination.

The confirmation node’s conditional transitions go beyond the If-Else expressions. The transition depends on user reply: assertion (yes) or negation (no). The Else condition comes into play if their answer isn’t both.

Add the Node

Setting up a confirmation node in a dialog task involves the following steps:

  1. Open the dialog task to which you want to add the Confirmation node.
  2. Add a Confirmation node in the designated place. For steps related to adding nodes, Learn more.
  3. By default, the Confirmation window is displayed in the Component Properties tab.


Configure the Node

Component Properties

Notes

  • The configurations you set up or edit in these sections reflect in all other dialog tasks that use this node
  • This article works with the new dialog builder, you will find this feature in legacy builder at the same location i.e. Confirmation node -> Component Properties.

 

To configure the component properties, follow the below steps:

  1. On the Component Properties tab, under the General Settings section, enter a Name and a Display Name.
  2. Under the User Prompts section, you can compose the confirmation request either as plain text or as a JavaScript message.center channel-specific messages for User Prompts using the Manage link. For more information, refer to the Using the Prompt Editor article.
    1. To add more prompts , click Add a Prompt and repeat the above steps.
    2. Enable the channel-specific standard formatting to Display Confirmation Options
      If this is not enabled, the yes/no options will not be displayed to the end-user.
    3. Platform detection of Yes/No is based on the below keywords. The platform ensures that the yes/no synonyms, including the internal ones, are processed at the same time and the earliest choice  takes precedence. This means that something like of course not is considered as NO, and is not mapped  to YES because of course could also be part of the YES synonym. Also, the yes/no synonyms are concepts and patterns as well.

      For yes:

      ‘kay, <I agree, <I am>, <I am certain>, <I am listening>, <I am pleased to>, <I am sure>, <I can believe it>, <I can believe that>, <I can see that>, <I can try>, <I consent, <I could not agree with you more, <I did>, <I do>, <I give consent, <I give my consent, <I guess so, <I have no objection, <I think so, <I totally agree, <I understand>, <I will drink to that, <O.K., <OK, <a’ight, <a’right, <absolutely, <accept>, <accepted>, <ack, <affirmative>, <agreed, <ah yes, <all right, <alright, <always>, <apparently>, <approved, <ay, <aye, <be my guest, <beyond a doubt>, <bring it on>, <but of course, <by all means, <can not argue with that, <certainly>, <completely, <confirmed, <constantly>, <continue, <correct>, <could be>, <could not have said it better, <da, <damn good, <damn straight, <definitely, <delighted, <do it>, <especially, <evidently>, <exactly, <extremely>, <fantastic>, <fine>, <for sure, <fortune smiles on that, <fully, <generally, <go ahead>, <go ahead with, <he does>, <he is>, <hell yeah, <highly likely>, <how true>, <i guess>, <in this case>, <indeed, <indefinitely, <indubitably>, <it does>, <it is>, <it is highly likely>, <it will be a pleasure to, <it will be my pleasure to, <it would be a pleasure, <let us try>, <make it so>, <makes sense, <most assuredly, <most certainly, <mostly>, <my pleasure>, <naturally>, <no doubt, <no objections>, <no problem>, <nod, <nods, <o.k., <of course, <oh alright, <oh okay, <oh sure, <ok, <okey dokey, <one hundred percent, <only just>, <perfect>, <please do>, <positively, <precisely, <probably>, <right>, <right ,, <right brah, <right on, <righto, <righty-ho, <she does>, <she is>, <shure, <si, <so will you, <sounds wonderful, <supposedly, <sure, <sure thing, <surely, <that is alright, <that is correct, <that is good, <that is right, <thats great , yes, <thats great yes, <they are>, <they do>, <thumbs up, <totally, <true>, <two thumbs up, <uh-huh, <undoubtedly, <unquestionably, <very well, <very well indeed, <we can try>, <we did>, <we do>, <we should try>, <well maybe you are right, <well perhaps you are right, <whatever>, <will do>, <with pleasure, <without a doubt, <wonderful>, <yah, <yay, <yea, <yeah, <yeah definitely, <yeah sure, <yeh, <yep, <yeppers, <yes, <yes please, <yes really, <yip, <you are right, <you bet>, <you could say that>, <you may, <you may be right, <you may have a point, <yup, <yuppers, I would say so, Y, d’accord, it_is_ok, its_ok, okay, okey, positive, right-o, touche, why_not, will_be_nice, ya, yes, yo, you_bet_you, ys

      For no:
      <I am afraid I disagree with you, <I am afraid I do not agree, <I am afraid not, <I am not sure I agree, <I am not sure that I, <I could not disagree more, <I disagree, <I do not>, <I do not agree, <I do not believe it>, <I do not believe so, <I do not believe you>, <I do not think so, <I do not want to>, <I dont think so, <I doubt it, <I just do not get it, <I refuse>, <I think not, <I will not>, <I would not>, <but no, <but of course not, <by no means, <come off it, <did not>, <disagree, <do not be absurd, <do not be ridiculous, <do not be silly, <do not be stupid, <does not seem likely>, <does not seem possible>, <doubtful, <false>, <fat chance, <fortune does not smile on that, <get out>, <get real, <hardly, <he does not>, <he is not>, <hell no, <horse hockey, <if you say so, <iie, <impossible, <improbable, <inconceivable>, <it does not>, <it is not>, <it is not possible, <it is unlikely>, <me thinks not, <most certainly not, <naaah, <naah, <nah, <naw, <nay, <neah, <negative, <neither, <neither of these, <never, <never>, <never mind>, <no, <no>, <no !, <no ,, <no -, <no ., <no I am fine, <no I am good, <no I am ok, <no can do, <no chance>, <no thank you, <no thanks, <no way, <no way>, <none, <none of them, <none of these, <noo, <nope, <not a chance, <not a prayer>, <not a snowball ‘s chance in hell, <not any of them, <not at all, <not at all>, <not at the moment, <not by a long shot, <not by any means, <not especially, <not exactly, <not in a million years, <not likely>, <not many>, <not much>, <not on your life, <not particularly, <not really, <not so much>, <not sure, <not that I know of, <not to my knowledge>, <not to speak of, <not very often>, <nuts to you, <of course not, <oh come on, <on the contrary>, <rubbish, <seldom, <she does not>, <she is not>, <strange, <surely not, <that is impossible, <that is rubbish, <that is unbelievable, <there is no reason to think so, <they are not>, <they do not>, <thinks not, <uh-hu, <uh-uh, <uhuh, <unbelievable, <unfortunately not, <unlikely, <unlikely>, <we do not>, <yeah yeah, <you are dead wrong, <you are having me on, <you are joking, <you are kidding, <you are not serious, <you are winding me up, <you can not be serious, <you have got that wrong, <you have got to be kidding, <you must be joking, <you must be kidding, N, do_not, instead, maybe_at_another_time, n, neither, no, not_OK, not_at_a_time, not_ever, not_now, nothing
      In both cases, “<” means the start of the sentence and “>” means the end of the sentence.  Many of these words are only treated as a yes or no if they appear at the start or the end of an utterance, not in the middle.
  3. You can use Rephrase Responses to rewrite VA replies using AI based on conversation context and user emotions. For Confirmation nodes, this feature helps rephrase the responses entered under User Prompts. To see this feature in your node’s Component Properties, enable the OpenAI or Azure-OpenAI integration and the Dynamic Prompt and Message Rephrasing feature under LLM and Generative AI.  By default, this feature is disabled for each node. Turn on the toggle to enable Rephrase Responses.Configure the number of previous user inputs to define  how many previous user messages should be sent to OpenAI as context based on which to rephrase the response sent through the node. You can choose between 0 and 5, where 0 means that no previous input is considered, while 5 means that the previous 5 responses are sent as context.
  4. Add context-specific Synonyms for Yes and No within the Confirmation node to suit the dialog’s context. The Platform can identify the emojis in user utterance and consider them for confirmation/rejection, for example, a thumbs-up emoji will be taken to mean confirmation from the user.

    Note: The Platform now supports additional Synonyms for Traditional Chinese language for Yes/No confirmation. Learn more.

  5. In the Variable Namespaces section, associate the variable namespaces to execute this node and its transitions. This option is visible only when the Variable Namespace is enabled for the assistant you are working with. You can go with the task level settings or customize it for this node. For more information, refer to the Managing Namespace article.

Additional Synonyms for Traditional Chinese Language

For the Traditional Chinese language, the Platform provides the following additional synonyms for “yes” and “no” responses on the Confirmation node:

Yes Confirmation

"係", "係呀", "講得啱", "啱", "冇問題"

No Confirmation

"唔係", "冇", "無", "唔得", "唔可以", "唔使", "唔要", "唔想", "唔啱"

These synonyms can be configured on the confirmation node under Component Properties > Synonyms during the Build stage of a Dialog Task.

After detecting these additional synonyms, the Confirmation node extracts “yes” or “no” from the user utterance.

Instance Properties

  1. On the Confirmation Component Properties window, click the Instance Properties tab.
  2. Under the Interruptions Behavior section, you can configure the interruptions behavior for this node.

    Note: The settings in the Instance Properties tab are specific to the current task and do not reflect in other dialog tasks that use this node
    1. Use the task level ‘Interruptions Behavior’ setting: The VA refers to the Interruptions Behavior settings set at the dialog task level.
    2. Customize for this node option: You can customize the Interruptions Behavior settings for this node by selecting this option and configuring it. For more information refer to the Interruption Handling and Context Switching article.
  3. Under the Precedence section, when the user’s input for an entity consists of a valid value for the entity and another intent, you can control the experience by choosing between Intent over Entity or Entity over Intent options. For example, if a Flight Booking assistant prompts for the destination and the user enters, Bangalore, how’s the weather there? you can define how the bot responds in such cases; pick the entity and add the intent to the follow-up intents stack or go ahead with the intent first based upon the Interruptions Behavior settings.
  4. Under the Custom Tags section, add tags to build custom profiles of your VA conversations. Learn more.

IVR Properties

Use  the IVR properties tab on the Confirmation Node to define the initial prompts, timeout prompts, no match prompts, and error prompts with customization for the retries behavior, input mode, grammar settings for Global and Node level use cases, prompts, and call behavior parameters for this node to use in IVR Channel. These settings are defined at the Confirmation Node level. For more information, read the Voice Call Properties article.

Note: The Confirmation Node supports all voice call properties for the  IVR, Audio Codes, Twilio Voice, and Voice Gateway channels. Except the IVR Data Extraction Key property is not supported.


Connections Properties

The Confirmation node’s conditional transitions go beyond the If-Else expressions used for the other nodes. You can define conditional expression based on a context object value, else a user assertion (yes), or else user negation (no). Beyond the three, you can define a fallback Else condition to trigger. 

Note: These conditions are applicable only for this instance and will not affect the node when being used in any other dialog.

For details on how to work with connection conditions,  read the Adding IF-Else Conditions to Node Connections article.

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 if they would like to know the weather forecast at the destination.

The confirmation node’s conditional transitions go beyond the If-Else expressions. The transition depends on user reply: assertion (yes) or negation (no). The Else condition comes into play if their answer isn’t both.

Add the Node

Setting up a confirmation node in a dialog task involves the following steps:

  1. Open the dialog task to which you want to add the Confirmation node.
  2. Add a Confirmation node in the designated place. For steps related to adding nodes, Learn more.
  3. By default, the Confirmation window is displayed in the Component Properties tab.


Configure the Node

Component Properties

Notes

  • The configurations you set up or edit in these sections reflect in all other dialog tasks that use this node
  • This article works with the new dialog builder, you will find this feature in legacy builder at the same location i.e. Confirmation node -> Component Properties.

 

To configure the component properties, follow the below steps:

  1. On the Component Properties tab, under the General Settings section, enter a Name and a Display Name.
  2. Under the User Prompts section, you can compose the confirmation request either as plain text or as a JavaScript message.center channel-specific messages for User Prompts using the Manage link. For more information, refer to the Using the Prompt Editor article.
    1. To add more prompts , click Add a Prompt and repeat the above steps.
    2. Enable the channel-specific standard formatting to Display Confirmation Options
      If this is not enabled, the yes/no options will not be displayed to the end-user.
    3. Platform detection of Yes/No is based on the below keywords. The platform ensures that the yes/no synonyms, including the internal ones, are processed at the same time and the earliest choice  takes precedence. This means that something like of course not is considered as NO, and is not mapped  to YES because of course could also be part of the YES synonym. Also, the yes/no synonyms are concepts and patterns as well.

      For yes:

      ‘kay, <I agree, <I am>, <I am certain>, <I am listening>, <I am pleased to>, <I am sure>, <I can believe it>, <I can believe that>, <I can see that>, <I can try>, <I consent, <I could not agree with you more, <I did>, <I do>, <I give consent, <I give my consent, <I guess so, <I have no objection, <I think so, <I totally agree, <I understand>, <I will drink to that, <O.K., <OK, <a’ight, <a’right, <absolutely, <accept>, <accepted>, <ack, <affirmative>, <agreed, <ah yes, <all right, <alright, <always>, <apparently>, <approved, <ay, <aye, <be my guest, <beyond a doubt>, <bring it on>, <but of course, <by all means, <can not argue with that, <certainly>, <completely, <confirmed, <constantly>, <continue, <correct>, <could be>, <could not have said it better, <da, <damn good, <damn straight, <definitely, <delighted, <do it>, <especially, <evidently>, <exactly, <extremely>, <fantastic>, <fine>, <for sure, <fortune smiles on that, <fully, <generally, <go ahead>, <go ahead with, <he does>, <he is>, <hell yeah, <highly likely>, <how true>, <i guess>, <in this case>, <indeed, <indefinitely, <indubitably>, <it does>, <it is>, <it is highly likely>, <it will be a pleasure to, <it will be my pleasure to, <it would be a pleasure, <let us try>, <make it so>, <makes sense, <most assuredly, <most certainly, <mostly>, <my pleasure>, <naturally>, <no doubt, <no objections>, <no problem>, <nod, <nods, <o.k., <of course, <oh alright, <oh okay, <oh sure, <ok, <okey dokey, <one hundred percent, <only just>, <perfect>, <please do>, <positively, <precisely, <probably>, <right>, <right ,, <right brah, <right on, <righto, <righty-ho, <she does>, <she is>, <shure, <si, <so will you, <sounds wonderful, <supposedly, <sure, <sure thing, <surely, <that is alright, <that is correct, <that is good, <that is right, <thats great , yes, <thats great yes, <they are>, <they do>, <thumbs up, <totally, <true>, <two thumbs up, <uh-huh, <undoubtedly, <unquestionably, <very well, <very well indeed, <we can try>, <we did>, <we do>, <we should try>, <well maybe you are right, <well perhaps you are right, <whatever>, <will do>, <with pleasure, <without a doubt, <wonderful>, <yah, <yay, <yea, <yeah, <yeah definitely, <yeah sure, <yeh, <yep, <yeppers, <yes, <yes please, <yes really, <yip, <you are right, <you bet>, <you could say that>, <you may, <you may be right, <you may have a point, <yup, <yuppers, I would say so, Y, d’accord, it_is_ok, its_ok, okay, okey, positive, right-o, touche, why_not, will_be_nice, ya, yes, yo, you_bet_you, ys

      For no:
      <I am afraid I disagree with you, <I am afraid I do not agree, <I am afraid not, <I am not sure I agree, <I am not sure that I, <I could not disagree more, <I disagree, <I do not>, <I do not agree, <I do not believe it>, <I do not believe so, <I do not believe you>, <I do not think so, <I do not want to>, <I dont think so, <I doubt it, <I just do not get it, <I refuse>, <I think not, <I will not>, <I would not>, <but no, <but of course not, <by no means, <come off it, <did not>, <disagree, <do not be absurd, <do not be ridiculous, <do not be silly, <do not be stupid, <does not seem likely>, <does not seem possible>, <doubtful, <false>, <fat chance, <fortune does not smile on that, <get out>, <get real, <hardly, <he does not>, <he is not>, <hell no, <horse hockey, <if you say so, <iie, <impossible, <improbable, <inconceivable>, <it does not>, <it is not>, <it is not possible, <it is unlikely>, <me thinks not, <most certainly not, <naaah, <naah, <nah, <naw, <nay, <neah, <negative, <neither, <neither of these, <never, <never>, <never mind>, <no, <no>, <no !, <no ,, <no -, <no ., <no I am fine, <no I am good, <no I am ok, <no can do, <no chance>, <no thank you, <no thanks, <no way, <no way>, <none, <none of them, <none of these, <noo, <nope, <not a chance, <not a prayer>, <not a snowball ‘s chance in hell, <not any of them, <not at all, <not at all>, <not at the moment, <not by a long shot, <not by any means, <not especially, <not exactly, <not in a million years, <not likely>, <not many>, <not much>, <not on your life, <not particularly, <not really, <not so much>, <not sure, <not that I know of, <not to my knowledge>, <not to speak of, <not very often>, <nuts to you, <of course not, <oh come on, <on the contrary>, <rubbish, <seldom, <she does not>, <she is not>, <strange, <surely not, <that is impossible, <that is rubbish, <that is unbelievable, <there is no reason to think so, <they are not>, <they do not>, <thinks not, <uh-hu, <uh-uh, <uhuh, <unbelievable, <unfortunately not, <unlikely, <unlikely>, <we do not>, <yeah yeah, <you are dead wrong, <you are having me on, <you are joking, <you are kidding, <you are not serious, <you are winding me up, <you can not be serious, <you have got that wrong, <you have got to be kidding, <you must be joking, <you must be kidding, N, do_not, instead, maybe_at_another_time, n, neither, no, not_OK, not_at_a_time, not_ever, not_now, nothing
      In both cases, “<” means the start of the sentence and “>” means the end of the sentence.  Many of these words are only treated as a yes or no if they appear at the start or the end of an utterance, not in the middle.
  3. You can use Rephrase Responses to rewrite VA replies using AI based on conversation context and user emotions. For Confirmation nodes, this feature helps rephrase the responses entered under User Prompts. To see this feature in your node’s Component Properties, enable the OpenAI or Azure-OpenAI integration and the Dynamic Prompt and Message Rephrasing feature under LLM and Generative AI.  By default, this feature is disabled for each node. Turn on the toggle to enable Rephrase Responses.Configure the number of previous user inputs to define  how many previous user messages should be sent to OpenAI as context based on which to rephrase the response sent through the node. You can choose between 0 and 5, where 0 means that no previous input is considered, while 5 means that the previous 5 responses are sent as context.
  4. Add context-specific Synonyms for Yes and No within the Confirmation node to suit the dialog’s context. The Platform can identify the emojis in user utterance and consider them for confirmation/rejection, for example, a thumbs-up emoji will be taken to mean confirmation from the user.

    Note: The Platform now supports additional Synonyms for Traditional Chinese language for Yes/No confirmation. Learn more.

  5. In the Variable Namespaces section, associate the variable namespaces to execute this node and its transitions. This option is visible only when the Variable Namespace is enabled for the assistant you are working with. You can go with the task level settings or customize it for this node. For more information, refer to the Managing Namespace article.

Additional Synonyms for Traditional Chinese Language

For the Traditional Chinese language, the Platform provides the following additional synonyms for “yes” and “no” responses on the Confirmation node:

Yes Confirmation

"係", "係呀", "講得啱", "啱", "冇問題"

No Confirmation

"唔係", "冇", "無", "唔得", "唔可以", "唔使", "唔要", "唔想", "唔啱"

These synonyms can be configured on the confirmation node under Component Properties > Synonyms during the Build stage of a Dialog Task.

After detecting these additional synonyms, the Confirmation node extracts “yes” or “no” from the user utterance.

Instance Properties

  1. On the Confirmation Component Properties window, click the Instance Properties tab.
  2. Under the Interruptions Behavior section, you can configure the interruptions behavior for this node.

    Note: The settings in the Instance Properties tab are specific to the current task and do not reflect in other dialog tasks that use this node
    1. Use the task level ‘Interruptions Behavior’ setting: The VA refers to the Interruptions Behavior settings set at the dialog task level.
    2. Customize for this node option: You can customize the Interruptions Behavior settings for this node by selecting this option and configuring it. For more information refer to the Interruption Handling and Context Switching article.
  3. Under the Precedence section, when the user’s input for an entity consists of a valid value for the entity and another intent, you can control the experience by choosing between Intent over Entity or Entity over Intent options. For example, if a Flight Booking assistant prompts for the destination and the user enters, Bangalore, how’s the weather there? you can define how the bot responds in such cases; pick the entity and add the intent to the follow-up intents stack or go ahead with the intent first based upon the Interruptions Behavior settings.
  4. Under the Custom Tags section, add tags to build custom profiles of your VA conversations. Learn more.

IVR Properties

Use  the IVR properties tab on the Confirmation Node to define the initial prompts, timeout prompts, no match prompts, and error prompts with customization for the retries behavior, input mode, grammar settings for Global and Node level use cases, prompts, and call behavior parameters for this node to use in IVR Channel. These settings are defined at the Confirmation Node level. For more information, read the Voice Call Properties article.

Note: The Confirmation Node supports all voice call properties for the  IVR, Audio Codes, Twilio Voice, and Voice Gateway channels. Except the IVR Data Extraction Key property is not supported.


Connections Properties

The Confirmation node’s conditional transitions go beyond the If-Else expressions used for the other nodes. You can define conditional expression based on a context object value, else a user assertion (yes), or else user negation (no). Beyond the three, you can define a fallback Else condition to trigger. 

Note: These conditions are applicable only for this instance and will not affect the node when being used in any other dialog.

For details on how to work with connection conditions,  read the Adding IF-Else Conditions to Node Connections article.

Menu