Hi I have done my own testing and found that blind transfers drop on inbound calls (where parameter is not set) but work perfectly on outbound calls when I set phoneCallProviderBypassEnabled: false at creation time. I tested with the following call ID: 019b1d1a-7b67-7ee4-a3af-594c138f1b45 and it worked using the (-d "{"assistantId": "88624e8f-8328-4e4d-ad75-feffa4c7bb67", "phoneNumberId": "7dc15331-2a82-4c6e-b756-ad71c00a16f4", "customer": {"number": "+61xxxxxxxx"}, "phoneCallProviderBypassEnabled": false}") parameter in CMD Example working outbound call ID: 019b1d1a-7b67-7ee4-a3af-594c138f1b45 Example failing inbound call ID: 019b1d24-a7db-7443-8d80-da29bea8d249 (this was without the initial disable of the parameter) - done with twilio Since this is a Twilio number, I cannot set the flag myself on inbound as I have tried multiple times and received the error in CMD { "message": ["property phoneCallProviderBypassEnabled should not exist"], "error": "Bad Request", "statusCode": 400 }. Please set the phoneCallProviderBypassEnabled: false by default for all calls org-wide. Thank You

You cannot set

phoneCallProviderBypassEnabled: false

as a default for all inbound calls org-wide via the API or configuration. For Twilio inbound calls, this parameter is not accepted and will return an error if included. Actionable next step: Contact Vapi support with your call IDs and troubleshooting results, as recommended in the documentation, to escalate this limitation and request a solution for org-wide default handling. Reference: [Debug call forwarding drops documentation](https://docs.vapi.ai/phone-calling/in-call-control/transfer-calls/debug-forwarding-drops) Source: - [Debug call forwarding drops documentation](https://docs.vapi.ai/phone-calling/in-call-control/transfer-calls/debug-forwarding-drops)