Hi Im trying to set up multiple destinations for the transfer call function and it doesnt seem to be working. It keeps defaulting to the first destination. I have the system prompt configured to point to the transfer call destinations. Has anyone encountered a similar issue, or has gotten it to work?

You have to update the Assistant using curl command becuase their frontend is not working.

@Ladiesman217 I also created a support ticket for this specific issue.

Okay I will do that. Thanks

Its with tool Configuration .

Hi Ladiesman217, If the

transferCall

function isn't working with multiple destinations, here's a concise set of steps you can follow to troubleshoot: 1. **Check Ended Reason**: - Use the API to get the call details:

bash
     curl -X GET "https://api.vapi.ai/call/{call_id}" \
       -H "Authorization: Bearer YOUR_API_KEY" \
       -H "Content-Type: application/json"

- Ensure the

endedReason

is "assistant-forwarded-call". If not, review your assistant configuration. 2. **Review Destination Configuration**: - Ensure that all destination numbers are correctly configured in the tool. Verify that the list includes all intended numbers with the correct formats and messages. 3. **Server Messages Configuration**: - Confirm

serverMessages

in your assistant configuration doesn’t override the transfer settings:

json
     {
       "assistant": {
         "serverMessages": []
       }
     }

- Remove

phone-call-control

unless custom transfer logic is required. 4. **Check Bypass Settings**: - Ensure the

phoneCallProviderBypassEnabled

is set to false if you want Vapi to control call transfers. 5. **Analyze Call Logs**: - If

endedReason

is "assistant-forwarded-call" but calls drop, investigate telephony provider logs with the

phoneCallProviderId

for any errors or issues. Ensure you also verify any scenarios where unsupported call transfer types may be involved (e.g., web to phone), as certain transfer paths are not supported and could result in failed attempts. For detailed steps on adjustments and setup, you can explore the [Debug forwarding drops](https://docs.vapi.ai/phone-calling/transfer-calls/debug-forwarding-drops) guide. Adjust as needed and test systematically to confirm it's working as expected.

can you elaborate pls. So is there a solution?

I have a right configuration command . But due to message length , I am unanle to send you.

can you upload as a file pls... would greatly be appreciated!

Ok I will do.

@Sage where you able to get this working? Thanks for the help, @Dev . I am having the same issue.

Could you please send a call id where the call transfer fails? We would like to review the logs

Here is the call id

b3732e12-36ec-4e9d-8d6e-9fa176b0819d

copying @bibs who is also having the same issue

You are welcome. @User

In your transfer tool, you have the enums set to the destination names, but no direct association of the name to the number:

"function": {
              "name": "transfer_call_tool_rashidy_law_v5",
              "description": "Transfer call to appropriate destination at Rashidy Law",
              "parameters": {
                "type": "object",
                "properties": {
                  "destination": {
                    "enum": [
                      "George",
                      "Rashidy"
                    ],

In the tool description, you can write the names into it from the enum which might give the assistant more context about which number belongs to who. Also, replace the names in the enum field from names to numbers and you should be able to see some significant changes in behavior.