@Vapi @Vapi Support Bot I’ve run into an issue where the end call message configured in the agent dashboard is not being spoken before the call disconnects. ### What I Observed - The end message is set in the agent configuration. - The agent ends the call immediately without speaking the message. - I tested by removing the Request Start → Default (server will use default message) option, but the issue persists. - Regardless of configuration, the agent terminates the call without delivering the end message. ### Expected Behavior The agent should speak the end call message (as defined in the dashboard) before ending the call. ### Questions - Is this a known bug or a configuration oversight? - Could the Request Start message option interfere with the end call message execution? - Are there additional flags or conditions required to ensure the end message is spoken? Any guidance or fixes would be greatly appreciated. Thanks in advance!

Hi there, Thank you for your message. Our team is currently out of the office. We operate Monday through Friday, from 9:00 AM to 8:00 PM Pacific Standard Time (PST). We’ll get back to you as soon as possible during our normal business hours. If your message is urgent, please mark it accordingly or include “URGENT” in the subject line, and we’ll do our best to respond promptly. Warm regards, Vapi Customer Support Team

I’ve worked on similar voice agent call-flow issues before and can help troubleshoot this. It’s usually related to how the call termination event is triggered in some setups the hangup executes before the TTS playback queue finishes, so the end message never gets spoken. I can help review the agent configuration, request start behavior, webhook/call-end logic, and any interrupt or timeout settings to identify the exact cause and get the end message working properly. @hamza-007

@Vapi @Vapi Support Bot