You transfer tool needs not be updated via API so it works with multiple destinations. in the UI it does not save destinations properly

Yeah, I’ve seen this before, the issue usually isn’t the API, it’s that the UI doesn’t properly save multiple destinations, so only the first one actually gets passed into the transfer. The fix is making sure those destinations persist in the config instead of overwriting. I can help you sort that out and make sure it works smoothly with multiple numbers. Are you setting this up fully inside the workflow builder, or mixing in some custom code?

I have sorted this, but could somebody fix the UI...

Glad you got it working! The UI still seems to be the hiccup, it’s not saving multiple destinations properly, which can be confusing even though the transfers work. I can help fix that so everything shows and saves correctly.

Hello, Thanks for reaching out to us. We are sorry for the inconvenience. Can you give more details about your concern? Your Org ID, email address and other details that will help us pinpoint your account and to look further into it? We will investigate further and we appreciate your kind understanding and patience.Hi IvanTrue, In the meantime vhere are some steps you can follow: 1. **Verify Configuration**: - Ensure that

phoneCallProviderBypassEnabled

is set to

false

for Vapi-managed transfers. - Remove

"phone-call-control"

from

serverMessages

if present, as it can override default call control. 2. **Check Call Logs**: - Use the Vapi API to retrieve the call details and check the

endedReason

. If it is not

"assistant-forwarded-call"

, verify your assistant's configuration settings. 3. **Validate Transfer Compatibility**: - Confirm that your transfer scenario is supported as some scenarios (like web-to-phone) might not be. 4. **Analyze Provider Logs**: - Get the call ID from the Vapi response and check your telephony provider’s logs for any transfer-related errors [more details here](https://docs.vapi.ai/phone-calling/transfer-calls/debug-forwarding-drops). Make sure to test systematically and document any changes you apply. This will help in further analysis if issues persist.