VAPI•2mo ago

EOC triggers twice when call fails

Whenever a call ends with status "Customer Did Not Answer" or "Twilio Connection Failed", the EOC (End Of Call) event is triggered twice.

Example Call ID: 019a3a26-5a13-700f-aa5f-616950a8cef9

Could you please check why this happens?

Vapi Support BotAPP•11/5/25, 6:02 PM

Thanks for reporting this! To help investigate, could you confirm if you have any custom assistant hooks or multiple webhooks configured that might trigger EOC (End Of Call) events for the same call? This will help narrow down whether the duplicate events are coming from your configuration or the platform itself.

Sources:

⤵️ Mention @Vapi Support Bot for follow-ups 🐥

verbal-limeOP•11/5/25, 6:15 PM

this is how my EOC looks like, just one webohk connecnted

VapiAPP•11/10/25, 7:13 AM

Hey! To help track down this issue, could you share:

- When exactly this happened (the timestamp)

- What response you expected to get

- What response you actually got instead

This would really help us figure out what went wrong!

verbal-limeOP•11/10/25, 11:17 PM

Hell thank you for the response,

I unfortunaly have no exact timestamp anymore, its not even listed, i think this happens to Numbers with Twilio Connection Failed or Customer Did Not Answer, i thnik the Number blocked my Agents number its not even Ringing.

Im expecting to get only one EOC report - but currenlty it sometimes triggers twice, which is wierd, because it doesnt always Trigger Twice.

This currently happens the calls where there ist no Start time, if the start time Is Avilable, the EOC triggers once.

thank you for the Help

Best Reguards
Jakob

VapiAPP•11/12/25, 2:07 PM

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

verbal-limeOP•11/12/25, 6:59 PM

Hi Thank you very much appriciate it

EOC triggers twice when call fails

Similar Threads

Similar Threads

Similar Threads