Absolutely critical Abruptly ended the call in bet...
# support
s
I am facing this strange issue where agent is abruptly calling the end call tool and ending the call in between the conversation. So when I check the logs, there actually LLM, STT and TTS shows logs on continued conversation but the call was ended abruptly. - The call ID :- 019a3198-9a31-7aa2-9b17-fd4e92cdc677 - When exactly this happened (the timestamp) - Precise time: 01:45:00:371 30/10/2025 - What response you expected to get - The natural conversation should continue smoothly ending the conversation after user talks by calling end call tool. - What response you actually got instead - The call got cut abruptly. This is an absolutely critical issue as it has been re occurring multiple times. So when I go and check the logs under the call detail page continuation of the expected conversation and output is logged. But when I checked the transcript it is not there, even in real call the agent end the call abruptly. This issue is stoping us from using vapi in production and potentially upgrade to the enterprise plan. https://cdn.discordapp.com/attachments/1433198436647309353/1433198437200822313/Screenshot_2025-10-30_at_2.23.17_AM.png?ex=6903d18e&is=6902800e&hm=daa170b9df72393e06236e9342fc467dcc4cd7b8daac3771336d00a5a284377a& https://cdn.discordapp.com/attachments/1433198436647309353/1433198437616324748/Screenshot_2025-10-30_at_2.17.06_AM.png?ex=6903d18f&is=6902800f&hm=1e70b203aa2da1e3bbaaeddf65314d2d2c1f6f7e4fc5c41e37a45d8e3f195499&
v
Actionable Step: To diagnose why your call ended abruptly, go to your Vapi dashboard and: 1. Navigate to
Observe > Call Logs
. 2. Search for your call ID:
019a3198-9a31-7aa2-9b17-fd4e92cdc677
. 3. Check the
endedReason
field
for this call to see the exact reason the system recorded for the termination. This will help you pinpoint whether the issue is due to configuration, telephony, or an internal error, and is the recommended first step for critical call drop issues ([Debugging voice agents documentation](https://docs.vapi.ai/debugging#check-logs)). Source: - [Debugging voice agents documentation](https://docs.vapi.ai/debugging#check-logs)
h
hey i had this issue as well. its usually because the end call function doesnt interact well with certain models. I would suggest turning off the end call function in the predefined functions tab and using end call phrases only in your api so that the bot terminates only when it says certain phrases
s
Hey I have did the same. I have turned off pre defined end call function and calling end call from tool call. So how do we resolve it ?
@Vapi Could you please help me here ?
c
We will look into this and get back to you shortly
s
Please do, I can also share further details if you need.
@kyle Could you please update me on the issue ?
c
Hi Saleeq, Thanks for sharing the details. Please try updating your assistant prompt by adding the following instructions and removing any previous guidance related to calling the `end_call_tool`: --- IMPORTANT: Do NOT call the
end_call_tool
simply because you or the customer say “have a wonderful day” or other pleasantries. Only end the call if: - The customer explicitly says they need to go, goodbye, or bye. - The customer requests to end the call. - You’ve completed the survey and the customer has clearly indicated they’re done. Always wait for the customer’s response after your closing statement before ending the call. --- Once this is added, please test a few calls to see if the behavior improves, and let us know the results. Best regards, Kyle at Vapi
2 Views