THIS IS JUST A REPOST @mubashshir.ansari SAME CONCERN. Hello Vapi Support Team, I am using the dynamic call transfer feature for my assistant. My goal is: if a call is transferred to a destination number and that number is busy or does not answer, I want the assistant to automatically resume the conversation with the original caller, rather than ending the call. Currently, when I provide a destination and Vapi attempts the transfer, if the recipient does not answer or is busy, the call ends instead of returning to the assistant. I have not found any option in the dashboard or API documentation to change this behavior. I have also tried using warm-transfer-experimental with the fallbackPlan option, but in this case the calls are still getting cut rather than returning to the assistant for further conversation. Could you please advise if there is a way to: Detect transfer failure (busy/no answer) after providing a destination, and Automatically return the caller to the assistant so the conversation can continue? If this is not possible today, is there a recommended workaround or are there plans to support this functionality?

Currently, Vapi does not support automatically resuming the assistant conversation after a dynamic transfer fails (busy/no answer); the call will end by default. As a workaround, you can configure your webhook to detect transfer failures (e.g., via the

transfer-destination-request

event) and then programmatically trigger a new assistant call to the original caller if the transfer fails. Example logic:

js
if (transferFailed) {
  // Use Vapi API to start a new assistant call to the original caller
}

This approach does not "resume" the same call but allows you to reconnect the user to the assistant for further conversation. For more details, see the [dynamic call transfers guide](https://docs.vapi.ai/calls/call-dynamic-transfers). Source: - [Dynamic call transfers](https://docs.vapi.ai/calls/call-dynamic-transfers)

Is this something that you are considering to feature since without it, could cause repeat rate.

Hey! To help track down this issue, could you share: \- The call ID \- When exactly this happened (the timestamp) \- What response you expected to get \- What response you actually got instead This would really help us figure out what went wrong!