Jacob
05/09/2025, 3:01 PMend-of-call-report webhook is no longer firing for any of our calls, starting on May 3. We’ve confirmed that:
- The Assistant is correctly configured with server.url and includes end-of-call-report in server.messages
- The phone number points to the correct assistant and version (production)
- We’ve removed any problematic headers
- The Make.com webhook is working fine (we tested it via Postman and direct trigger)
- No Server Interactions show up in recent Call Logs, even though they did before May 3
This seems like a regression after the early-May update.
Thanks!Vapi Support Bot
05/09/2025, 3:01 PMend-of-call-report webhook is for your workflow, especially given the change in behavior since May 3. Your confirmation of the configuration and successful webhook testing is very helpful context. While I don't have additional information to resolve this specific issue right now, your thorough description will be valuable for further investigation.Vapi Support Bot
05/09/2025, 3:01 PMend-of-call-report webhook is for your workflow, especially given the change in behavior since May 3. Your confirmation of the configuration and successful webhook testing is very helpful context. While I don't have additional information to resolve this specific issue right now, your thorough description will be valuable for further investigation.Kings_big💫
05/09/2025, 4:07 PMJacob
05/09/2025, 4:13 PMKings_big💫
05/09/2025, 5:30 PMJacob
05/10/2025, 5:35 AMVapi
05/11/2025, 1:14 AMlogs
🔵 15:24:12:603 Sending End of Call Report...
🔵 15:24:12:603 No serverUrl found for message type: end-of-call-report. Skipping...
🔵 15:24:12:603 Sent End of Call Report
You are using a transient assistant, and the server URL is not assigned to it. Because of this, you are not getting the end-of-call reportJacob
05/11/2025, 6:29 AMJacob
05/11/2025, 11:05 AMJacob
05/11/2025, 2:22 PMVapi
05/14/2025, 9:45 PM