Porting Checklist: Twilio
Twilio is a developer platform, and porting a number out of Twilio is heavier than consumer wireless porting. There's no "Port Out" button in the Twilio Console — the receiving carrier (Phound) submits the port request to Twilio on your behalf, and you supply a signed Letter of Authorization (LOA) plus a recent bill.
This guide walks through exactly what to gather and the Twilio email address you'll need.
What You Need from Twilio
- Your Twilio Account SID (found at console.twilio.com)
- The service address Twilio has on file (you'll need to email Twilio to confirm this)
- A signed Letter of Authorization (LOA) with matching info
- A recent Twilio invoice/bill (within the last 30 days)
- The phone number(s) to be ported
Step 1: Get Your Account SID
- Log in to the Twilio Console.
- Your Account SID appears on the dashboard home page (the main account identifier starting with
AC...). - Copy it — Phound will need this.
Step 2: Email Twilio to Confirm the Service Address
Twilio's porting team uses a specific service address on file. You need to confirm what's on record before filling out the LOA.
Email porting@twilio.com with:
- Your Account SID
- The phone numbers you want to port out
- A request like: "Please confirm the service address on file for these numbers so I can complete the LOA for porting."
Twilio typically responds within a business day.
Step 3: Download a Recent Invoice
- Go to Billing in the Twilio Console.
- Download your most recent invoice (within the last 30 days).
- The invoice must show the account holder name, service address, and the numbers being ported.
Warning: If your invoice is older than 30 days, the gaining carrier will likely reject the port. Pay any outstanding balance first, then generate a fresh invoice.
Step 4: Complete the Letter of Authorization (LOA)
Phound will provide an LOA template. The LOA must include:
- Authorized user's full legal name — must match Twilio's Customer Service Record (CSR) exactly
- Account SID
- Service address (from Step 2 — must match what Twilio has on file)
- Phone numbers being ported
- Date and signature of the authorized user
Twilio provides its own LOA Template as a reference.
Tip: The #1 rejection reason for Twilio ports is mismatched name or service address. Match Twilio's records character-for-character, including case, punctuation, and suffixes like "LLC" or "Inc."
Step 5: Keep Your Account Funded and Numbers Active
- Twilio account must have no outstanding balance at port time.
- The numbers must be active in Twilio (not released, ported, or suspended).
- Do NOT release/delete the number from the Twilio Console before the port completes — that cancels the port and may lose the number.
Step 6: Submit to Phound
- Open Phound → Settings > Numbers > Port a Number.
- Provide:
- Twilio Account SID
- Phone number(s)
- Signed LOA
- Recent Twilio invoice
- Phound submits the port request to Twilio.
Track in Check Your Porting Status.
Timeline
Twilio ports take longer than consumer ports:
- Typical: ~15 days total (~10 days setup + ~5 days migration)
- Toll-free numbers: Often longer
- International numbers: Significantly longer, varies by country
Common Twilio Rejection Reasons
Twilio's own porting docs list these as the top rejection causes:
- Authorized user name mismatch — name on LOA doesn't match Twilio's CSR
- Service address / ZIP mismatch
- Port initiator not an authorized user on the losing Twilio account
- Number inactive — already released, ported, or suspended
- Number already pending another port request
- Outstanding Twilio balance
- Invoice too old (over 30 days)
See Twilio's Reducing Port Rejections for their guidance.
Twilio Support
- Port-out questions: porting@twilio.com (dedicated porting team)
- General Twilio support: twilio.com/help
Still need help?
If you couldn't find what you were looking for, our support team is ready to assist. Contact Phound Support and we'll get back to you as soon as possible.