Calls are getting looped with the user hearing the warm transfer message call id: 019e1766-0304-7ffc-bcab-f06a5c20f2f7

Hi Nightcrawler, We've identified the issue with your calls getting looped. It looks like the warm transfer intro message was played into the main audio stream, which was then picked up by the speech-to-text system as user input, causing the automatic transfer loop. This affected 181 calls. To resolve this, we recommend fixing the audio routing, adding speech-to-text filtering, and investigating any configuration changes made on May 11.

Thank you Praveen, consider this fixed

Hi, I'm closing this ticket now. Let me know if you need anything else.

Thanks praveen, We had one more issue where the user is not hearing the first message for an outbound call, you can hear it in the recording but that is not how it is being played out in a real call, callid:019e18a0-84e1-7000-bff3-465b02fe96b5

move the dynamic name from the

firstMessage

and use a generic opener:

"firstMessage": "Hi there, this is calling from Little Guy Australia."

Static messages get cached by Vapi and play instantly with zero TTS latency. Option 2 — add a small

waitSeconds

buffer: Give the carrier media path time to stabilize before the agent speaks:

"startSpeakingPlan": {
  "waitSeconds": 1.5
}

This adds 1.5 seconds of silence after the call answers before the greeting plays. The TTS generates during that window. Downside: slight delay every call. Option 3 — use

firstMessageMode: "assistant-waits-for-user"

for outbound: The agent stays silent until the recipient says something (e.g., "Hello"). The agent then responds. This guarantees the media path is open before any audio is sent.

"firstMessageMode": "assistant-waits-for-user"