Setting Up E911 Emergency Address on Twilio
A physical address the FCC requires be on file for any number capable of making or receiving calls, so a 911 dispatcher knows where to send help if it's ever used for an emergency call.
Why it's required
FCC rules require any interconnected VoIP number (which is what a Twilio number is) to have a registered emergency address, so 911 services can locate the caller the same way they can for a traditional landline. This applies even if you never plan to actually use the number for voice calls.
The penalty for skipping it
Twilio charges $75 per emergency call placed from a number with no emergency address on file, on top of whatever actually happens on the call. It costs nothing to add one — there's no reason to leave this unset.
Adding it via Linxi Settings (recommended)
Linxi Settings has its own Emergency Address section. Enter your address once and Linxi handles the underlying Twilio API calls for you — no need to touch the Twilio Console at all.
Adding it manually (if you're scripting your own setup)
If you're provisioning numbers outside Linxi, or the console UI isn't cooperating, the Node.js Twilio SDK can assign an existing Address SID directly:
What address to use
Must be a real, physical street address — not a PO Box. It doesn't need to be your business's official registered address; it just needs to be somewhere a first responder could actually be dispatched to.
Reusing the same address for multiple numbers
Once you've created an Address resource on Twilio (it gets its own AD… SID), you can assign that same Address SID to as many numbers as you own at that location — no need to re-enter the address every time you add a new number.
