Hi guys, just spoted a BIG BUG with call transfer...
# support
к
Hi guys, just spoted a BIG BUG with call transfers in your UI. Multiple destinations dont work at all and first destination is selected. Because the properties of argument object of the tool are empty even when destinations are created. So, no phone number gets passed into the function. When I updated the tool by cURL to add the property, it started to transfer properly. So this is definitely a BIG BUG. Can you fix this? -d '{ "function": { "name": "transfer_call_tool", "description": "Use this function to transfer the call. Only use it when following instructions that explicitly ask you to use the transfer_call_tool. DO NOT call this function unless you are instructed to do so. If it is new client use +YYYYYYYY else (for existing customers) use +XXXXXXXXX", "parameters": { "type": "object", "properties": { "destination": { "type": "string", "enum": ["+YYYYYYYYYY", "+XXXXXXXXXXX"], "description": "The destination to transfer the call to." } }, "required": ["destination"] } } While your UI has created this UGLINESS { "function": { "name": "transfer_call", "description": "Transfers the caller to a human representative or lawyer, handing off the conversation with full context.", "parameters": { "type": "object", "properties": {}, "required": [] } }, } This child of incest exists already for 4-5 months ... as I read reports on forums. Whats going on?
v
To fix the call transfer bug, update your tool's parameters to explicitly include the
destination
property.
Here’s a working example you can use with cURL:
Copy code
json
"parameters": {
  "type": "object",
  "properties": {
    "destination": {
      "type": "string",
      "enum": ["+YYYYYYYYYY", "+XXXXXXXXXXX"],
      "description": "The destination to transfer the call to."
    }
  },
  "required": ["destination"]
}
Apply this structure to your tool definition, and the transfer should work as expected. [Reference](https://docs.vapi.ai/call-forwarding) Source: - [Vapi documentation: call forwarding](https://docs.vapi.ai/call-forwarding)
To fix the call transfer issue with multiple destinations, manually update your tool's parameters to include the required
destination
property.
Here’s a working example:
Copy code
json
"parameters": {
  "type": "object",
  "properties": {
    "destination": {
      "type": "string",
      "enum": ["+YYYYYYYYYY", "+XXXXXXXXXXX"],
      "description": "The destination to transfer the call to."
    }
  },
  "required": ["destination"]
}
This ensures the assistant receives the correct destination and enables proper call transfers. For reference, see [Vapi documentation: call forwarding](https://docs.vapi.ai/call-forwarding). Sources: - [Vapi documentation: call forwarding](https://docs.vapi.ai/call-forwarding) - [Vapi SIP Trunking Telnyx external number call forwarding troubleshooting (Discord)](https://discord.com/channels/1211482211119796234/1343963959421829172)
s
https://docs.vapi.ai/api-reference/assistants/create have you tried to read their docs here? it's laid out very well on how to set up the transfer assistant.model.openai.tools.TransferCallTool @козак
к
I see, but why it doesn work in UI?
I told about bug in UI, while I know that it works normally while creating/updating tool through API
and I can say more - this docs are probably not up-to-date as the transfer call tool doesnt work with multiple destinations without arguments. It works only when configured like this, with function.parameters.properties.destination https://docs.vapi.ai/call-forwarding while in the https://docs.vapi.ai/api-reference/assistants/create and https://docs.vapi.ai/api-reference/tools/create the function.parameters are not mentioned at all
c
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.
3 Views