|
Locale Summary |
|
|---|---|
|
Locale name |
United States |
|
ISO code |
US |
|
Region |
North America |
|
Guidelines |
|
|---|---|
|
Prerequisites |
|
|
Restrictions |
As an RCS for Business provider, Twilio connects businesses with carriers (AT&T, Verizon, T-Mobile) and Google, which manages RCS connectivity. To ensure a trusted ecosystem with high quality interactions, Twilio enforces partner rules and upholds the highest compliance standards. Content Restrictions: See the Forbidden Message Categories in the US. The following are the major categories:
In addition, Any use cases that violate Twilio's Acceptable Use Policy, Messaging Policy or Google’s Acceptable Use Policy are prohibited on Twilio's platform, regardless of sender type or destination. Note there are currently certain categories that Google does not allow, even though these categories have historically been supported by US carriers. The following use cases fall into this category:
|
|
Requirements |
1. RCS Sender: Create an RCS sender in the Twilio Console by following the steps here. Carriers verify the sender’s public details, such as display name and logo, to ensure authenticity. 2. Brand Verification: Brand and asset vetting is performed by a 3rd party, Aegis Mobile. This vetting is done on the brand assets to ensure that the information is correct. We collect all of this information during the onboarding process and will submit this on behalf of the brand however we do need the end brand to complete the Attestation Letter. Downloadable Template of the Attestation Letter Aegis will also be sending an email to the end brand verifying the brand details that will need to be completed. Until this new part is completed we are unable to proceed with any carrier onboardings. 3. Carrier-specific requirements: After you submit the sender, we will collect additional information to onboard your RCS sender(s) with major U.S. carriers The required information includes:
4. Compliance: Carriers in the US have indicated that they are seeking Short Code-level standards for onboarding, even though they have not yet established their own onboarding standards for this channel. We expect these standards to be developed in 2026. In the meantime, following the CTIA Short Code Handbook remains the best available industry documentation for Compliance.
The sender and the Business vertical must satisfy the CTIA guidelines for Opt-In, Privacy policy, SMS Terms of services. Opt In / Message Flow / Call to Action When sharing the consent flows for RCS, we expect a detailed explanation of how consent is being collected, including any links or screenshots of the opt-in flow that show the exact steps the consumer is taking.
When reviewing opt-in flows, we will check the following three categories:
Industry Standards for opt-ins for US Short Codes CTIA and the carriers have different requirements for the level of consent that is required for the type of messaging that is being sent. Twilio will work with you directly to ensure that you are gathering the proper level of consent and will guide you through the specific requirements and process. Privacy Policy and Terms of Service When onboarding, the Privacy Policy and Terms of Service are documents that are reviewed for specific language that the carriers are expecting to see to ensure that the message and data disclosures are properly shared with consumers. Privacy Policy In the Privacy Policy, Twilio looks to ensure that there is some language that is in the Privacy Policy that ensures that the Messaging Consent data is not being shared, sold, or bought. Below is an example of the language the carriers look for. “All the above categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties.” Terms of Service In the Terms of Service there are specific terms that we search for to make sure that the text messaging program is identified.
|
|
Timeframe |
The RCS onboarding process has two main steps, each with its own timeline. Step 1: Twilio Internal Review After you submit a sender in the Twilio Console, a Twilio RCS onboarding specialist will begin the review process. This initial step is designed to confirm that your submission aligns with all carrier and messaging compliance requirements. The specialist will reach out to you with their findings, highlighting any corrections needed and providing guidance on how to fix them. The overall timeline for this process is variable and depends entirely on the compliance of your initial submission and your responsiveness to any requested changes. We can only move to the next stage once the submission is fully compliant.
Step 2: Brand Vetting and Carrier Review Once your sender application passes Twilio's review, we submit it to our carrier and third-party vetting partners (such as Aegis or Google) in the US for approval. The final launch timeline can vary and may take longer depending on the use case and specific requirements. The best way to ensure a faster approval is to submit a fully CTIA compliant application, as the process can be delayed if carriers require additional information or clarification. Important Note: Please be aware that application timelines may be impacted by carrier network freezes or delays around major holidays.
|
|
Regulatory Bodies |
Compliance is a critical aspect of business messaging in the US. Several regulatory and industry bodies oversee messaging, and Twilio helps you adhere to their guidelines. Multiple entities determine what is or is not permitted on a given RCS sender.
Each carrier may approve or reject any use case on their network, even if all requirements are met |
|
Pricing |
Click to see pricing, including for RCS.
|
|
Other Options |
10DLCs (10-digit long codes), Toll-Free numbers and Short Codes are the best alternatives for messaging in the US. |
|
Next Steps |
Once your RCS sender is live. Add it to your Messaging Service and begin sending messages |
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.