I am having multiple issue on voice transfers where the warm transfer is being played in the middle of the conversation rather than the beginning, from Vapi's side it looks normal but on the operator they are hearing it differently Here is the call id: 019d6e35-11a1-7000-a1e8-48f4596acf80 And the other issue is it is not saying the transition line when transffering like "one moment while i connect you", i have put it in both the system prompt and in the transfer tool but it is never consistent Here is the call id:019d6e37-26f6-7000-9d38-3951d07fbe4a

This feels like a timing/buffering issue where the transfer fires correctly but the audio reaches the operator out of order, so I’d check if the transfer is being triggered before the previous audio fully finishes playing. The missing transition line is likely a race between the model response and the transfer trigger, so forcing the transfer to wait for that phrase or handling it fully in the tool usually makes it consistent. Happy to dig into those call IDs with you and help debug it directly, are you using streaming responses or waiting for completion before triggering the transfer? @nightcrawler

hi @Matt can you look into the callid please

Happy to help take a look, but just to clarify I’m not Vapi support, I work as a specialist on implementations and debugging. I can’t access the call ID from my side unless I have access to your workspace. If you can share logs or grant access, I’ll help you analyze the issue and figure it out . @nightcrawler

Sorry, am not comfortable sharing those informations, i need support from vapi @Vapi

Hi, I reviewed both calls, there are two separate issues with different causes: Call 1 (019d6e35 – failed transfer): The caller hung up ~2 seconds into the hold tone. Vapi had already dialed the operator, but since the caller disconnected, there was no one to bridge. This is expected behavior, not a bug. Call 2 (019d6e37 – garbled transition): The transfer succeeded, but the transition message sounded broken because the model was mid-sentence when the transfer was triggered. Root Cause: you have the transition phrase in two places, in the system prompt (

"ALWAYS say one short line such as..."

) AND in the tool's

transferPlan.message

. they're conflicting. the model tries to generate the phrase itself mid-stream, which breaks the output. Fix: Please remove the transition instruction from the system prompt and keep it only in the transferPlan.message. This ensures the message plays cleanly at the right moment.