Title. Especially in the dashboard. I cannot find a button to end an ongoing call anywhere. Bizarre.

Hi there! 👋 I understand you're looking for a way to end an ongoing call from the Vapi dashboard. Unfortunately, I couldn't find information about a specific button in the dashboard to end calls. However, I can help with alternative ways to end calls in Vapi. According to the [documentation](https://docs.vapi.ai/quickstart/dashboard), there's currently a limitation where "Your assistant won't yet be able to hang-up the phone at the end of the call." This suggests that automatic call termination by the assistant has some limitations. Instead, you can end calls using these methods: 1. Use the

EndCall

function by setting

endCallFunctionEnabled

to true in your configuration 2. Implement idleMessages to trigger the endOfCall if the caller doesn't say anything 3. Programmatically end a call by sending an

end-call

message type within

ClientInboundMessage

The [API endpoints](https://docs.vapi.ai/api-reference/test-suites/test-suite-controller-create) might also be helpful, as there are endpoints for call management including: - `DELDelete Call Data`:

/api-reference/calls/delete

- `PATCHUpdate Call`:

/api-reference/calls/update

Is there anything else you'd like to know about managing calls in Vapi? Sources: - [Vapi Documentation](https://docs.vapi.ai/quickstart/dashboard) - [API Reference](https://docs.vapi.ai/api-reference/test-suites/test-suite-controller-create)

Top right.. same button that started the call https://cdn.discordapp.com/attachments/1359925931497492520/1359951150148747304/image.png?ex=67f958b4&is=67f80734&hm=ba843a3aede6bea361cb6552809afe4632ba2a32af60f3c67351dddb55afbfd8&

checking if this is resolved/solved for you?

No, I just end it in my twilio call menu

It's possible. You can just generate a new webhook URL in make, drop that into your Vapi integration settings, and then test a call. That’ll help confirm if the webhook is firing correctly and whether data is reaching Make. If it works, then it was likely still using the old URL under the hood.