Hi Vapi team, We’re currently experiencing a critical issue related to the event handling for calls in our system. We’ve detected that, for some calls, we are receiving the same event type end-of-call-report twice for a single call. This is causing severe problems on our end, as our internal logic is tightly coupled to the sequence and uniqueness of the events received from Vapi. After some investigation, the issue seems to be triggered when a call is quickly hung up while it's still ringing. In these cases, Vapi reports the event as twilio-reported-customer-misdialed. Request: Is it possible to ensure that in these scenarios, only a single end-of-call-report is sent, and always in the same order as the other events? This would greatly help us avoid duplicated processing and maintain a stable and predictable integration. Please let us know if you need any additional details to reproduce or investigate this behavior. call id: 01107c41-570e-4489-9109-ae01a834e8fe call id: a38dd047-3c76-46c1-a286-3f652c157838 Best regards, David https://cdn.discordapp.com/attachments/1392827941150527591/1392827941779542107/image.png?ex=6870f39a&is=686fa21a&hm=5ddab0a96eff575d122939b233ccd7f3e083360a7507588fcce019b4d01f3f38& https://cdn.discordapp.com/attachments/1392827941150527591/1392827942383652915/image.png?ex=6870f39a&is=686fa21a&hm=4f932b1f70ad829a087df6748250eaf8a99e627bc174ffd2cbf38a2642e0f91a&

Hey David, thanks for sharing your details. Our team will look into it and get back to you soon with an update. Lopping in @Shubham Bajaj

Thank you Praveen

Hey David Jurado, Thanks for reaching out! We're currently swamped with a bunch of tickets and it's taking us longer than usual to get back to everyone. I know waiting isn't fun, but we want to make sure we give your issue the attention it deserves rather than rushing through it. We'll circle back with you soon to get this sorted out.

thank you

Hey David Jurado, 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!

thank you

Hey David Jurado, 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!

Hello, thank you for your message. I know that the last week was hard, so don't worry — and much encouragement from our side. We hope to hear from you soon!

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

hello, we still need help with this ticket. Thank you

Hey David, the first one end of call report request timed out on your server, and when it retriggered second time, the artifact was empty—which then led to a 500-level error on your side. I'm checking with team about this.

Thank you. Why was the first event empty and the second one included an artifact?

We will check with the team and get back to you.

ok thank you