Hi, it seems every time I call and ask to forward to a person, manager, or live person, the transfer call tool works. It sees us forwarded, but in reality, I'm getting a hang up and I don't get transferred. So the call just ends. And here's my call log. See if I'm not sure what I'm doing wrong. I'm not sure if it was working before. I've seen other people in the support thread having the same issue. I'm not sure if this is a global VP issue or something I'm doing. If you can help with this, that'd be great Call ID: 019e1f7f-ef03-7001-89d2-875f196c1186

Hey, I’ve seen this happen a few times lately too. Usually when the transfer tool says “success” but the call drops, it’s often tied to the SIP/trunk handoff, transfer destination format, or how the provider is handling the redirect behind the scenes. Since others are reporting similar behavior, it could also be a broader Vapi/provider-side issue. I can help you trace it properly from the call logs and transfer flow. Are you using SIP transfer, Twilio, Telnyx, or another phone provider on the outbound/inbound side? @quang

I am using the vapi number and for transferring it is transferring to another provider

That actually narrows it down a lot. Since it worked before, the transfer trigger is probably firing correctly, but the external provider handoff is failing or being dropped. Small changes in the prompt, transfer timing, or number formatting can sometimes cause silent hangups like this. Since others are reporting it too, there may also be an active Vapi-side transfer issue. I’d mainly check the transfer number format (+E164), whether the assistant ends the call right after the tool fires, and the transfer type being used. If you send the transfer config or prompt section, I can help pinpoint the exact issue. @quang

Thanks, this actually makes the issue pretty clear. Your tool config looks correct, so this is likely not a prompt problem but a transfer execution gap usually blind transfer + empty destination description can cause the handoff to drop silently in some Vapi/provider setups. Best next step is to test switching to warm transfer (even temporarily) and confirm the call isn’t ending right after the tool fires, plus verify no competing transfer tools (Amy/Nancy) are being triggered by the same intent. I can help you debug this directly and pinpoint whether it’s config-side or platform side. Want to take this privately and go through the call flow + logs together? @quang

sure

All good, I’ve just sent you a direct message so we can go through this properly. @quang

@Matt @quang Can you send an update if you found a fix? I'm having the same issue. I've ruled out swithching to warm-transfers, etc. I'm personally thinking it's a bug on the platform side. I'd love to hear what you find out.

Yeah, at this point it’s looking less like a setup mistake and more like a transfer bridge/routing issue on the platform side , especially since warm transfer isn’t resolving it and multiple users are seeing the same behavior. The fastest approach now is tracing the transfer events + provider handoff logs to see exactly where the bridge fails after the tool fires. @Dalton

@Dalton not yet. @Matt offer to solve this for a charge. I’m going to see if I can solve this or just hire someone to fix it and build out some other things for me

Yeah, I do charge for hands on debugging since this is part of my work and expertise. The same way everyone charges for the skills they use to make money professionally. I already spent time narrowing down the likely cause and honestly kept the rate pretty low so you could get it resolved quickly instead of spending hours troubleshooting platform routing and transfer behavior yourself. No pressure either way, just offering direct help if you want it fixed faster. @quang

Hey Matt, I didn't mean to anything. I thought you were part of Vapi's support team or something. I'm just here. I thought Vapi had a support channel because they led me here. I didn't even know this was not Vapi support.