Introduction

When a routing point grows and many branches and components appear, it becomes difficult to read and maintain. The “Container” component allows you to “encapsulate” parts of the flow into an internal section, as if it were a sub-flow, keeping the design clean and organized without losing functionality.

The container is available in Voice, Interaction, and Chat routing points, as well as in Agent Scripting, within the Design components group.

Configuration

• Place it at the point in the flow where you want the internal section to start.
• From the main flow, connect the previous component to the Container as you would with any other component.
• Double-click on the “Container” component.
• Important: the actual user flow remains that of the main routing. The container only “hides” a part of the flow to maintain order.

1. Inside the container:
   • You will see a new “empty” workspace: this is the container's internal flow.
   • Design the internal flow as you would in any routing: add components, create paths, conditions, send messages, etc.
   • Add a “Start” component (green circle).
   • Ensure that all paths end in an “End” component.
   • A button with a left arrow will appear in the top bar, indicating that you are inside a container and that you can use that button to return to the main flow.
   • It is not possible to add a container inside another container.
     • For this reason, while inside the container, you will no longer see the “Container” component in the component list.
2. When you finish designing, compile the flow.
3. Click the left arrow button at the top of the canvas to return to the main flow.

1. From a flow perspective, when the user reaches the Container, the execution “enters” the internal flow, follows its logic, and then ends at an “End”.
2. Upon returning to the main flow, compile the complete routing.