10DLC website requirements


As carriers evolve their 10DLC requirements , we are committed to helping keep your organization compliant. For new registrations, we have added fields to the Brand Registration page. An admin will need to input your website information for already registered clients.

Why does my organization need a URL to our website?

As malicious actors continue using the texting medium to send spam, carriers have instituted a manual verification level above The Campaign Registry. In an effort to reduce spam, carriers are ensuring that organizations have a place where a contact can opt into text messages knowingly, and can reference a privacy policy about how their information will be used. However, this does not mean that opt-in is required to send texts. Click here for more information.


Brand Registration

If your organization has already filled out the Brand Registration, your Account Owners will be prompted to input your organization's URL. Please link to your main site homepage. GetThru has created a prompt on the 10DLC Brand & Use Case Registration page for easy updating.


Use Case Registration 

For a Use Case to pass manual vetting, your website must include both a Contact Source URL and Privacy Policy page during use case registration.

Contact Source URL

Carriers require a valid URL, specific to the organization, that has a phone number input field and opt-in language. An example of this is shown at the end of this guide. This URL should take the person verifying the application directly to the phone number collection page. Carriers will verify that the phone number input field exists and shows the proper disclosures. 


To meet carrier requirements, the following language should be included on the page, preferably adjacent to the phone number input field: 

"By providing your phone number, you agree to receive text messages from this organization. Message and data rates may apply. Message frequency varies."

If your organization has a "Contact" page, that would be the best page to include the phone number and opt-in information. 


Privacy Policy

Carriers need to see a dedicated privacy policy page on the organization's website that discloses how the organization manages contacts' data. The privacy policy should be easily discoverable from your contact source URL, preferably linked in the footer of your website. 


There are two crucial aspects your privacy policy must cover. 

  • Your privacy policy must explicitly state that your organization does not share or sell any personal information without consent, except when legally required to do so. 
  • Your privacy policy must share information about how to opt out of communications.

The absence of either of these elements will result in the rejection of the use case. 


To share opt-out information with users, we recommend sharing the following language in your privacy policy:

"SMS Opt-Out: If you are receiving text messages from us and wish to stop receiving them, simply respond with either “STOP” or “UNSUBSCRIBE” to the number from which you received the message. Once we receive your message, you will no longer receive further text messages from us."

For best practices, it's recommended to craft a personalized privacy policy addressing the following key points:

  • The type of data you collect from your users.
  • How and why you are collecting the data.
  • Explicitly states you do not Share or Sell personal information.
  • How users can unsubscribe/opt-out from your organization.
  • Explain how you protect your user data.
  • Explain the update possibilities to your privacy policy.


It is recommended that you create a personalized privacy policy that pertains to your organization based on the points outlined above; however, if you need assistance crafting your organization's privacy policy, you can review some online resources that generate custom privacy policies (some are free and some may require a fee). Please check out our guide: Online Resources for Privacy Policies.


You can also reference GetThru's comprehensive privacy policy here: https://www.getthru.io/privacy-policy  


If your site doesn't include a contact source URL and/or privacy policy already, adding them is necessary to help your organization get approval through manual vetting. If a use case fails manual vetting, your site must be updated to fulfill the requirements, which will require restarting the manual vetting process.


Below, you can see an example of a page that shows phone number collection, an opt-in message, and a privacy policy linked in the footer:

Please write to support@getthru.io if you have any questions or difficulty adding your website!