Hi, i just discussed this issue during Arthur's OH, and he suggest to raise a ticket as a debug is needed. We set the waitSeconds to 3.0 seconds for the entire call, but in some cases the BOT start to speak while the user is still speaking. I believe it happens when the user start to speak, stop to speak for a second, and start to speak again. the waitSeconds timer maybe start the 3 seconds count from the brake time and interrupt the user while he is still speaking. See call ID a207f0d6-8403-4c07-a650-a75ef8c9ba52 as an example. time 16:05:00:347 as a good example. another time example inside this call: 16:05:28:359 see attached screen shot with this call graph. i marked the 2 example above and another one. You can see the bot started to speak immediately after the user (or even before the user ended on the second example), and you can see the user speak with a short brakes in the middle which probably cause my problem. i would expect VAPI to reset the 3 seconds timer once the user start to speak again. Let me know if you want me to try and recreate such a scenario myself while speaking in English. Hopefully you have enough details to debug with this call ID. https://cdn.discordapp.com/attachments/1389323129368612875/1389323129620267038/Screenshot_2025-06-30_220936.jpg?ex=6864337e&is=6862e1fe&hm=fe6d3d49b83c38e0c1108dda8eeaa2c52dfbc8168074fbed4b38bcfcdf40b34b&

We see smartEndpointingPlan enabled, which is mostly configured for English. We would recommend disabling it and increase the waitSeconds to 4 or 5.

Hi, i tried your suggestion but still not solve our problem (and we must have another fix for the customEndpointingRules if we will use waitSeconds 4-5 seconds). see Call id 531657cb-c159-45bd-8869-a11440aa1e17. I did this call myself to test the changes. in some cases the bot still started to speak to early. i tried to investigate inside the log. see attached. maybe the problem is because no checkpoint of User speech possibly starting when it should? although in my last example i have such checkpoint and still not OK.

Hey, our team is looking into this and will keep you updated soon.