Configure jump nodes

Jump nodes redirect the conversation to an existing branch or step, skipping everything else. Jumps are instant, with no pauses or expectations of user feedback. Once the preceding node runs, the customer is immediately redirected the target node. You can only jump to a branch or a step, and you can’t jump to another jump node.
Configure jump nodes
Tips
- Jumps are best for loops or rerouting. For simple conditions and decisions, consider using a branch node instead.
- Make sure there are no self-referencing jump loops the customer will be stuck in.
- To avoid duplicating nodes, create a single step node and then jump to it whenever you need it. For example, you can create a step node for error handling or a common subflow.