VAPI•3w ago

Transfer only (skip AI)

Does this feature work from the documentation? Transfer Only (skip AI)

I've tried to skip the phone call and transfer to another phone number, but it throws an unknown error on the call. The error only occurs when I add the

destination

destination

destination

destination config to the server response.

I see in the

status-update

status-update

status-update

status-update webhook that the call's ended reason is

assistant-request-returned-forwarding-phone-number

assistant-request-returned-forwarding-phone-number

assistant-request-returned-forwarding-phone-number

assistant-request-returned-forwarding-phone-number, then the call gets dropped without transferring.

---

Call IDs:

019adb1a-c43c-7dde-9aca-9f07179c9fd3
019adb1a-7ec5-7113-b818-3c858dc13e7a
019adb18-e6bf-7442-9116-bd7bc00bf50b
019adb1f-8523-7dde-9ad0-6782320365a9

---

Example assistant request webhook response:

const disabledResponse: Vapi.ServerMessageResponseAssistantRequest = {
  assistant: {
    name: "Skip AI",
    firstMessage: "Hey, hey, hey. I'm transferring your call now. Please stay on the line.",
    firstMessageMode: "assistant-speaks-first",
    model: {
      provider: "openai",
      model: "gpt-4.1",
    },
    voice: {
      provider: "vapi",
      voiceId: "Elliot",
    },
  },
  destination: {
    type: "number",
    number: disabledPhoneNumber,
    message: "Connecting you to the front office.",
  },
};

const disabledResponse: Vapi.ServerMessageResponseAssistantRequest = {
  assistant: {
    name: "Skip AI",
    firstMessage: "Hey, hey, hey. I'm transferring your call now. Please stay on the line.",
    firstMessageMode: "assistant-speaks-first",
    model: {
      provider: "openai",
      model: "gpt-4.1",
    },
    voice: {
      provider: "vapi",
      voiceId: "Elliot",
    },
  },
  destination: {
    type: "number",
    number: disabledPhoneNumber,
    message: "Connecting you to the front office.",
  },
};

const disabledResponse: Vapi.ServerMessageResponseAssistantRequest = {
  assistant: {
    name: "Skip AI",
    firstMessage: "Hey, hey, hey. I'm transferring your call now. Please stay on the line.",
    firstMessageMode: "assistant-speaks-first",
    model: {
      provider: "openai",
      model: "gpt-4.1",
    },
    voice: {
      provider: "vapi",
      voiceId: "Elliot",
    },
  },
  destination: {
    type: "number",
    number: disabledPhoneNumber,
    message: "Connecting you to the front office.",
  },
};

const disabledResponse: Vapi.ServerMessageResponseAssistantRequest = {
  assistant: {
    name: "Skip AI",
    firstMessage: "Hey, hey, hey. I'm transferring your call now. Please stay on the line.",
    firstMessageMode: "assistant-speaks-first",
    model: {
      provider: "openai",
      model: "gpt-4.1",
    },
    voice: {
      provider: "vapi",
      voiceId: "Elliot",
    },
  },
  destination: {
    type: "number",
    number: disabledPhoneNumber,
    message: "Connecting you to the front office.",
  },
};

Server events | Vapi

Learn about different events that can be sent to a Server URL.

Vapi Support BotAPP•12/1/25, 6:31 PM

To use "Transfer only (skip AI)" correctly, your response should include only the

destination

destination

object and use the phoneNumberphoneNumber property (not numbernumber). Remove the assistantassistant object entirely. Hereâs the correct format:

const transferOnlyResponse = {
  destination: {
    type: "number",
    phoneNumber: disabledPhoneNumber, // Must include country code
    message: "Connecting you to the front office.",
  },
};

const transferOnlyResponse = {
  destination: {
    type: "number",
    phoneNumber: disabledPhoneNumber, // Must include country code
    message: "Connecting you to the front office.",
  },
};

