You’re running into a real limitation in how VAPI handles transfers. Fallback plans are evaluated before dynamic destinations resolve, which is why it breaks when combined. A clean workaround is to keep your dynamic number via transfer destination request, but handle fallback outside VAPI. For example, use Twilio status callbacks or a post transfer webhook to detect no answer and reroute. This way you keep dynamic routing and still control failover reliably. Quick question, how are you currently detecting no answer? Are you using Twilio call status events or relying only on the VAPI flow? @Rojan