Okay since it doesn’t handle no-answer on dynamic transfers, so Twilio has to own that layer. Set a statusCallback on the transfer call (via your Twilio config) and listen for no-answer, busy, or failed events on your webhook. When that fires, use Twilio’s Call Update API to redirect the same live call to your fallback (or re-initiate via VAPI outbound if it already dropped). I’ve implemented this exact pattern before with VAPI + Twilio + dynamic routing, happy to help you wire it end-to-end. @Rojan