UNITED STATES (US)
|Country name||United States|
Short codes can only message users on carriers within the countries in which they are provisioned. Although Twilio can provision short codes in multiple countries, if your customers are not located in the USA, you should not obtain a US short code.
Short codes require express consent from end users before an SMS can be sent; if you cannot obtain consent, you should not use a short code.
Twilio and/or the carriers will not support certain types of campaigns, including:
The following use cases are allowed. However, since the carriers impose additional requirements and scrutiny, they may take longer than usual to provision.
Toll-free numbers and 10DLC A2P are the best alternatives.
The Short Code process is separated into two primary steps, each with their own timelines.
Expect delays on any applications submitted from mid December through early January, as the wireless carriers have an annual provisioning freeze during this time.
Multiple entities determine what is or is not permitted on a given short code.
Click to see SMS pricing, including for short codes.
Once approved, you must configure your short code to respond to the mandatory compliance keywords HELP and STOP and implement proper blacklist functionality for STOP requests. You can either build this functionality yourself or leverage Twilio’s Advanced Opt Out feature.
In addition, you should regularly process your carrier’s reassigned and deactivated phone number lists to ensure messages aren’t sent to users who have not opted in to receive them.
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.