We started getting reports of calls ending too quickly yesterday around 5pm CST. The end call tool has started firing about a message too soon and ends in an unexpectedly abrupt end to the call. Did something change recently? Is there config hidden in the API that we need to flip? My own test calls:

ed839c81-cfac-456d-9356-86777015a8e2
0080891c-1e82-47e8-8ae1-6011f970e413
bd0a4716-00c4-4652-a340-10df3c85ffae

Thank you for sharing the call IDs and details. Based on the documentation, there are no recent changes or hidden API configs for the End Call tool. To help diagnose further, could you confirm if the abrupt call ending is happening with all assistants or only specific ones? This will help narrow down whether the issue is configuration-specific or platform-wide. Sources: - [Default Tools Documentation](https://docs.vapi.ai/tools/default-tools) - [Call End Reasons](https://docs.vapi.ai/calls/call-ended-reason) - [Changelog May 2025](https://docs.vapi.ai/changelog/2025/5/9)

Please use an endCall phrase to have the assistant end the call and delete the endCall tool from the assistant. Adjust your prompt to say the endCall phrase once your assistant has completed all the tasks it needs to.