Q4
01/27/2026, 7:46 AMAI Evy
01/27/2026, 7:46 AMAI Evy
01/27/2026, 7:46 AMPrompt based—meaning the LLM generates the message based on the config and the conversation context. [(1) ]()
There's an important clarification: these options control the agent's behavior when the user is not talking during the function call period. If the user interrupts or talks, the agent would respond normally regardless of these settings.
A few possibilities for what you're experiencing:
1. **User interaction triggering speech**: If the user says something during execution, the agent may respond independently of the "Speak During Execution" setting.
2. **Potential bug**: There have been community reports of unexpected behavior with these settings. One user reported that even with both "Wait for Result" and "Speak During Execution" off, the node still appeared to wait instead of transitioning immediately. [(2) ]()
3. **LLM-generated content**: Since these settings are prompt-based, the LLM might be generating speech based on conversation context rather than the explicit setting. [(1) ]()
I'd recommend:
- Checking if there's any user speech happening during the function call
- Reviewing your prompt to ensure it doesn't instruct the agent to speak during function execution
- If the issue persists, this may be worth reporting to support with your call ID for investigationAI Evy
01/27/2026, 7:46 AMAI Evy
01/27/2026, 7:46 AMQ4
01/27/2026, 7:49 AMAI Evy
01/27/2026, 7:49 AMAI Evy
01/27/2026, 7:49 AMwait for result is on and speak during execution is off, the agent will transition once the function result is ready. However, "if the user interrupts the agent, the transition can also happen once function result is ready and user is done speaking."
If this behavior doesn't fit your use case, you may need to adjust your flow design or consider whether blocking interruptions during the function call would provide a better experience.AI Evy
01/27/2026, 7:49 AMAI Evy
01/27/2026, 7:49 AM