Digital Menu action
Use the Digital Menu action in digital bot flows to offer guidance and other options to your customer.
The label you enter here becomes the name of the action in the task editor.
Enter the wording that the bot uses to ask the customer a question for the first time. Use the Rich Text Builder to customize the question. You can format text, add links and images, incorporate expression text, and add variables.
Note: Given a no input from the user, the bot returns the Settings > User Input > No Input Detected > No Input Apology content, combined with the Question communication.
|Buttons||Create buttons for the user to indicate what they want to do next. For example, book a hotel room, contact the hotel event center, or listen to dining hours. To activate a button, enable the check mark next to it.|
Quick Replies: Select this option to create buttons for the user to indicate what they want to do next. For example, book a hotel room, contact the hotel event center, or listen to dining hours.
Carousel: Select this option to create cards with images, titles, or descriptions and provide an enhanced visual experience for your users.
In quick reply cards, you can use expressions to specify button types, values and labels. For example;
The carousel collection must have at least one item and up to three items per card, and 10 cards per carousel. Genesys recommends that you use images that are 800 x 400 pixels or similar for optimum visuals. When you add carousel cards, you can use expressions to add images, card titles, and card descriptions. For example;
The variable that stores the value that the customer selects. If the customer does not make a choice, then the value remains as No value specified.
Enter the communication that the bot produces when the user’s input is not a valid match.
Note: The bot returns the content from Settings > User Input > No Match Detected > No Match Apology, combined with the No Match communication.
|Customize No Match||
Enables the No Match Reprompts field. Use this option to create a list of no match prompts that incrementally occur when the bot receives No Match input events.
|No Match Reprompts||
When the bot receives a No Match input, the bot returns the communication 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 overrides the maximum number of No Match retries that you define at 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 Settings > User Input > No Match Detected > No Match Apology combined with the corresponding No Match Reprompt communication.
|Default No Match||
Enables the default No Match field. Use this option to define a single No Match prompt that the bot produces when it receives No Match input events.
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.