Hi community, I'm running into an issue with reliably starting a conversation as soon as a user answers a call. I have two main problems: 1. Silent User: If a user answers the phone and says nothing, my assistant (which is set to wait for the user) also stays silent, and the call eventually ends without any interaction. 2. Missed "Hello": Often, if a user says a short greeting like "Hello", the transcriber doesn't seem to catch it. As a result, the assistant never receives the first message and doesn't respond. I've tested all three First Message Mode options: * Assistant waits for the user: This is my preferred mode, but it causes the two issues described above. * Assistant speaks first & Assistant speaks first with model generated message: These modes are not suitable because the assistant starts speaking too early, while the phone is still ringing. My goal is to have the assistant start speaking only after the user has actually answered the call. My question is: How can I configure Vapi to reliably start the assistant's speech as soon as the call is answered by a human, solving both the "silent user" and the "missed short greeting" problems? Is there an event or a setting I'm missing? Thanks for any advice!

Hey! To help track down this issue, could you share: \- The call ID \- When exactly this happened (the timestamp) \- What response you expected to get \- What response you actually got instead This would really help us figure out what went wrong!

Hi For example: Call ID: 00284d5c-c469-4b03-9a6b-1782a4e60078 When it happened: At the start of the call. What you expected to happen: The assistant should start speaking only after the user answers the call. What actually happened: In Assistant speaks first mode, the assistant starts speaking before the user has answered the call (e.g., during the ringing). ----- Also a clear example of the transcriber missing the initial greeting is Call ID a401ffbf-555f-4bb6-be15-02a5b6dd3fb9. On this call, the user said "Alo" three times, but the assistant never detected it and failed to respond. This is a very often problem.

Hey Andrii, thanks for sharing your details. Our team will look into it and get back to you soon with an update.