Call Transfer is not happening
# supporti
ICY
04/09/2025, 6:51 PMAPI : https://api.vapi.ai/call/phone
Request Body : vapi.json (Attached)
After the first assistant the call is not transferred to Symptoms Checker Assistant, even though the assistant speaks the message, but then goes blank and the call automatically gets cut.
https://cdn.discordapp.com/attachments/1359601737178288259/1359601737417359572/vapi.json?ex=67f8134a&is=67f6c1ca&hm=575a67ee275b5d3159020a878cabf4c1714269b116b251ff22a8bfd5b139db16&
ICY
04/09/2025, 6:52 PM@User Please look into this
k
Kings_big💫
04/09/2025, 7:05 PMVerify the accuracy of the assistant’s ID, ensure proper configuration of the transferCall function, and consult the call logs for specific error messages to diagnose and address the problem..
i
ICY
04/10/2025, 5:15 AM@Kings_big💫 How can i configure the transfer calls?
Also the accuracy of assistantIds and names are correct in request.
In Call logs, in messages, i can see the call transfer to Symptoms Check Assistant, but still in call, it assistant does not responds and the call automatically gets cut
The last messages in Call logs messages are :
{
"role": "tool_calls",
"time": 1744261150843,
"message": "",
"toolCalls": [
{
"id": "call_azzfuORWozk8RacinAC7OWG0",
"type": "function",
"function": {
"name": "transferCall",
"arguments": "{\"destination\": \"Symptoms Check\"}"
}
}
],
"secondsFromStart": 48.844
}
------------------------------------------------------------------------------
{
"name": "transferCall",
"role": "tool_call_result",
"time": 1744261153534,
"result": "",
"toolCallId": "call_azzfuORWozk8RacinAC7OWG0",
"secondsFromStart": 51.535
}
and the next message displayes the Symptoms check prompt and then no further messages as the call gets cut
ICY
04/10/2025, 5:23 AM@User Please look into this
ICY
04/10/2025, 7:00 AM@Vapi Support Bot @User @Vapi
s
Sahil
04/10/2025, 7:16 AMCan you send me the call_id?
Sahil
04/10/2025, 7:16 AMAlso, can you make a few call right now and provide me the call_id of that? ^^
i
ICY
04/10/2025, 7:38 AMsure @Sahil
API Details : Vapi.json Uploaded
Call IDS :
[ web-call : "d60c72f3-c205-4d89-888f-2887c50733a4",
phone-call : "bfabbd57-b652-4050-b0ef-9237a427afa2" ]
now, not even the first assistant is responding.
Also, we are creating the squad using the api details provided.
Can you let me know, if there is any transfer call functionalities or configurations in vapi that i am missing ? or do i need to go for any alternate method for squads
https://cdn.discordapp.com/attachments/1359601737178288259/1359794668300275722/vapi.json?ex=67f8c6f8&is=67f77578&hm=9319a7179b99878e3bbf8dd14200c2b64af27f299ffc17351282cbe49024b7b6&
ICY
04/10/2025, 7:39 AM@Sahil
If the data provided doent seems to be enough to undersand, can we join over a meet call ?
s
Shubham Bajaj
04/13/2025, 9:42 PMlooking into it.
Shubham Bajaj
04/13/2025, 9:51 PM🔵 06:56:56:744 Converted Requested Tools Calls To Internal Format. [
{
"type": "transferCall",
"destinations": [
{
"type": "assistant",
"assistantName": "Symptoms",
"description": "Transfer the call after introduction ",
"transferMode": "rolling-history"
}
],
"function": {
"name": "transferCall",
"description": "Use this function to transfer the call. Only use it when instructions explicitly ask you to use the transferCall function. DO NOT call this function unless you are instructed to do so.\n\nHere are the destinations you can transfer the call to:\n 1. Symptoms. When: Transfer the call after introduction ",
"parameters": {
"type": "object",
"properties": {
"destination": {
"type": "string",
"enum": ["Symptoms"],
"description": "The destination to transfer the call to."
}
},
"required": ["destination"]
}
},
"messages": [
{
"type": "request-start",
"blocking": false,
"contents": [],
"content": "Transferring the call now",
"conditions": []
}
],
"toolCall": {
"id": "call_DITjqavNGIP3coLKHwAsCOCt",
"type": "function",
"function": {
"name": "transferCall",
"arguments": {"destination": "Symptoms"}
}
}
}
]
Shubham Bajaj
04/13/2025, 10:01 PM🔵 06:56:58:646 Queuing Say Request. (Length: 19) (content: "Shall we start now.")
🔵 06:56:58:647 Say Request...19 (say: "Shall we start now.", interruptible: false, audio: false, endCallOnError: true, addToModelOutput: true, endCallAfterSpoken: false)
🟡 06:56:58:648 Couldn't Complete Say Request {
"task": {
"content": "Shall we start now.",
"endCallOnError": true,
"interruptible": false
},
"error": {}
}
🔵 06:56:58:697 Couldn't Parse JSON. Error: SyntaxError: Unexpected non-whitespace character after JSON at position 71 (line 1 column 72). {"type":"speech-update","status":"stopped","role":"assistant","turn":5}{"type":"conversation-update"
Shubham Bajaj
04/13/2025, 10:01 PM@ICY The JSON parser encounters the end of the first valid object at position 71 (the closing }), but then immediately finds another opening { instead of proper separation, causing the syntax error.
This is likely happening because two separate events are being emitted very close together in time, and their JSON representations are being concatenated in the output stream without proper formatting.
Shubham Bajaj
04/13/2025, 10:01 PMIt is on us, and our team will be working on it
Shubham Bajaj
04/13/2025, 10:02 PMcc: @Kings_big💫