in transferCall, do i need to specify parameters ?...
# support
h
Hi
v
Yes, specifying parameters—especially the
destination
parameter—is essential for
transferCall
to work.
Without it, the call will not be forwarded. Here’s a minimal example:
Copy code
json
"parameters": {
  "type": "object",
  "properties": {
    "destination": {
      "type": "string",
      "enum": ["+1234567890"], // Replace with your number
      "description": "The destination to transfer the call to."
    }
  },
  "required": ["destination"]
}
Be sure to include this in your tool configuration for successful call transfers. Sources: - [Vapi documentation: call forwarding](https://docs.vapi.ai/call-forwarding) - [Vapi SIP Trunking Telnyx external number call forwarding troubleshooting](https://discord.com/channels/1211482211119796234/1343963959421829172)
v
Message marked as helpful by @Hans! 🎉
Message marked as helpful by @Hans! 🎉
k
Send your call id
h
You mean tool id ? 906508b3-fc46-4e57-86b8-22d53e39f44d If it 's not this, how can i get call id ? 🤔
Here goes screenshot of agent I gave system prompt details Is vapi.ai smart enough to redirect call without
parameters
config ? Or am I going something wrong ? 🤔 https://cdn.discordapp.com/attachments/1375161681763631186/1375170894330200084/image.png?ex=6830b732&is=682f65b2&hm=157184f1617b33ed5d1a13432cfe28a661ea63c23d48e945220c85510e264cf9&
k
Vapi can redirect calls without explicit parameters, but proper configuration with defined destinations and messages is recommended for reliable forwarding.
h
I have found issue in Messages panel In this example, we can add multiple request-start messages with condition for several phone numbers But in UI, we can add only 1 message for message type. https://cdn.discordapp.com/attachments/1375161681763631186/1375218005419491510/image.png?ex=6830e312&is=682f9192&hm=5d4d4c9c4566316008b6b481ff00c06a21cb39fbbba6be743a61ea37ab5cc9b3&
k
Hey Hana, checking if this is resolved/solved for you?
h
Yes, it 's solved
v
For reliable call forwarding in Vapi, always specify the
destination
parameter in your
transferCall
function, even if calls appear to work without it.
This ensures predictable behavior, especially as your configuration grows. Example:
Copy code
json
{
  "function": {
    "name": "transferCall",
    "parameters": {
      "destination": "+15308891500"
    }
  }
}
This approach avoids ambiguity and supports custom messages and transfer plans per destination. Sources: - [Call Forwarding Documentation](https://docs.vapi.ai/call-forwarding) - [Default Tools: Transfer Call](https://docs.vapi.ai/tools/default-tools#transfer-call)
For reliable call forwarding in Vapi, always specify the
destination
parameter in your
transferCall
tool configuration.
Here's a recommended example:
Copy code
json
{
  "function": {
    "name": "transferCall",
    "parameters": {
      "destination": "+15308891500"
    }
  }
}
This ensures your call is routed as intended, regardless of any fallback behaviors Vapi may apply if parameters are omitted. Sources: - [Call Forwarding Documentation](https://docs.vapi.ai/call-forwarding) - [Default Tools: Transfer Call](https://docs.vapi.ai/tools/default-tools#transfer-call)
k
Glad the issue was resolved. Please reach out to us if you have any other questions regarding this issue
y
Where do you specify this since you dont have access to that request when invoking the transfer call tool?
k
This ticket has been marked as solved, and as a result, you will no longer receive any further responses. Kindly create a new support ticket to escalate your inquiry.