The bot can retrieve follow-up information from the user. Here, enter the amount of time the bot waits for the user’s reply.

The default response timeout is six hours. The minimum and maximum allowed timeouts are one minute and three days. The system considers a NOT_SET, zero, or negative duration as errors.

Note: The follow-up response timeout applies to each customer response. Each time the customer responds and then receives another prompt from the bot, the timeout resets.

For example, if the bot asks, “What is your preferred date,” it waits up to 12 hours for a customer response. If the customer responds with a date within the 12-hour time frame and the bot replies, “Thank you, do you have an alternate choice,” then the flow restarts the timeout. The flow waits another 12 hours for the response about an alternate date.

Enter the timeout within which the bot must reply to the customer.

The default response timeout is 30 seconds. The minimum and maximum allowed timeouts are one second and one minute. The system considers a NOT_SET, zero, or negative duration as errors.

Enter the timeout after which the messaging session must close. Once a conversation starts, this duration indicates how long a conversation can remain open.

The default session timeout is 12 hours. The minimum and maximum allowed timeouts are one minute and three days. The system considers a NOT_SET, zero, or negative duration as errors.

The name of the bot integration you want to use in the flow.

For more information about configuring a Genesys Digital Connector integration, see Configure the Genesys Digital Connector integration.

The name of the bot to call within the message flow.

The information that you send to the bot. Enter the name of the variable and a value to assign. You can add multiple variables, and you can reorder them.

Most commonly, use session variables for bots that start the digital connector with the completed intent. This process ensures that the digital connector receives the necessary context for which to perform its operations.

The options that appear in this section reflect the logic configured in the bot. Each intent represents an action to perform. For example, book a hotel (BookHotel) or order flowers (OrderFlowers). Each intent path matches an output path for the Call Digital Connector action in the task editor.

Below each intent, Architect displays the configured bot slots or entities, or data the user must provide to fulfill the intent. Using the BookHotel intent as an example, the slots could include location, check-in date, room type, and number of nights. If the user chooses the BookHotel path, then the bot provides the slots associated with that path.

Select the variables to which you want to assign the failure data values that the bot returns.

Note: To expand or collapse the list of variables, click the arrow next to Failure Outputs.

Configure a matching output for the intent. This path indicates that the action successfully communicated with its external endpoint and received a result. 

Drag the appropriate action below the intent path that follows the route you want the interaction to take. 

This path indicates that an error occurred while running the action or there was a problem processing the results.  

Note: If the network experiences connectivity issues, the action automatically takes this failure path.

Drag the appropriate action below the Failure path that directs the route you want the interaction to take. For example, a transfer action to send the interaction to an agent for assistance.