This should resolve the error and allow the transfer to work as intended. For reference, see the documentation: https://docs.vapi.ai/server-url/events#transfer-only-skip-ai.

Source:

Server URL Events Transfer Only (skip AI)

â¤µï¸ Mention @Vapi Support Bot for follow-ups ð¥

Lltd-scarlet To use "Transfer only (skip AI)" correctly, your response should include **only*...

recent-tealOP•12/1/25, 6:35 PM

The phone number does include a country code. Also, phoneNumberphoneNumber doesn't appear to be a valid property on the destination object.

recent-tealOP•12/1/25, 6:37 PM

I added a base assistant config to see if that resolved issue, but it did not. The assistant config actually works, but when I add a destination object I receive an error.

spotty-amber•12/1/25, 9:21 PM

It looks like the forwarding is failing before the destination handoff is completed.
Are you sending the assistant response from a synchronous server or from a delayed/async process?
Sometimes if the timing is off, VAPI drops the call instead of transferring.
If you want, DM me the full server response and Iâll help you pinpoint the issue.

Sspotty-amber It looks like the forwarding is failing before the destination handoff is comple...

recent-tealOP•12/2/25, 1:18 PM

That is basically the full response. I'm using an Express app, and all my other endpoints work when sending responses back, even an assistant. It's when I add the

destination

destination

to the ServerMessageResponseAssistantRequest object--that's when it fails.

Essentially this is the response broken down (the disabledAssistantResponsedisabledAssistantResponse object as above). If I remove the

destination

destination

field, I get the expected "Hey, hey, hey..." message from the webhook/assistant. I'm following Vapi's Node example (with some modifications).

const disabledAssistantResponse = await assistantRequestHandler(payload) 
return res.status(200).json(disabledAssistantResponse);

const disabledAssistantResponse = await assistantRequestHandler(payload) 
return res.status(200).json(disabledAssistantResponse);

GitHub

GitHub - VapiAI/example-server-javascript-node

Contribute to VapiAI/example-server-javascript-node development by creating an account on GitHub.

KyleAPP•12/3/25, 3:01 PM

Hi ronnypg,

It seems like the issue is related to the incorrect use of the

destination

destination

object in your response for the "Transfer only (skip AI)" feature. To successfully transfer a call without involving the assistant, your server response should only include the

destination

destination

object. Here's the corrected format:

const transferOnlyResponse = {
  destination: {
    type: "number",
    number: disabledPhoneNumber, // Ensure it includes the country code in E.164 format
    message: "Connecting you to the front office.",
  },
};

const transferOnlyResponse = {
  destination: {
    type: "number",
    number: disabledPhoneNumber, // Ensure it includes the country code in E.164 format
    message: "Connecting you to the front office.",
  },
};

Remove the assistantassistant object entirely from the response. The phoneNumberphoneNumber property you mentioned should indeed be numbernumber, according to Vapi's configuration requirements.

Ensure your server sends this response asynchronously within the required time frame to avoid call drops due to timing issues. If the call still gets dropped, verify that the disabledPhoneNumberdisabledPhoneNumber is correct and includes the country code.

For further details, you can refer to the Transfer Only (skip AI) documentation.

Server events | Vapi

Learn about different events that can be sent to a Server URL.

Ccomprehensive-tomato Hi ronnypg, It seems like the issue is related to the incorrect use of the `des...

recent-tealOP•12/3/25, 10:40 PM

Thank you for your response. Yes, that is exactly what I'm trying.

I've copied your transferOnlyResponse and followed the documentation. When I call the number, I get a "Unknown error occurred. Contact support at Vapi." message.

For testing I'm only returning a destination. I'm not fetching any data or making a delayed response.

const transferOnlyResponse = {
  destination: {
    type: "number",
    number: <my_own_valid_number>, // With a valid E.164 number
    message: "Connecting you to the front office.",
  },
};

const transferOnlyResponse = {
  destination: {
    type: "number",
    number: <my_own_valid_number>, // With a valid E.164 number
    message: "Connecting you to the front office.",
  },
};

----

Below are call IDs that don't really have any context data in the dashboard, and they both have a call ended reason of Call.in progress.sip completed callCall.in progress.sip completed call

Call IDs:

019ae648-d1b1-7aa9-8f61-9a944e303741
019ae648-6b1e-733c-98dc-b45ccefc8f97
019ae64e-71a0-7aa1-9009-1e815f8fd8b1

Ccomprehensive-tomato Hi ronnypg, It seems like the issue is related to the incorrect use of the `des...

