Jump Start Component
The Jump Start component allows redirecting the conversation to:
Another point within the same flow, or
Another previously published flow.
It is a key component for building more organized, reusable, and easy-to-maintain flows, especially in scenarios with menus, forms, or repeated decisions.
🎯 What is it for?
Avoid repeating logic blocks or messages.
Relocate the user according to their choice or a condition.
Keep the conversation flowing without restarting it.
Reuse entire sections of the flow (payments, errors, menus, etc.).
✅ Typical use case
If a user starts the flow through option A, but their interaction corresponds to sending them to option B, the Jump Start component allows redirecting them without cutting off the conversation or losing context.
Example:
The user selects an option related to billing → they are redirected directly to the Payment flow or block.
The user selects an option related to billing
→ they are redirected directly to the Payment flow or block.
⚙️ Jump Start component configuration
When selecting a Jump Start component, you will find the following options:
🧩 Add jump destination
Allows defining to which group of components or flow block the conversation will be redirected.
You can: Select a specific component of the same flow. Redirect to an isolated flow unit, ideal for reusing sections.
Select a specific component of the same flow.
Redirect to an isolated flow unit, ideal for reusing sections.
📌Good practice: the jump destination must be consistent with the point in the flow where it is executed (menu, error, validation, etc.).
🔽 Select component
From this dropdown, the exact component to which the flow will jump is defined.
This step is critical because:
An incorrect destination can lead the user to messages that do not correspond.
It is one of the main causes of logical errors in production.
💡Key tip:
Giving clear names to the components (for example: Main menu, Validation error, Payment rejected) makes it much easier to correctly configure the jump starts and avoids errors.
🔁 Jump to another published flow
This option allows redirecting the conversation to another flow that is already published.
It is useful when:
You work with modular flows (Sales, Support, Payments).
You want to reuse an entire flow without duplicating it.
You are looking for a more organized and scalable architecture.
📌 Only published flows can be selected.
⚙️ Advanced configuration: repetition control and End of flow
The Jump Start component has a behavior designed to avoid infinite loops, so it is essential to configure its advanced use correctly.
🛑 Activate End of flow
This option defines what the flow will do when the maximum number of jumps allowed is reached.
This way:
We avoid infinite loops.
We ensure good user management.
The flow always has a clear output (end, assignment, redirection, etc.).
🔢 Maximum number of jumps
This field defines how many times the user can go through that Jump Start before executing the configured action (for example, End of flow).
📌 Orientative recommendations:
Flows with menu: higher values (20 / 50 / 100).
Forms or validations: lower values.
It is always recommended to use this value together with End of flow activated.
🧠 When is it convenient to increase the jump limit?
Flows with menu navigation where the user can go back several times.
Educational bots or surveys.
Assistants that allow reviewing previous decisions without closing the conversation.
✅ Checklist before publishing
🔁 Does each jump point to the correct block?
🗂️ Do the destinations make logical sense within the flow?
🧪 Did you test all possible paths in the simulator?
🏷️ Are the components well named?