Lots of people have been asking so I hope this helps 🙂 Heads up if you're running VAPI in production. Middle-tier pattern that saved us yesterday. Yesterday VAPI was down ~3h 30m (8:11 to ~11:30 AM MST). If your Twilio number points directly at VAPI's inbound URL, your callers don't get through. Here's the pattern we had in place and you should too:

Twilio number  →  your own endpoint  →  https://api.vapi.ai/twilio/inbound_call
Twilio status  →  your own endpoint  →  https://api.vapi.ai/twilio/status

Your endpoint does three things on every inbound: 1. Forwards Twilio's payload straight through to VAPI's

/twilio/inbound_call

(no transformation) 2. Watches for VAPI accepting the call (websocket open or a 2xx response) 3. If VAPI didn't accept, fall back. Two options: - Return TwiML that forwards to a phone number you've stored for that tenant (look up in a DB of clients you have by

To

/

From

, both are in Twilio's payload) - Hand off to a different AI voice provider's inbound endpoint Same wrapper on the status callback URL: Twilio fires status events at your endpoint, which forwards to

https://api.vapi.ai/twilio/status

. Bonus, you now get to log call lifecycle in your own stack as it happens. Why this works: - You own the routing decision, so a provider outage stops being a customer-facing event - You can flip vendors per-tenant with a config flag, no redeploy If you don't have infra for the middle tier, a tiny Cloudflare Worker, an n8n workflow, or a Make scenario all handle this in under 100 lines. The per-tenant fallback phone number is the easiest first step. Failover to another AI voice provider is more work but the same shape. Ping me if you have questions and make sure to have Claude or Codex help you do this. It's more than capable of walking you through. Here's a prompt to get you started, paste it into a fresh Claude or Codex session - see in thread i attached prompt.

You are giving me an idea that we should do some community sharing style office hours. So many of you have alot of knowledge to share and would be cool to bring folks together if we can figure out good timing. Let me know if that's interesting to you

happy to write it 🙂

ooooo

i have been usign vappi for 2+ years now. 😛

I love this - let me see if we already have a mechanism for community contributions to our blog. I also will be hosting livestreams and if you are open perhaps you could be a guest sometime!

message me anytime happy to help!!

yay! I will definitely do that - for now going to ask internally about the blog idea.

tell em Titus sent ya 😛

banger post 🔥

Thanks!