### Answer To improve a global node's ability to identify confusion in a conversation, you can use several techniques from the conversation flow documentation [(1) ]() : Add conversation finetune examples - Provide specific examples of confused user responses and how the agent should handle them. This helps the model understand what confusion looks like in your specific context . Adjust the LLM temperature - If the agent's responses are inconsistent in detecting confusion, try adjusting the LLM temperature for that node . Change the node model - If instructions are concise but the agent struggles to follow them, try using a more capable LLM model for this node . Make transition conditions more flexible - Ensure your transition conditions from the global node precisely match your intended triggers. Consider breaking down complex conditions into multiple simpler ones . For global nodes specifically, you can configure them with custom settings including choosing a different LLM model and adding fine-tuning examples for both conversation response and transition [(2) ]() . Since global nodes can be triggered at any point in the conversation , make sure your confusion detection instructions are clear and specific about what constitutes confusion (e.g., repeated questions, "I don't understand" phrases, contradictory statements) .

​ To learn more, see the sources I considered: [[1] Debug guide](https://docs.retellai.com/build/conversation-flow/debug-guide) [[2] Conversation Node](https://docs.retellai.com/build/conversation-flow/conversation-node) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.

### Answer I don't have specific information in the available sources about whether dynamic variables set within components are visible to the main conversation flow [(1) ]() [(2) ]() . The documentation shows that components have their own internal structure with nodes, tools, and start nodes [(1) ]() [(3) ]() . It also explains that you can set

default_dynamic_variables

at the conversation flow level [(4) ]() [(5) ]() [(3) ]() , but doesn't explicitly address variable scope between components and the main flow. For clarification on this specific behavior, I recommend: - Visit [Documentation]() - Visit [Hire certified Retell partner]() Would you like a general answer based on my knowledge about how variable scoping typically works in similar systems?

​ To learn more, see the sources I considered: [[1] Components](https://docs.retellai.com/build/conversation-flow/components) [[2] Dynamic Variables](https://docs.retellai.com/build/dynamic-variables) [[3] Create Conversation Flow](https://docs.retellai.com/api-references/create-conversation-flow) [[4] Get Conversation Flow](https://docs.retellai.com/api-references/get-conversation-flow) [[5] Update Conversation Flow](https://docs.retellai.com/api-references/update-conversation-flow) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.