확인 노드를 사용하면 사용자에게 예 또는 아니요로 답변하도록 요청할 수 있습니다. 이는 확인에 도움이 되며 사용자는 선택을 수락하거나 거부할 수 있습니다. 예: 항공편 예약 봇에서 확인 노드를 사용하여 목적지의 일기 예보를 알고 싶은 경우 응답하라는 메시지를 표시할 수 있습니다. 확인 노드의 조건부 전환은 If-Else IF-Else 표현식보다 우수합니다. 전환은 사용자 응답에 따라 다릅니다. 긍정(예) 또는 부정(아니요). Else 조건은 두 가지 답변 모두에 해당되지 않는 경우 적용됩니다.

설정

대화 작업에서 확인 노드를 설정하려면 다음 단계를 수행합니다.

노드 추가

1. 확인 노드를 추가하려는 대화 작업을 엽니다.
2. 지정된 위치에 확인 노드를 추가합니다. 노드를 추가하는 단계의 경우, 여기를 참조하세요.
3. 확인 창은 기본적으로 구성 요소 속성 탭이 선택되어 표시됩니다.

노드 설정

구성 요소 속성

구성 요소 속성을 설정하려면 다음 단계를 수행하세요.

1. 구성 요소 속성 탭의 일반 설정 섹션에서 이름 및 표시 이름을 입력합니다.
2. 사용자 프롬프트 섹션에서 일반 텍스트 또는 JavaScript 메시지 형태로 확인 요청을 작성합니다.
3. 메시지 링크를 사용하여 사용자 프롬프트에 대한 채널별 메시지를 입력할 수 있습니다. 자세한 내용은 프롬프트 편집기 사용을 참조하세요.
4. 봇 응답을 추가하려면 프롬프트 추가를 클릭하고 위의 단계를 반복하세요.
5. 채널별 표준 형식을 표시 확인 옵션으로 활성화합니다. 이 옵션을 사용하지 않으면 최종 사용자에게 예/아니요 옵션이 표시되지 않습니다.
6. 플랫폼은 아래 키워드를 기반으로 예/아니요를 감지합니다. 플랫폼은 내부 동의어를 포함한 예/아니요 동의어가 동시에 처리되며 가장 먼저 선택한 것을 택합니다. 즉 물론 아닙니다와 같은 동의어는 아니요로 간주됩니다. 이전에는 물론입니다가 “예”의 동의어 일부였기 때문에 “예”로 매핑되었습니다. 또한, 예/아니요 동의어는 개념이자 패턴입니다.예인 경우: '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 아니요인 경우: <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 두 경우 모두 <문장의 시작을 의미하며 그리고> 문장의 끝을 의미합니다. 따라서 이 단어 중 상당수는 발화의 중간이 아니라 시작 부분에 나오는 경우에만 예 또는 아니요로 취급됩니다. 대화의 컨텍스트에 맞도록 확인 노드 내에 예 및 아니요에 따른 컨텍스트별 동의어를 추가할 수 있습니다. 플랫폼에서는 사용자 발화에서 이모지를 식별할 수 있으며 확인/거부에 따른 사용을 고려할 수 있습니다. 예: 엄지손가락을 치켜세우는 이모지 사용은 사용자의 확인을 의미합니다.
   
   이 이미지는 새 대화 빌더에 해당하며, 이 기능은 확인 노드 -> 구성 요소 속성 위치에 있는 이전 빌더에서 찾을 수 있습니다.
7. 변수 네임스페이스 섹션에서 이 노드와 전환을 실행할 변수 네임스페이스를 연결합니다. 이 옵션은 봇에 변수 네임스페이스를 사용하도록 설정한 경우에만 표시됩니다. 작업 수준 설정을 사용하거나 이 노드에 사용자 정의할 수 있습니다. 자세한 내용은 네임스페이스 관리를 참조하세요.

인스턴스 속성

