When the call is finished with status

customer-did-not-answer

, We're receiving the webhook in 5 minutes exactly. The Calls examples: * 019b5106-0125-7666-b44f-bc13781c1b3c * 019b4be6-d2f5-7aaa-b2a0-4113fd451ee8 * 019b50fd-21e2-7113-b708-4b592e3d38b9 My configuration of the webhook is this:

serverMessages: ["end-of-call-report"],
        server: {
          url: "..."
        }

Thank you for sharing your webhook configuration and the observed 5-minute delay for the "end-of-call-report" when the call status is

customer-did-not-answer

. The documentation does not mention a fixed delay for this webhook event in such cases. Could you clarify if you have any custom timeout settings (such as

customerJoinTimeoutSeconds

) configured for your assistant or calls, or is everything set to default values? This will help determine if the delay is related to a specific configuration or a platform behavior. Sources: - [Server events documentation](https://docs.vapi.ai/server-url/events) - [Customer join timeout documentation](https://docs.vapi.ai/calls/customer-join-timeout)

No, I didn't defined this parameter (

customerJoinTimeoutSeconds

). The strange is that, when the customer declined the call (unjoin to the call), we receive exactly in 5 minutes the webhook.

Hi, Thank you for reporting this. The behavior you're seeing is expected based on the default configuration. How it works: When you initiate an outbound call and the customer doesn't join (answer), Vapi waits for a timeout period before ending the call and sending the end-of-call webhook. The default

customerJoinTimeoutSeconds

is 300 seconds (5 minutes) if not explicitly set. To reduce this timeout: You can set a shorter

customerJoinTimeoutSeconds

in your call configuration. For example, to timeout after 30 seconds of no answer:

{
  "customerJoinTimeoutSeconds": 30,
  ...
}

This will cause the call to end and trigger the webhook much sooner if the customer doesn't answer. If this isn't matching your expectations, could you share: 1. The Call ID 2. What timeout behavior you were expecting 3. Whether the customer actually answered the call This will help me investigate if there's something unexpected happening. Best, Vapi Support

Hello Sahil, But I think it's strange logic. Because when the client clicked the button on his phone "Hang Up", the webhook should be sent immediately.

It takes a little bit time to process everything Ivan.