transferCall tool fails when destination is set to...
# support
d
I've seen multiple post about this issue but havent seen any concrete response from Vapi's team. I am trying to build a transferCall tool with destination being another assistant. Here is my tool payload: "type": "transferCall", "function": { "name": "transfer_call_tool", "parameters": { "type": "object", "properties": {}, "required": [] } }, "messages": [ { "type": "request-start", "blocking": false } ], "orgId": "32cfed26-1556-4ec3-bb3b-cb3d7ff36176", "destinations": [ { "type": "assistant", "transferMode": "rolling-history", "assistantName": "GFslow" } ] } The name is matching exactly the name of the destination assistant. However, when calling the assistant this tool is attached to, the call fails with message "Couldn't find assistant GFslow" @Vapi Can you tell me if this feature is broken OR if i missed something in the configuration of this tool?
c
Hi, could you please provide a call id where you experienced this issue? We would like to review the logs to identify the cause.
3 Views