Changed behavior - breaking
# support
j
Hi, recently ( not sure of timeframe) , the webhook behavior changed to send a status update only on successful calls. see call log 4e72282f-5d64-4f5f-8ce3-45c65bb18bea . Previously, it sent status updates always and end of call report only on successful calls that connected, but that looks to be opposite now (maybe). Please advise on why this behavior changed, and how to be notified of it in advance ( like weeks maybe?) in the future. This has brought our system down, and i can't even begin to fix it unless i get a new understanding of the behavior.
documentation states that it should be sending both for all calls. Please make the behavior match the documentation. https://docs.vapi.ai/server-url/events
update: it does not look like it always sends an end of call report either. Please see call id 971b2bca-0b35-41a8-af19-262423e85c1f
also ,end of call report isn't even enabled on my agent. fd697ea5-ccc7-48ed-9fa4-b633f2301f9c this is definitely a bug
@Vapi @VAPI Tech Please address this.
@Shubham Bajaj
@Kings_big💫 maybe?
k
To help track down this issue, could you share one or two: - The call ID This would really help us figure out what went wrong!
j
Its in the post @Kings_big💫
call id : 971b2bca-0b35-41a8-af19-262423e85c1f agent id : fd697ea5-ccc7-48ed-9fa4-b633f2301f9c I am re-adding it here for easier visibility
k
Looking into it
j
thank you!
s
Looking into It.
j
fyi - this is not an isolated issue, it is applying across many calls. It broke our production system. I just posted one that was most recent, but it is causing issues with keeping our crm up to date with the 5k+ calls we make daily, which means our contact cadence doesnt get updated, and we end up spamming our leads.
s
Hey @jsieber-eip We have recently made a change where we send an end-of-call report for all calls. That's why it's getting sent to your server URL as well, even without subscribing to it. This is a bug that will be fixed in a day or two at max.
j
@Shubham Bajaj why isn't it sending the status-update ?
it used to send status-update for all calls if i selected that for server-hooks, but it started not sending it for failed calls, and only sending the end-of-call-report
Do i need to rewrite my app to expect only an end-of-call-report for all calls (if enabled?)
s
No it will be fixed in upocoming days.
j
ok.. will there be an announcement? and will it begin sending status updates on all calls when they end?
s
Yes once this is fixed we will announce it using changelog and newsletter.
j
I'm going to change from using status-updates to using end-of-call-report since it looks like they are consistently sending and the status-updates haven't been fixed. Can you confirm all calls will now send end-of-call-report if it is enabled in server messages? And that this won't be patched back in the next release to only sending for successful calls, as it did previously? @User
p
End-of-call reports should be sending. Our team is working on resolving the issue with status-update server messages. Thank you for your patience
j
I sent shubham a case when an end-of-call-report did not send
p
Hey jsieber-eip, I wanted to let you know that we're managing a high volume of support requests at the moment, so our response time might be a bit slower than usual. I truly appreciate your understanding and will get back to you as soon as possible!  Thanks again for your patience!
Hey jsieber-eip, I sincerely apologize for the delay in our responses this week. We experimented with some process adjustments that didn’t work as intended, and unfortunately, this caused some disruptions. That’s entirely my responsibility. Just a quick note—our team is unavailable on weekends. However, if something urgent or critical comes up, feel free to reach out to me directly, and I’ll assist you. The support issues will be resolved in the coming weeks, and starting Monday, you can expect more consistent and improved support. Thank you so much for your patience and for continuing to stick with us!
Could you also send that case or call id here?
j
it's above in the thread
p
Hi, First off, we want to sincerely apologize for the delay in getting back to you. We understand how frustrating it is to wait - especially when you're counting on us - and we owe you a clear explanation of what’s been happening and how we’re addressing it. Over the past few weeks, we've seen a significant increase in support requests. While this reflects exciting growth, it has also stretched our small team and exposed some real challenges in scaling our support operations. To improve your experience, we’ve taken a step back to reassess our approach. Here’s what we’re implementing: - Smarter Support Through Automation: We’re investing in our AI support systems to help you resolve issues more efficiently. Soon, our support bot will offer expanded capabilities, making it easier to access accurate, instant help—particularly for common or repetitive queries. - Expanding the Support Team: To meet growing demand, we’re adding 2–3 new team members focused on managing support volume and improving response times. - Prioritized SLAs for High-Usage Accounts: We’re introducing service level improvements for users who are growing with us: - Accounts with usage over 1,000 minutes/month will receive prioritized support. - For all general inquiries, we’re establishing a standardized 48-hour response time. We’re confident these steps will lead to faster, more reliable support and help us better serve you as you grow with us. Also, in case you still need help with this ongoing ticket, do let us know, and we will help you get this resolved as soon as possible. Thank you for your continued patience and for being part of our journey. Warm regards, Vapi Team