Unexpected behavior of end tool functionality
# support
s
As we are working on to build an Voice agent, we are came to notice the repetitive issue occurs on the path of handling the call end logic. Scenarios where the end logic fails: 1. The Agent are in operation it asks a question with the user and the user replied to the agent question - after that by logically agent should use some tools internally at the time of gap user as expected didn't speak anything then the system finds its in-active and cuts the call without any prior information to the user. We are enabled the End call function in the vapi > Assistant > Predefined function > Enable End Call. 2. We are additionally created a tool from the tools tab to end the call, Tool Id: 2367ed18-8801-4055-b333-3bafd6115066 In this scenario the tool invoked as expected - when the user says bye, wind up kind of keywords - but from vapi side the call is not disconnected for next 10 seconds.
v
Thank you for describing the scenarios. To help diagnose the delay and user notification issue, could you please confirm whether you have configured any assistant hooks or messages to notify the user before the call ends, especially in cases of inactivity or when the custom end call tool is triggered? Sources: - [Vapi Default Tools](https://docs.vapi.ai/tools/default-tools) - [Custom Tools](https://docs.vapi.ai/tools/custom-tools) - [Call End Reasons](https://docs.vapi.ai/calls/call-ended-reason) - [Assistant Hooks](https://docs.vapi.ai/assistants/assistant-hooks)
s
How to add hooks and call end reasons in the dashboard not in programmatic wa
k
Calls end prematurely due to silence during tool processing, and custom end call tool has a 10-second delay; adjust silence timeout, add idle prompts, and ensure the tool runs synchronously to fix it.
a
You can set up call forwarding. If there's an error, we'll forward the call for you.