We are building a system that relies on the end-of-call-report webhook and uses the summary analysis to trigger post-call processing. However, we noticed that for one of the calls, the end-of-call-report webhook was never received. Call ID: CA38e703801877408cca4939b0313da43b Timestamp: July 29, 2025 — Call started at 10:00:55 UTC, ended at 10:15:41 UTC According to the Vapi call logs, the call ended with the status: call.in-progress.twilio-completed-call However, based on Twilio’s call logs: - The call status was completed - Twilio sent the final webhook to Vapi’s /twilio/status endpoint - The webhook included CallStatus=completed in the payload - Vapi responded with HTTP status 201 Given this, could you help us understand why the end-of-call-report webhook was not triggered on your end?

Hey Yasu, thanks for sharing your details. Our team will look into it and get back to you soon with an update.

Thank you so much Praveen. We really appreciate your help. Here is some additional context: This issue occurred with an important user’s call, so we would be very grateful if you could help resolve it. The same issue continues to occur only with specific To numbers. Call ID: c8fb66e4-363e-41d0-b76d-c884bdf16f2e Time: July 30, 2025 at 10:00 (UTC)

Hey Yasu, I’m really sorry for the trouble you’re having. Let me check with our team and get back to you with an update soon.

The user’s level of urgency is increasing, so it would be very helpful if you could check this as soon as possible. Aside from upgrading to the Enterprise plan, is there any other way to speed up responses to this kind of trouble support?

Het Yasu, we are working on your issue now.

Thank you for working this. Sorry but is there any update?

We apologize for the delay in responses lately. We are in process of making some changes to our workflow in how we handle support requests. The good news is that we are starting to get back on track of having a 48 hour response time and we would like to start cleaning up anything old. With that being said, just wanted to check in with you to see if you have made any progress or changes to your project since support has last reached out.

Thank you for your support. Although the root cause of this issue remains unclear, the phenomenon is no longer occurring, so we can leave it as pending for now. That said, there are three other matters below that—while I appreciate your ongoing support—have not yet been resolved, so I’d really appreciate it if you could investigate them as a priority. https://discord.com/channels/1211482211119796234/1422558461073293413 https://discord.com/channels/1211482211119796234/1422037986928758804 https://discord.com/channels/1211482211119796234/1418151356413513788