Work with Genesys Dialog Engine Bot Flows

Administrators and contact center managers can create bot flows in Architect through a natural language understanding (NLU) engine that can understand and process information the customer provides as input. Drag and drop actions to build your bot along with NLU.

Note: This feature is not PCI DSS-compliant. Best practice recommends that you do not use them in Architect secure call flows. For more information, see PCI DSS compliance.

To help familiarize yourself with bot flows in Architect, review the following pages:

Page Description
About Genesys Dialog Engine Bot Flows

Find articles that describe and demonstrate how to use Architect to build a bot and then use it in a call or chat flow.

About Architect

Discover Architect features and learn how to use Architect to build flows.

About bots

Learn how to create bot integrations for use in Architect interaction flows.

Create a bot flow

Learn how to create a bot flow.

Manage data resources in the flow In addition to editing variables and viewing usage, you can add and filter variables for flows.
Expression help feature Learn how to access the built-in expression resource to assist when creating bot flow task expressions.
Work with expressions Use expressions to create sophisticated and complex flow calculations by selecting variables and operators.
Architect built-in variables See the list of Architect read-only, built-in variables for bot flows.
Manage a variable Edit a variable’s values.

This table describes the available Architect actions that you can implement into your bot flows. After you build the bot flow, use the Call Bot Flow action to call it from voice, chat, and message flows.

Icon Category Action Description

Ask for Intent

Call an intent that describes a goal or task that a user wants to do, such as tracking their package or booking a cab.

Ask for Yes/No

Select follow-up intents that guide the user through a conversation.

Ask for Slot

Identify slots that a caller or chat recipient mentions in an utterance.


Interact with a customer through one-way communication. 
Data Call Data Retrieve information about a customer from default or custom data actions integration in Genesys Cloud.
Data Table Lookup Retrieve data stored in a Genesys Cloud data table.
Update Data Assign values to flow or task level variables.
Disconnect Disconnect

An alternative way to end the bot flow.

Exit bot flow

An alternative way to end the bot flow.

External Contacts Get External Contact Retrieve information about an existing external contact.
Get External Organization Use the Get External Organization action to find a specific organization, or with the Get External Contact action to find a specific person.
Search External Contacts Find one or more external contacts based on your search terms.
Flow Clear Slot Select the slot to clear.
Set Intent Set an intent as the active intent.
Logical Decision Direct the process branch, depending on whether a condition is true.
Switch Configure a switch action to specify what Architect does, when to do it, and under which circumstances. This action is similar to a Decision action, and is easy to set when to evaluate multiple cases. 
Loop Loop Direct your process repeat a series of actions before it goes on to the next action in your design.
Loop Until  Make your process repeat a series of actions and include exit criteria for the action after it meets specific criteria.
Anything Else? Loop Make your process repeat a series of actions and then ask recipients what they would like to do next.
Next Loop Use the Next Loop action when, during the loop iteration, the flow encounters a false outcome and you want it to continue to the next iteration.
Exit Loop Use this action inside a Loop action. Use it to end and exit the current loop, and to continue flow execution by moving to the following action.
Task Task Use this action to build complex flow options; for example, to group related steps of a process together and create a flow routine.
Call Task Call another task. When the called task completes, the configured output path determines how flow execution continues.