What you're doing works, but it's not officially documented as a supported pattern, This are the few things to note; On webhook override risk, VAPI sets the webhook during import, but there's no evidence it continuously re-syncs or overrides it afterward. That said, VAPI doesn't officially guarantee it won't touch it again. This is a real risk you'd be taking on. The recommended production approach for your exact use case (inbound = your server, outbound = VAPI) is actually to not import the number into VAPI at all, and instead use the "phone call provider bypass" pattern. VAPI has an example repo for this: your Twilio number points to your own webhook, and you selectively invoke VAPI only for outbound via create_call(). No number import needed. Happy to walk you through the setup if that'd help!