Ask for Yes/No action

Use this action for questions that require a “yes” or “no” answer from the customer. For example, the bot might ask, “Do you want to book an appointment?” This action provides the user the opportunity to answer accordingly; either yes or no. Use this action at any point in your flow. Alternatively, you can add it as a child of an associated parent Ask for Intent action.

Access the Ask for Yes/No action from the bot flow’s Ask menu in the Architect toolbox.

Name	Description
Name field	Type a distinctive name for the action. The label you enter here becomes the action’s name displayed in the flow structure.
Question	Here, ask the recipients what they would like to do. For example, “Do you want to proceed?” In call flows, the question you enter hear plays verbally to the caller. In chat and message flows, this question appears in a text.
Invalid Response: No Input	Enter the communication that the bot produces when it does not receive user input. For example, “Say yes if you want to proceed, or say no if you do not want to proceed.” Note: No Input reprompts are not enabled for Digital Bot Flows. The bot returns the configuration you define in Settings > User Input > No Input Detected > No Input Apology combined with the Question communication.
Default No Input	Enables the No Input field and allows you to define a single No Input prompt that the bot returns after it receives no input.
No Match	The communication that the bot returns when the user’s input is not a valid match. For example, “Please say yes or no. Do you want to proceed?” Note: The bot returns the configuration you set in Settings > User Input > No Match Detected > No Match Apology combined with the No Match communication.
Customize No Match	Enables the No Match Reprompts field and allows you to create a list of no match prompts. The bot returns these prompts incrementally after it receives No Match input events.
No Match Reprompts	When the bot receives a No Match input, it returns the communication at the position in the No Match Reprompts collection that corresponds to the current number of No Match inputs received for that action. For example, the first No Match input triggers the bot to use the first No Match reprompt in the defined collection. The length of the No Match Reprompt collection also overrides the maximum number of No Match retries that you define in Settings > User Input > No Match Detected > Maximum Number of No Match Retries for that particular action. For example, if you define two reprompts in the collection, the bot retries twice. An empty collection turns off No Match retries. Note: The bot returns the configuration you set in Settings > User Input > No Match Detected > No Match Apology combined with the No Match communication.
Default No Match	Enables the default No Match field and allows you to define a single No Match prompt that the bot returns after it receives No Match input events.
Paths	Max No Inputs: Enable or disable the Max No Inputs path. When you enable this option, if the bot exceeds the maximum number of no input retries that you set for this action, then the flow follows this output path. Note: If you disable this path, then the flows that you configure for the output path are hidden, not deleted.