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:

Open the dialog task to which you want to add the Confirmation node.
Add a Confirmation node in the designated place. For steps related to adding nodes, Learn more.

Note

You can add a confirmation node within an existing sequence or outside any existing sequence. If you add it outside, a new, untitled sequence will automatically get created containing the new confirmation node.
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.

To configure the component properties, follow the below steps:

On the Component Properties tab, enter a Name and a Display Name.
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, , , , , , , , , , , , , , <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>, , <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:
 , , , , , , , <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.
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. Adjusting the settings allows you to fine-tune the model’s behavior to meet your needs. The default settings work fine for most cases. However, if required, you can tweak the settings and find the right balance for your use case.
- Model: The default model for which the settings are displayed. You can choose another supported mode if it’s configured. If you select a non-default model, it’s used for this node only. If you want to change the default model, you can select the model in the drop-down list and use the Mark Default option shown next to its name.
- No of previous user inputs: 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.
- Additional Instruction: Add a brief description of the use case context to guide the model.
- Temperature: The setting controls the randomness of the model’s output. A higher temperature, like 0.8 or above, can result in unexpected, creative, and less relevant responses. On the other hand, a lower temperature, like 0.5 or below, makes the output more focused and relevant.
- Max Tokens: It indicates the total number of tokens used in the API call to the model. It affects the cost and the time taken to receive a response. A token can be as short as one character or as long as one word, depending on the text.
- Fallback Behaviour: If the rephrase response fails, use the original user query.
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.
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.

Note

This section will be visible only if you enable Variable Namespace in App Profile.

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 while building the Dialog Task.

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

Instance Properties¶

On the Confirmation Component Properties window, click the Instance Properties tab.
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.
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.
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¶

Note

If the node is at the bottom in the sequence, then only the connection property is visible.

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.