1. 확인 창에서 인스턴스 속성 탭을 클릭합니다.
2. 중단 동작 섹션에서 이 노드에 대한 중단 동작을 설정할 수 있습니다. 참고: 인스턴스 속성 탭의 설정은 현재 작업에만 해당되며 이 엔티티 노드를 사용하는 다른 대화 작업에는 반영되지 않습니다.
   • 작업 수준 ‘중단 동작’ 설정 사용: 봇은 대화 작업 수준에서 설정된 중단 동작 설정을 참조합니다.
   • 이 노드 옵션을 위한 사용자 정의: 이 옵션을 선택하고 동일하게 설정하여 이 노드에 대한 중단 동작을 사용자 정의할 수 있습니다. 자세한 내용은 중단 처리 및 컨텍스트 전환 문서를 참조하세요.
3. 우선 순위 섹션에서 엔티티에 대한 사용자 입력이 엔티티 및 다른 의도에 대한 유효한 값으로 구성될 때 엔티티보다 의도 중에서 또는 의도보다 엔티티 옵션 중에서 선택하여 경험을 통제할 수 있습니다. 예를 들어, 항공편 예약 봇이 목적지를 묻는 메시지를 표시하고 사용자가 Bangalore의 날씨는 어떻습니까?라고 입력하는 경우에 봇이 대응하는 방법을 정의할 수 있습니다. 엔티티를 선택하고 후속 조치 의도 스택에 의도를 추가하거나 중단 동작 설정에 따라 의도를 먼저 진행합니다.
4. 맞춤형 태그 섹션에서 태그를 추가하여 봇 대화의 맞춤형 프로필을 작성하세요. 자세히 확인하려면 여기를 클릭하세요.

IVR 속성

이 탭을 사용하여 입력 모드, 문법, 프롬프트 및 IVR 채널에서 이 노드가 사용할 호출 동작 매개 변수를 정의할 수 있습니다. 노드 수준에서 수행됩니다. 자세한 내용을 확인하려면 여기를 클릭하세요.

연결(또는 전환) 속성

확인 노드의 조건부 전환은 다른 노드에 사용되는 If-Else IF-Else 표현식보다 우수합니다. 컨텍스트 개체 값에 따라 조건식, else 사용자 긍정(예) 또는 else 사용자 부정(아니요)을 정의할 수 있습니다. 이 세가지 외에도 트리거할 폴백 Else 조건을 정의할 수 있습니다. 구성 요소 전환을 설정하려면 다음 단계를 수행하세요.

1. 확인 창에서 연결 탭을 클릭합니다.
2. 연결 탭의 연결 규칙 섹션에서 기본적으로 컨텍스트가 선택됩니다.
3. If에는 다음을 입력할 수 있습니다.
   • If 조건: 비교할 컨텍스트 개체를 입력합니다.
   • 연산자: 드롭다운 목록에서 다음 연산자 중 하나를 선택합니다. Exists, equals to, greater than equals to, less than equals to, not equal to, greater than, less than.
   • 값: 컨텍스트 개체를 비교할 값을 입력합니다. 예: Context.entity.PassengerCount (컨텍스트 개체) greater than (연산자) 5 (지정된 값).
   • Then go to 드롭다운 목록에서 조건식이 성공할 경우 실행할 노드를 선택합니다.
4. Else IF 사용자 응답은 긍정(예시: 예) 섹션의 Then go to 드롭 다운 목록에서 사용자 응답이 긍정인 경우 다음으로 실행할 노드를 선택합니다.
5. Else IF 사용자 응답은 부정(예시: 아니요) 섹션의 Then go to 드롭다운 목록에서 사용자 응답이 긍정인 경우 다음으로 실행할 노드를 선택합니다.

確認ノードでは、ユーザーに はいまたはいいえの回答を指示することができます。これは、ユーザーが選択肢を受け入れるか拒否するかについて、検証または許可するのに役立ちます。

たとえば、フライト予約ボットでは、確認ノードを使って、目的地の天気予報を知りたいかどうか、ユーザーに回答を指示することができます。確認ノードの条件付き遷移は、If-Else If-Elseの表現を超えています。

遷移はユーザーの返答に依存します：アサーション（はい）または否定（いいえ）。Else条件は、答えが両方でない場合に機能します。

セットアップ

ダイアログタスクにおけるダイアログノードのセットアップは、以下の手順で行います。

ノードの追加

1. ダイアログタスクを開き、確認ノードを追加します。
2. 確認ノードを指定された場所に追加します。ノードの追加手順についてはこちらをご参照ください。
3. 「確認」ウィンドウは、デフォルトではコンポーネントプロパティタブが選択された状態で表示されます。

