Introduction

When designing complex customer service strategies in wolkvox Studio, it is common for flowcharts to grow considerably, filling the workspace canvas with multiple components and connection lines. This can make it difficult to read, organize, and visually manage the path.

To solve this, wolkvox offers the 'Connector Out' and 'Connector In' components. These function as "wireless bridges" or portals that allow you to visually cut a flow line at one point and resume it elsewhere on the canvas (or simply to separate logic into blocks), maintaining operational continuity without the need to draw endless arrows.

Important Note: These components are found in the "Design" category and are available for Voice (IVR), Chatbot, Interaction Routing, and CRM + Webhook Routing Points. They are not available for the Agent Scripting module.

Configuration

Below, we explain step-by-step how to use these components to clean up and organize your workspace:

Step 1: Ending a flow path with 'Connector Out'

1. The “Connector Out” component acts as the exit point or "transmitter." Use it when you want to end a section of the diagram and jump to another area of the canvas.
   • Double-click on the component to open its configuration panel.
2. In the "Connector out name" field, type a short label that identifies this link (for example: SalesMenu).
   • Requirement: The name must not exceed 10 characters.

Step 2: Resuming the flow with 'Connector In'

1. The “Connector In” component acts as the arrival point or "receiver." Use it to start the next visually separated section of the diagram.
   • Double-click on the component to open its configuration panel.
2. In the "Connector in name" field, type exactly the same name you used in the “Connector Out” from the previous step (for example: SalesMenu).
   • Important: The link is made exclusively through this text. If the names do not match exactly, the flow will break and will not continue.
   • From the “Connector In,” draw an arrow to the next operational component of your flow.
   • The system will internally understand that when the customer reaches the Connector Out, they must immediately jump to the corresponding Connector In.

Visual example of component usage