Digital Menu action

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.

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; MakeChoice("type", "value", "label"). Also, you can choose to create only a single card with three buttons.

1. Click Button.
2. Under value, enter the postback or URL value that Architect sends to the bot when the customer clicks it. If you do not add the optional label, then Architect uses the value you enter here as the button label. However, if you have more than one card but the button labels are the same; for example, “view,” then the value you enter here distinguishes for the bot which button that the customer selects.
3. To add a button label that differs from the value that you enter in Step 2, click Add alternative label and enter the button’s display label. 
4. Repeat steps 1-3 for each additional button that you want to add.
5. Add the appropriate action below each button’s path to continue the digital bot flow.

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; MakeImageFromUrl("your_URL").

1. Click Card. The Card dialog box opens.
2. Click Select an Image and choose an existing image or import a new one. Alternatively, you can add an image with the Image Builder. For more information, see Add images with the Image Builder.
3. Add a required title that appears below the image.
4. (Optional) Add a description to appear below the title.
5. Click Button Name.
6. Under Button Action, select Postback or Open URL.
7. Under value, enter the postback or URL value that Architect sends to the bot when the customer clicks it. If you do not add the optional label, then Architect uses the value you enter here as the button label. However, if you have more than one card but the button labels are the same; for example, “view,” then the value you enter here distinguishes for the bot which button that the customer selects.
8. To add a button label that differs from the value that you enter in Step 2, click Add alternative label and enter the button’s display label. 
9. Repeat steps 1-8 for each additional button that you want to add.
10. Add the appropriate action below each card’s path to continue the digital bot flow.

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.

The variable that stores the collection of KnowledgeBaseDocument matching results from the search that Architect performs in the action. If you select standard knowledge handling, then search results collection only contains the article that appears to the user. If you choose custom knowledge handling, then the results collection can contain multiple articles that strongly match the search.

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.

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.

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.

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.
• Max No Matches: Enable or disable the Max No Matches path. When you enable this option, if the bot exceeds the maximum number of no match 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.