Guidelines

United States (US)

Locale Summary
Locale name	United States
ISO code The International Organization for Standardization two character representation for the given locale.	US
Region	North America
Dialing code The dialing prefix used to establish a call or send an SMS from one locale to the given locale.	+1

Guidelines
Portable Numbers	Mobile numbers Geographic (local) numbers Non-geographic (national) numbers Toll-free numbers VoIP numbers
Restrictions	Most numbers are portable. In rare cases, Twilio may not have geographic coverage for that number and won’t be able to port it. Most mobile operators require account numbers and PINs to port; some providers also require account PINs to port out. Before porting check with your current provider whether a PIN is required and iclude it in your port request.
Required Information	Letter of Authorization (LOA) Name and address that matches the Customer Service Record (CSR) Copy of a phone bill dated within the last 30 days Current provider’s account number PIN, if required
Timeframe	Once you submit all required information, 2 - 4 weeks for standard ports (fewer than 50 numbers), barring rejections from your current service provider. For bulk ports (more than 50 numbers), 4 - 6 weeks, barring rejections from your current service provider.
Regulatory Bodies	The Federal Communications Commission (FCC)
Other Details	The most common reason for a rejected port is incorrect name and/or address information. To ensure you have the correct information, ask your current service provider for the address and name on your Customer Service Record (CSR).
How To Submit	Submit your request directly via the Twilio Console. The maximum amount of numbers per port is 1000.

For the benefit of all our customers, these guidelines are provided to help you comply with applicable requirements and to help ensure Twilio's platform remains compliant with global telecommunications ecosystem requirements. These guidelines represent our current understanding of common compliance requirements generally applicable to Twilio and its customers, and do not constitute legal advice. By posting these guidelines, Twilio makes no assurances regarding the legal compliance of your application built using our APIs. You are expected to understand and abide by all compliance obligations applicable to your specific application. You should check these pages regularly for updates as telecommunications ecosystem requirements continue to evolve and change, and the information below may be updated or changed without notice.