### Answer The conversation node has a Block Interruptions setting that, when enabled, prevents the agent from being interrupted by the user while speaking. [(1) ]() If your first node has this setting enabled, that would explain why the agent isn't interruptable at the start of the conversation. You can check and disable this in the node settings. Additionally, some users have reported that for certain use cases (like legally required disclosures in California) , they intentionally use the conversation flow builder so that the initial stage is uninterruptable. [(2) ]() To allow interruptions on your first node: - Open the node settings for your first conversation node - Ensure Block Interruptions is disabled [(1) ]() If the setting is already disabled and you're still experiencing issues, I'd recommend filing a bug report with your call IDs for the team to investigate.

​ To learn more, see the sources I considered: [[1] Conversation Node](https://docs.retellai.com/build/conversation-flow/conversation-node) [[2] Discord message from @julientrwl on 2025-01-20](https://discord.com/channels/1186424376300679209/1186462578310910112/1330995805242523712) ​

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

### Answer If Block Interruptions is already disabled and the agent still isn't interruptable on the first node, this could be related to how the turn-taking model handles the initial agent speech. A few things to check and try: - **Interruption Sensitivity**: You can adjust the Interruption Sensitivity setting to make the agent more or less responsive to user interruptions. [(1) ]() - **Responsiveness setting**: Lowering the responsiveness slightly may help the system better detect when a user is trying to interrupt. The turn-taking model uses contextual analysis to determine when to respond and when to wait, combining sound signals with semantic understanding. [(2) ]() [(3) ]() In some cases, during the very first utterance, the model may not yet have enough context to properly detect interruption attempts. I don't have documentation that specifically explains why the first node might behave differently regarding interruptions when Block Interruptions is disabled. I'd recommend sharing your agent ID and a call ID where this issue occurred so the Retell team can investigate further. Check out these potentially useful sources: - [Conversation Node]() - [VAD vs. Turn-Taking Endpoints in Conversational AI]() - [Retell AI's Turn-Taking Model for Seamless Calls]()

​ To learn more, see the sources I considered: [[1] Agent interrupting users on speakerphone calls](https://discord.com/channels/1186424376300679209/1442882951246512168) [[2] VAD vs. Turn-Taking Endpoints in Conversational AI | Retell AI](https://www.retellai.com/blog/vad-vs-turn-taking-end-point-in-conversational-ai) [[3] Retell AI's Turn-Taking Model for Seamless Calls | Retell AI](https://www.retellai.com/blog/how-retell-ais-turn-taking-model-ensures-seamless-calls) ​

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