I provide my assistant a forwardingPhoneNumber an instruction in the prompt to "to transfer the call to a live person, use the transferCall function." I provide my assistant config via a server-url configured on the phone number. I see the webhooks where my server is providing my assistant config successfully - but the system is forwarding the call almost immediately after receiving the config. Can you please help me figure out what I might be doing wrong?

Hey! To help track down this issue, could you share: - The call ID This would really help us figure out what went wrong!

yup, it's "b15ecae3-3600-4e6e-ab2a-bc2ec904b80d" @Shubham Bajaj

Hey Blehh, We aren't able to locate that call ID, do you have one that is within the last 30 days? Thank you for your patience while we resolve this

Here's another one from just now:

76709165-e3ef-497b-be27-fd74e2713bd7

It might be relevant that the forwarding number is another vapi number with a static assistant assigned via the ui. I had tested the assistant config successfully with a NOT vapi forwarding number in the past. In the webhook logs I see a successful assistant request/response immediately followed by a status update that the call is being forwarded. I don't see a call log for the forwarded call, but then I do see a call log for the forwarded-to bot.

Your current response has all the assistant configuration properties directly at the root level of the JSON, rather than nested inside an assistant property. Based on the AssistantRequestMessageResponse class definition, the response should have a specific format. The correct structure should be:

{
  "assistant": {
    "voice": {...},
    "model": {...},
    "recordingEnabled": true,
    ...
  }
}

Give it a try and let me know how it goes for you

thanks @Shubham Bajaj that fixed it! i'm surprised that vapi processed my response. it looks like vapi still read my forwardingPhoneNumber for the forwarding, but i'm not really seeing which schema that would've matched 🤔

> it looks like vapi still read my forwardingPhoneNumber for the forwarding, but i'm not really seeing which schema that would've matched @blehh could you share the call ID so I could take a look?

yeah this was the last one before i changed my server response schema:

06f29089-1c9a-4ddd-a57c-05c9d566f183

I just looked into the call logs for the shared call ID. You are still returning the wrong response format for the assistant request. That's why it's going to the forwarding phone number. So I suggest you look at the above shared format and return the assistant correctly according to it, and then it will work as you are expecting it out to work.