We’re building voice agents for clients in Mexico who need customers to call a Mexican local number (or at least be able to dial from Mexico reliably) and talk to the Vapi agent. Right now it looks like Vapi primarily provides US numbers. Can callers in Mexico call a Vapi US DID and connect to the agent without issues (routing, carrier blocks, latency)? If yes, is there any recommended setup to maximize reliability for Mexico callers? If no / not ideal: what’s the best way to provide a Mexico number that forwards to Vapi? Do you support BYO number via Twilio/Telnyx (Mexico DID) and connect it to Vapi? If forwarding is required, do you recommend SIP trunking vs call forwarding? If you have a reference doc / example: could you share the step-by-step for: Mexico DID → Vapi agent (inbound) (including any webhook/SIP config, required credentials, and gotchas)? Goal: Our Mexico business owners want a public phone number customers can call, and the agent answers 24/7 in Spanish. Thanks!

Hi there, Thank you for your message. Our team is currently out of the office. We operate Monday through Friday, from 9:00 AM to 8:00 PM Pacific Standard Time (PST). We’ll get back to you as soon as possible during our normal business hours. If your message is urgent, please mark it accordingly or include “URGENT” in the subject line, and we’ll do our best to respond promptly. Warm regards, Vapi Customer Support Team

Mexico callers can dial a US Vapi DID, but it’s not ideal—mobile carriers may block or degrade calls, and latency can affect voice quality. Best practice is a local Mexico DID via Twilio or Telnyx → SIP trunk → Vapi inbound, which is more reliable than call forwarding. Vapi supports BYO numbers, and SIP is preferred for clean audio, DTMF, and faster agent response. Are you already using Twilio or Telnyx for MX numbers, or do you want a recommendation based on volume and budget? @AJ