Control Flow
Node | Control Flow |
---|---|
Description | These nodes within the Conversation Studio provide user the ability to control the flow of a conversation from start to end. Using the control flow nodes, users can create custom flows for different system events, defining the conversation’s flow by simply connecting a combination of available nodes. |
Following are some example system behaviors, that can be easily defined using the Control Flow nodes.
Adding a bot when a conversation starts
Removing an agent when their SLA expires
Sending a text message when a conversation is pause

Nodes
The list of nodes for control flow are given as follows:
Node | Description |
---|---|
Reminder | The Conversation Controller Reminder nodes can be used to schedule and unschedule reminders and define flows to be executed when a certain reminder triggers. |
Text Message | The Text Message node can be used to send messages to the customer |
Condition | The Condition Node serves as a checkpoint in our workflow. It comprises a bunch of nodes that check specific conditions against the input payload and route the message to one of two paths. Most condition nodes accept one input and have two outputs for true/false conditions. |
Init | The Init Node serves as the entry point for the Conversation Studio. It acts as a bridge between the Conversation Manager and the Conversation Studio. This node processes incoming messages based on the defined intents and performs a switch operation to send the message to the corresponding output node. |
Action | Actions nodes are individual nodes created for specific tasks, like assigning a bot or ending a conversation. Each node focuses on one action, simplifying workflows. |