On bots created with API the redirect number is not beign filled. When the assistant triggers the call transfer the assistant hangs up, the assistant tries to triger though. I tried to call from another phone number and tried different destination numbers. Is the only way now workflows? I used this config in API create request: "tools": [ { "type": "transferCall", "destinations": [ { "type": "number", "number": "+3******3", "message": "Transfering...." } ] } ] https://cdn.discordapp.com/attachments/1372951680601030777/1372951681087705219/image.png?ex=6828a464&is=682752e4&hm=04003946e7d6c808e1f49db89472a019d97704ddf0ff466bf88523a43dcdb4d1&

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!

@Shubham Bajaj please read my ticket. 8dccd8fa-06d9-4135-ab2a-cc46503498bf It happens at the end (trying to forward the call) It just hangs up the call instead of transfering

Who said you this is deprecated? It's not deprecated

@Kings_big💫 said: "Standalone assistants are still supported, but advanced features like call transfers now require using Workflows." And transfer call is not working, also your AI agent is saying is not supported

logs_evidence

- endedReason: assistant-forwarded-call - 🔵 23:03:07:728 Requested Destination Not In tool.destinations. (+34xxxx38) - 🔵 23:03:07:728 Using tool.destinations[0]: { "type": "number", "number": "+34xxx93", "message": "Le paso con el restaurante" } - 🔵 23:03:07:732 Transferring Twilio Call...TwiML:+346xxx193 🔵 23:03:07:870 Live Call Manager Ending...(assistant-forwarded-call)

What does it mean? That it is not vapis fault?

@Juaní As you can see here, the call was transferred successfully. I have DMed you your Twilio call SID. Can you take a look in your Twilio call logs, and share with Me.

ok

The number you were trying to transfer the call doesn't exist in the transfer tool called destinations, and that's why it fell back to the first destination inside the tool. In case you were expecting the call on number A but instead it went on the number B, so you have to add the number A inside your assistant destinations as well .

It was GeoPermissions from twilio. Solved