When I speak to my agent via browser using "talk with assistant", my webhook triggers and an end of call report is correctly sent, yet when I generate an outbound call to my handset via a make.com scenario, no webhook is triggered at the end of the call and no information is sent.

@bmbkny I'm glad to hear that your webhook triggers correctly when using the "talk with assistant" feature. However, it seems there might be an issue with the webhook not being triggered for outbound calls made through make.com scenarios. Here are a few things you might want to check to troubleshoot this issue: 1. **Webhook Configuration**: Ensure that the webhook is correctly configured in your make.com scenario to trigger on outbound call events. 2. **Event Subscription**: Verify that you have subscribed to the correct events for outbound calls in your VAPI settings. 3. **Network Issues**: Check if there are any network issues that might be preventing the webhook from being called. 4. **Make.com Scenario Settings**: Review the settings of your make.com scenario to ensure that it is set up to trigger the webhook upon completion of an outbound call. 5. **Logs**: Check the logs on both the VAPI platform and make.com for any errors or messages that could indicate what might be going wrong. If you've already checked these and the issue persists, it might be helpful to look at the specific configurations of your setup. If you need further assistance, please provide more details or ask support for more info on this.

when I add the webhook url at the ORG level, it triggers at the end of an outbound call, but since there are no choices for reporting, it triggers without sending information. I believe the issue is related to Vapi not triggering a URL at the end of a phone call in the Assistant level settings specifically when engaging with the system through a phone service.

@bmbkny It sounds like the webhook at the ORG level is functioning, but it's not sending the detailed information you need. This could be due to the way the webhook is set up at the ORG level, which might not include the detailed reporting options available at the Assistant level. Here's what you can do to address this issue: 1. **Assistant Level Webhook**: Double-check that the webhook URL is correctly added to the Assistant level settings and that it is configured to trigger at the end of a phone call. 2. **Event Configuration**: Ensure that the events you want to report on are properly configured in the Assistant settings to send the necessary data to the webhook. 3. **Payload Format**: Verify the format of the data payload that Vapi is expected to send at the end of the call. Make sure that the webhook is set up to handle this format and extract the required information. 4. **Documentation**: Review Vapi's documentation to confirm if there are any additional settings or parameters that need to be configured for the Assistant level webhook to trigger correctly with the full information. 5. **Support**: If the issue persists and you're unable to resolve it with the available settings, it may be necessary to reach out to Vapi support for further assistance. If you need more detailed help with the webhook configuration or if there's anything specific you'd like me to assist you with, please let me know!

@Vapi I've ensured th configuration is correct, the webhook url is configured and I'm still having the same issue.

@bmbkny Since you've confirmed that the configuration is correct and the issue persists, it seems like there might be a more complex problem at hand, possibly a bug or a limitation within the Vapi system when it comes to triggering webhooks with full information at the end of a phone call at the Assistant level. At this point, the best course of action would be to reach out to Vapi support for a more in-depth investigation. They would have the necessary tools and access to look into the system's behavior and provide a resolution. Please reach out to Vapi support with the following information: - A detailed description of the issue. - The steps you've taken to configure the webhook. - Any relevant logs or error messages. - The expected behavior versus the actual behavior you're observing. The support team should be able to guide you through the process of diagnosing and fixing the issue. If there's anything else I can do to assist you, please let me know. Otherwise, if your query is resolved for now, I can go ahead and close this support ticket for you.

@User Can you help with the issue I'm having please?

@bmbkny can you share the call id?