### Answer
Yes, there are ways to handle backtracking in Conversation Flow agents, though it requires specific configuration.
For Global Nodes:
You can enable the "Go back to previous node" functionality. [(1) ](
) When you set up a global node (which can be triggered from anywhere in your flow) , you need to configure a "Go Back Condition" that determines when the conversation should return to the original node. The key is properly defining this condition - for example, when a booking process is complete or a specific variable is set.
However, this feature doesn't work automatically - you need to configure the exit condition that triggers the return. Without a properly defined "Go Back Condition," the component won't know when to send the conversation back to the main flow.
Alternative Approach:
According to community feedback, Retell doesn't automatically return from global nodes, but you can build this functionality by storing the last node in a variable and routing back manually with a Logic Split. [(2) ](
)
Workaround for Complex Flows:
Some users have found that for scenarios requiring frequent backtracking between multiple nodes, using a single prompt agent with detailed instructions can be more reliable than conversation flow, especially when you need patterns like going from node 10 to node 3, or node 7 to node 2. [(3) ](
)
The limitation you're experiencing is real - edges in conversation flow are directional. [(4) ](
) You'll need to either use global nodes with proper go-back conditions, manual routing with variables, or consider if a single prompt agent might