From my experience, what you’re trying to do isn’t possible with VAPI + Twilio as it currently stands. VAPI doesn’t expose the parent call’s SID or metadata, so you can’t pass the customer’s number as the caller ID on a transfer. All blind or SIP transfer attempts hit the same limitation. A possible workaround would be to manage the entire call flow within Twilio directly using Twilio Studio or a custom Twilio Function so you retain the call SID and can manipulate caller ID and routing. Outside of that, VAPI’s architecture simply doesn’t allow this. @RDOG