Hi everyone, I wanted to understand why Vapi triggers a second call immediately after the first call, if the first call has decline.

Hi there, Thank you for your message. Our team is currently out of the office. We operate Monday through Friday, from 9:00 AM to 8:00 PM Pacific Standard Time (PST). We’ll get back to you as soon as possible during our normal business hours. If your message is urgent, please mark it accordingly or include “URGENT” in the subject line, and we’ll do our best to respond promptly. Warm regards, Vapi Customer Support Team

@Vapi Support Bot can you help out?

Hi Adham Sameh, If you're experiencing an issue where a second call is being triggered after the first call is declined, you might want to consider reviewing your call handling workflow. This could involve checking any configured callbacks or hooks that might be inadvertently triggering additional calls. Based on the setup with Vapi, ensure the call flow and any Twilio status callbacks are set correctly to avoid unintended actions. For example, you should verify any logic tied to the

participant-status

webhook, ensuring it correctly handles call statuses like "no-answer" or "busy" to prevent secondary actions unless explicitly desired. Additionally, reviewing the [Call End Reasons](https://docs.vapi.ai/calls/call-ended-reason) documentation could provide insights into why a call might behave unexpectedly and whether specific return codes are being handled or misinterpreted. If your workflow involves logic similar to the call transfer and conferencing setup outlined in the [Call Handling with Vapi and Twilio](https://docs.vapi.ai/calls/call-handling-with-vapi-and-twilio) document, confirm that the call references are not reused improperly or that unintended logic paths are not causing the second call trigger.