ノードの設定

コンポーネントプロパティ

コンポーネントのプロパティを設定するには、以下の手順に従います。

1. コンポーネントプロパティタブの一般設定セクションで、名前と表示名を入力します。
2. ユーザープロンプトセクションでは、確認リクエストをプレーンテキストまたはJavaScriptメッセージとして作成できます。
3. 管理リンクを使用して、ユーザープロンプトのチャネル固有のメッセージを入力できます。詳細は、プロンプトエディターの使用をご参照ください。
4. さらにボットの応答を追加するには、プロンプトの追加をクリックし、上記の手順を繰り返します。
5. チャネル固有の標準フォーマット化を有効にして、確認オプションの表示 を行います。これを有効にしないと、「はい/いいえ」のオプションはエンドユーザーに表示されません。
6. 「はい/いいえ」のプラットフォーム検出は、以下のキーワードに基づいて行われます。このプラットフォームでは、内部的なものも含めて、「はい/いいえ」の同義語が同時に処理され、最速で選択できるようになっています。これは以下のような意味です。もちろん違うのようなものは「いいえ」と見なされますが、以前は「はい」にマッピングされていました。これは、もちろんが「はい」の同義語の一部だからです。また、「はい/いいえ」の同義語は、概念やパターンでもあります。「はい」の場合： '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 「いいえ」の場合： <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 いずれの場合も、<は文頭を意味し、>は文末を意味します。そのため、これらの単語の多くは、途中ではなく、発話の最初に現れた場合にのみ、 はいかいいえ として扱われます。また、ダイアログのコンテキストに合わせて、確認ノード内にはいといいえのコンテキスト固有の同義語を追加することもできます。プラットフォームは、ユーザーの発話に含まれる絵文字を識別し、確認/拒否のために考慮することができます。たとえば、サムズアップの絵文字は、ユーザーからの確認を意味するものと見なされます。 この画像は新しいダイアログビルダーに対応していますが、従来のビルダーでも同じ位置（つまり、確認ノード->コンポーネントのプロパティ）でこの機能を見つけることができます。
7. 可変ネームスペースセクションでは、可変ネームスペースを関連付けてこのノードとその遷移を実行します。このオプションは、可変ネームスペースがボットに対して有効になっている場合にのみ表示されます。タスクレベルの設定を使用するか、またはこのノード用にカスタマイズできます。詳細情報は、ネームスペースの管理をご参照ください。

インスタンスプロパティ

1. 「確認」ウィンドウで、インスタンスプロパティタブをクリックします。
2. 割り込み動作セクションでは、このノードの割り込み動作を設定できます。メモ：インスタンスプロパティタブの設定は、現在のダイアログタスクに固有のものであって、このノードを使用して他のダイアログタスクに反映させることはできません。
   • タスクレベルの「割り込み動作」設定を使用します：ボットは、ダイアログタスクレベルで設定された割り込み動作の設定を参照します。
   • このノードオプションのカスタマイズ：このオプションを選択してその設定を行うことで、このノードの割り込み動作の設定をカスタマイズできます。詳細情報は、割り込み処理とコンテキストの切り替えの記事をご参照ください。
3. 優先順位のセクションでは、エンティティに関するユーザー入力がエンティティの有効な値と別のインテントで構成されている場合、エンティティよりもインテントまたはインテントよりもエンティティのオプションを選択することにより、エクスペリエンスを制御することができます。例として、フライト予約ボットが目的地の入力を指示し、ユーザーが バンガロール、そちらの天気はどうですか？と入力した場合、ボットがこのような場合にどのように応答するかを定義することができます；エンティティを選択してインテントをフォローアップインテントスタックに追加するか、割り込み動作設定に基づいて最初にインテントを実行します。
4. カスタムタグセクションにおいて、タグを追加して、ボット会話のカスタムプロファイルを作成します。詳しくはこちらをクリックしてください。

IVRプロパティ

このタブを使用して、このノードがIVRチャネルで使用する入力モード、文法、プロンプト、および呼び出し動作パラメータを定義できます。それはノードレベルで行われます。詳細はこちらをクリックしてください。

接続（または遷移）のプロパティ

