Hello! I've having a few issues with my conversational flow agents and their node transitions. Even though the node transition instructions are clearly defined, the agents are seeming to have trouble moving down their paths. For example, in the call provided, the agent was collecting the callers information to pass along to the estimate team of this businesses. Once it collected that information, it was supposed to move to the confirmation node where the agent reads back the callers info to confirm it got everything correct, then end the call. But as you can see the node never transitioned out of collecting the callers information. Call ID: call_c006b8f1ea26b71e7e4420322a2 call_1ce56363aa3b43bca59b76dae56 I've added fine tune examples of when to transition out of this node, but it did not help. This just recently started happening and was not an issue before.

I can help with that! This issue is usually caused by the agent not recognizing the completion criteria for the node, even if instructions are set sometimes recent updates or changes in data formatting can affect this. Can you share how the node is currently configured to detect when it should transition?

Hello @George ‼ , can you be more a specific than "Caller provided all required information." , like Caller provided his name, and the home address , you can even divide the node into two or three nodes if there a lot of questions.

This is the current node set up. Should I be more specific about which details need to be gathered before a transition can be initiated? Ie. Transition when: "Caller provided there budget and timeline for the project. @Omar Ashraf | Community Lead is that what you mean too? https://www.loom.com/share/52f8b5b495ab45928af042ecc7b9f239

Yes

For reference: new transition prompting. https://cdn.discordapp.com/attachments/1452364609091670055/1452711536609984593/Screenshot_2025-12-22_at_10.16.34_AM.png?ex=694ace8c&is=69497d0c&hm=e517b8d9ad2ed2c63584670f6aa8935651be52afa441c93779969726b5a193ab&

No its not effected by the model, and I would rather divided this node into two because the multiple questions, but test this first and see if it works for you or not.

Thank you! I was thinking of actually taking out 2-3 of those questions because it's causing a bit of friction on the calls, but I will test.

Can you share the call id

call_eedb5928bdc1d004c4c1b239efe In the testing portal, the transition happens correctly every time. But when it's live, no change.

You have about 7 things in the transition to validate , its a bit too much for the agent , divide this node into 2-3 nodes , to have easier transitions

Interesting. Even though it works in the testing portal?

It will work but if the conversation is not clear enough , it could get stuck as this call , make it simple for the agent will prevent that from happening.

Thanks for the explanation. I'm going to reduce the number of questions we ask, then if the issue continues separate the nodes.