Webhook only works with completed calls – no updat...
# support
j
Description: Currently, our webhook integration with VAPI only receives events for successfully completed calls. However, it does not send any
status-update
or
end-of-call-report
when a call ends with other outcomes such as: * Busy * Failed * No-answer * Any other non-completed status This results in incomplete tracking of call states on our side. Actual Result: Webhook is triggered only for completed calls. No events are sent for failed or incomplete call attempts. Expected Result: Webhook should send
status-update
or
end-of-call-report
events for all call outcomes (busy, failed, no-answer, etc.), not only for successfully completed calls.
c
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
v
To improve call outcome tracking, ensure your assistant is configured to send
status-update
events for all call states. Add
"status-update"
to your assistant's
serverMessages
array:
Copy code
js
const assistantConfig = {
  // ...
  serverMessages: ["end-of-call-report", "status-update"]
};
This will enable your webhook endpoint to receive updates for various call outcomes, not just completed calls. For more details, see the [Vapi webhook documentation](https://docs.vapi.ai/server-url/events). Source: - [Server events](https://docs.vapi.ai/server-url/events)
j
Well, I do receive ["end-of-call-report", "status-update"] when the call is completed, but I don’t understand why I don’t receive them when the call status is busy or twilio-failed.
m
Hey, this might help, how i receive them is by only having "end-of-call-report" and "status-update" selected in the agent, everything else deselected, then it works, at least for me
j
@Manuel thanks! it solves my problem, it works again!
c
Glad you were able to get this resolved. If anything else comes up or you need further assistance, we’re here to help.
3 Views