Call ID from the test call: 0199cf53-0b9c-7008-a139-e3122ccc04e6 Detailed description of what happened : In a connected make scenario, web hook is receiving type as "status-update" even though i have selected only "end-of-call report" in server messages. Expected behavior vs. actual behavior : it shoud send end of call-report but how come it is generating status update in webhook post call/ Screen recording (for web-based calls showing the issue): screen shot attached https://cdn.discordapp.com/attachments/1426439612552712313/1426439612838182932/620F3667-8B19-4127-9A9C-DA79DC402462.png?ex=68eb3ae9&is=68e9e969&hm=6a048580a470b27185d48782b989b6fdf49d5ed981f09566d5e8fa06f80e467f& https://cdn.discordapp.com/attachments/1426439612552712313/1426439613580443759/3857DDD1-CAED-41D3-B654-E49AA0C69F1E.png?ex=68eb3ae9&is=68e9e969&hm=c61028ff6e7dc0b568f40862e373df0bbfbf22319353b4b2fd65aba9dd3800c0&

I can help you check why your Make webhook is receiving status-update events even though only end-of-call-report is enabled. This usually happens when the SDK or client still pushes default message types before the call fully ends. I’ll help you verify if these are triggered from the client session or the server-side listener. Could you confirm if the call was made from the Vapi dashboard or via a custom client setup? @N2N

In your assistant configuration, it looks like there are more serverMessages than just the end-of-call report despite the screenshot you sent of your dashboard:

"serverMessages": [
        "end-of-call-report",
        "conversation-update",
        "speech-update",
        "status-update",
        "user-interrupted"
      ],

Please double check your assistant configuration from the API to ensure the appropriate serverMessages are configured with your assistant