Introduction

The “Start” component is the starting point of any flow in wolkvox Studio: it defines where the routing point execution begins and also enables initial configurations that depend on the type of flow (Voice/IVR, Chat, CRM/Webhook/Cron/Auto QAi/wvx Copilot, Interactions, and Agent Scripting).

By design, each routing point must have a single (mandatory) Start component, and no more than one can exist within the same flow.

Configuration

Initial configuration

1. In the routing point designer, locate the “Start” component in the top toolbar (it is the base component that represents the start of the flow).
2. Drag it onto the canvas if it does not already exist in the diagram.
3. To open the settings, double-click on the Start component (this opens the right configuration panel).

Recommendation: define “Start” as the first logical element of the flow and connect it immediately to the next component that will continue the path.

Configure “Start” in Voice (IVR)

In Voice-type flows, the Start component configuration panel includes the IVR recording section:

• Enable IVR call recording: by enabling this checkbox, all calls that enter and transit through that flow will be recorded (according to your operation's configuration). This option may indicate an extra cost.

Steps

• Open the “Start” component configuration.
• Check “Enable IVR call recording” if your operation requires recording from the start.
• Click “Save”.
• Compile the flow to apply changes.

Configure “Start” in Chat

In Chat-type flows, Start concentrates two important capabilities: transcription of incoming audios and inactivity messages.

Activate ASR for customer audios (audio → text)

Activate ASR: Customer Audio to $txt_query (Has extra cost): converts the audios sent by the customer into text and saves the result in $txt_query.

Language selector:

• You can choose a specific language (for example, es-CO).
• There is also an xx option for automatic language detection (multiple languages).

Steps:

• Check the box Activate ASR: Customer Audio to $txt_query.
• Select the language in the dropdown (for example, es-CO) or “xx” if you need auto-detection.
• Save the configuration and compile.

Activate inactivity message sending

Activate message sending for inactivity: sends reminders when the customer stops responding.

Fields:

• Timeout (minutes): minutes since the customer's last activity to trigger the message. Maximum: 120.
• Repetitions: how many times the reminder will be resent if inactivity continues. Maximum: 3.
• Inactivity message: type the message and then press the “+” icon to add it to the list.
• Message: list of added messages (you can select one and delete it with the “-” icon).
• Execute in order of creation: if activated, messages will be sent in the order they were created; if not, they will be sent in random order.

Steps:

• Check Activate message sending for inactivity.
• Configure Timeout and Repetitions.
• Type the text in Inactivity message and press “+” to add it.
• (Optional) Add several messages.
• (Optional) Activate Execute in order of creation.
• Click “Save” configuration and compile.

Configure “Start” in CRM + Webhook + Cron + Auto QAi + wvx Copilot

In these routing points, the Start component configuration focuses on execution scheduling:

• Cron: allows defining the process execution interval.
  • Typical options: from 1 minute to 1440 minutes, and the “no” option.

Steps:

• Open Start and locate the “Cron” field.
• Select the interval (or no if you do not want scheduled execution).
• Click “Save”.
• Compile the flow.

Start in Interactions

In Interactions-type routing points, the “Start” component does not have a configuration panel. Even so:

• It remains mandatory and unique.
• It marks the beginning of the flow for the interaction path.

Configure “Start” in Agent Scripting

In Agent Scripting, “Start” is also mandatory and unique, but its configuration impacts the behavior of the agent interface in wolkvox Agent:

• Disable AgentBox disposition: by enabling this checkbox, the “Disposition” tab is hidden in the agent application, preventing them from classifying calls from that section (that is, it restricts the possibility of assigning a call code/result from that view).

Steps:

• In Agent Scripting, double-click on the “Start” component.
• Check “Disable AgentBox disposition” if your operation requires that classification is not done from that tab.
• Click “Save”.
• Compile the script.