確認ノードの条件付き遷移は、他のノードで使用されているIf-Else If-Elseの表現を超えています。コンテキストオブジェクトの値に基づいて条件式を定義したり、他にユーザーの主張（はい）や他にユーザーの否定（いいえ）を定義したりすることができます。この3つ以外にも、フォールバックのその他 条件を定義してトリガーすることができます。コンポーネント遷移のセットアップは、以下の手順に従います。

1. 「確認」ウィンドウで、接続タブをクリックします。
2. 接続タブの接続ルールセクションでは、デフォルトでコンテキスト 」が選択されています。
3. Iｆ条件では、以下のように入力します。
   • If条件：比較用のコンテキストオブジェクトを入力します。
   • 演算子：ドロップダウンリストで、これらのいずれかの演算子を選択します。存在する、等しい、等しいより大きい、等しいより小さい、等しくない、より大きい、より小さい。
   • 値：コンテキストオブジェクトの比較となる値を入力します。例： Context.entity.PassengerCount （コンテキストオブジェクト）が（演算子）5（指定値）より大きい。
   • その他のドロップダウンリストで、条件が成功した場合、これを実行するノードを選択します。
4. Else IFユーザー応答が肯定的（たとえば「はい」）セクションでは、次に進むドロップダウンリストで、ユーザーの反応が肯定的な場合に次に実行するノードを選択します。
5. Else IFユーザー応答が否定的(たとえば「いいえ」)セクションでは、 次に進むドロップダウンリストで、ユーザーの反応が肯定的な場合に次に実行するノードを選択します。

Confirmation Node allows you to prompt the user for a yes or no answer. It helps in the verification or allowing users to accept or decline a choice.

For example, in the Books Flight Bot, you can use a confirmation node to prompt the user to respond if they would like to know the weather forecast of the destination.

The confirmation node’s conditional transitions go beyond the If-Else 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.

Set-Up

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

Add Node

1. Open the dialog task to add the Confirmation node.
2. Add Confirmation node in the designated place. For steps in adding nodes, refer here.
3. The Confirmation window is displayed with the Component Properties tab selected by default.

Configure 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.
3. You can enter channel-specific messages for User Prompts using the Manage link. For more information, refer to Using the Prompt Editor.
4. To add more bot responses, click Add a Prompt and repeat the above steps.
5. 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.
6. 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 is taken. This means that something like of course not is considered as NO, earlier it was mapping to YES because of of course being 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. So, many of these words are only treated as a yes or no if they appear at the start of an utterance, not in the middle.
   You can also 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.
   
   This image corresponds to the new dialog builder, you will find this feature in legacy builder at the same location i.e. Confirmation node -> Component Properties.
7. 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 bot. You can go with the task level settings or customize it for this node. For more information, refer to Managing Namespace.

Instance Properties

1. On the Confirmation 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.
   • Use the task level ‘Interruptions Behavior’ setting: The bot refers to the Interruptions Behavior settings set at the dialog task level.
   • Customize for this node option: You can customize the Interruptions Behavior settings for this node by selecting this option and configuring the same. Refer to Interruption Handling and Context Switching article for more information.
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 bot 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 bot conversations. Click here for more.

IVR Properties

You can use this tab to define the input mode, grammar, prompts, and call behavior parameters for this node to use in IVR Channel. It is done at the node level. Click here for details.

Connections (or Transitions) Properties

Confirmation node’s conditional transitions go beyond the If-Else 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.

To setup component transitions, follow the below steps:

1. On the Confirmation window, click the Connections tab.
2. On the Connections tab, under the Connection Rules section, Context is selected by default.
3. Under If, you can enter the following:
   • If condition: Enter a context object to compare.
   • Operator: In the drop-down list, select one of these operators: Exists, equals to, greater than equals to, less than equals to, not equal to, greater than, and less than.
   • Value: Enter the value with which to compare the context object. For example,  Context.entity.PassengerCount (Context object) greater than (operator) 5 (specified value).
   • In the Then go to drop-down list, select the node to execute if this condition succeeds.
4. Under Else IF user response is affirmative (For example, Yes) section, in the Then go to drop-down list and select the node to execute next if the user’s response is affirmative.
5. Under Else IF user response is negative (For example, No) section, in the Then go to drop-down list and select the node to execute next if the user’s response is affirmative.