Vapi is the Voice AI platform for developers.

Vapi AI

<@1006897684965244938>  So, just to confirm — for something as basic as call transfer, we now have to use workflows, which are still in beta and only support Vapi as the model provider?

Why make something simple more complicated? I totally get the value of workflows for more advanced use cases, but disabling the old option before the new one is fully ready — and for such a basic feature — doesn’t seem like the right call.

Kindly share it in details

https://roadmap.vapi.ai

??? I can only see feature requests there. 
I'm just saying there is a basic functionality documented in your docs that it is deprecated in favour of a non-code visual node approach, when Vapi was supposed to be API focused.
https://cdn.discordapp.com/attachments/1373580787856703578/1373589250448031845/image.png?ex=682af62d&is=6829a4ad&hm=61bc6088619d6f5b410299d3cae8cad3b7d99f17279dea4aa351e716a7d0f91d&

<@1006897684965244938> You referred to call transfer as an "advanced functionality," but honestly, it’s not. Any AI assistant should be able to redirect to a human — that’s a basic requirement in most real-world use cases.

So just to clarify: for that essential feature, we now can only use the Vapi model (in workflows), and not OpenAI or any other provider? That feels like a pretty big limitation.

Hey <@471980021003845643> we are API first company and `transferCall` is not deprecated. Can you please help me the issue your facing?

I opened a support ticket a few days ago, I create the assistant with transferCall tool but when it tries to transfer it hangs up. In the dashboard the field for transfer call phone is empty. <@865531204849500190>

<@471980021003845643> just for clarification, this issue has been resolved.
cc: <@319034765808369666> <@1006897684965244938>