Begin_after_user_silence_ms starts counting before the callee picks up

Outbound conversation flow, start_speaker = user, calling from Retell numbers.

We want the agent to say something when the callee picks up but stays silent, so we set begin_after_user_silence_ms to 7000. In testing, I answered about 4s into the ringing and the agent was already mid-sentence. The timer seems to start at the carrier’s 200 OK, not when the person actually answers.

Same issue as this thread from May, which has no answer: Start_speaker: "agent" fires on carrier SIP answer, not on human pickup — agent speaks before user hears anything

Possibly related: about 1.4% of our connected outbound calls are fully silent on both sides (empty transcript, no agent turn), all from Retell numbers. Example: call_fc2a9c17f91bb1ed119f2a0c7b3

Questions:

  1. Does begin_after_user_silence_ms start at the 200 OK?
  2. Is there a way to start it on the actual pickup, or on the first audio from the callee?
  3. Does end_call_after_silence_ms apply if the agent never spoke?

Hey @maxi Thanks for sharing the details. I’ve escalated this to the relevant team for further review. As soon as I receive an update, I’ll let you know promptly.

Thank You

Hey @maxi here are the answers to your questions :

  • Yes, the timer starts as soon as the call connects

  • For the agent, call connect means the call is answered

  • Yes, end_call_after_silence_ms applies even if the agent never spoke.

Thank You