recent-tealOP•12/3/25, 10:41 PM

What's strange is that I can use the same exact disabledPhoneNumberdisabledPhoneNumber and use the transferCalltransferCall tool to transfer a caller to that number.

Ccomprehensive-tomato Hi ronnypg, It seems like the issue is related to the incorrect use of the `des...

recent-tealOP•12/4/25, 1:17 PM

Sorry, maybe I'm not seeing something, but here's what my responses look like, which is well under the 7.5s7.5s limitation.

I've even called the number directly, and it works.

The Postman screenshot is just a representation of what I'm sending back on a live phone call and assistant-request webhook request.

---

Call ID:

019ae981-38e2-755f-949e-a77c3542b9d5

recent-tealOP•12/15/25, 9:37 PM

@Vapi @Duckie As you can see from above, I'm only returning a destination and it's within the time limitation, but I still receive an error when I try to call.

Vapi Support BotAPP•12/15/25, 9:38 PM

Try this next: Double-check your assistant configuration to ensure you are not including any serverMessagesserverMessages like "phone-call-control""phone-call-control" and that phoneCallProviderBypassEnabledphoneCallProviderBypassEnabled is set to falsefalse. Your response should look like:

{
  "destination": {
    "type": "number",
    "number": "+12623728081",
    "message": "Connecting you to the front office."
  }
}

{
  "destination": {
    "type": "number",
    "number": "+12623728081",
    "message": "Connecting you to the front office."
  }
}

If the issue persists, review your telephony provider logs for transfer errors, as provider-side issues can also cause immediate call drops.
See: Vapi transfer troubleshooting guide

Source:

Debug call forwarding drops

Lltd-scarlet **Try this next:** Double-check your assistant configuration to ensure you are n...

recent-tealOP•12/15/25, 10:14 PM

I have no assistant configuration, so there won't be a phone-call-controlphone-call-control server message or phoneCallProviderBypassEnabledphoneCallProviderBypassEnabled setting.

I'm testing with transferring from a Vapi number to a different Vapi number. Is that possibly not allowed?

recent-tealOP•12/16/25, 5:00 PM

@Duckie

Vapi Support BotAPP•12/16/25, 5:01 PM

Based on the documentation, cross-provider transfers may have compatibility issues, and it is not explicitly stated whether transferring from one Vapi number to another Vapi number is supported. If your response format matches the example below and the issue persists, it may be a platform limitation:

{
  "destination": {
    "type": "number",
    "number": "+12623728081",
    "message": "Connecting you to the front office."
  }
}

{
  "destination": {
    "type": "number",
    "number": "+12623728081",
    "message": "Connecting you to the front office."
  }
}

If you continue to experience call drops, please contact Vapi support with your call IDs, as this scenario may not be fully supported or may require further investigation.
See: Vapi transfer troubleshooting guide

Source:

Debug call forwarding drops

recent-tealOP•12/16/25, 10:31 PM

@Vapi Any suggestions?

Call IDs:

019b2922-8e20-755f-8e3c-74cb71667a99
019b291e-d7c9-7446-bd89-b64b6e5388e3

recent-tealOP•12/17/25, 8:53 PM

If it's helpful, I'm also using the @vapi-ai/server-sdk@vapi-ai/server-sdk

Transfer only (skip AI)

Similar Threads

Similar Threads

Similar Threads