Date: January 16, 2025


Subject: 10-DLC Registration and TF Verification Requirements Effective Jan 2025

 


As carriers and upstream partners continue to enhance A2P messaging for 10-DLCs and TF messaging codes, the rules and requirements for verifications can fluctuate. Several new rules and requirements were put in place towards the end of 2024 that are very important to be aware of and include in future submissions.




Mobile Terms & Conditions / Privacy Policy URL

 

As always, a T&C/Privacy Policy page is required as part of the mandatory disclaimer language, and expectations for URL behavior and content have been clarified. 

  1. Effective January 2025, all 10-DLC and TF submissions require a URL T&C / Privacy Policy that is branded to the sender.
  2. The URL must be live and able to be opened in a browser. It cannot be a place holder. The URL must be able to open a real T&C / Privacy Policy page.
  3. The URL displayed in the verification submissions must be specific to the "sender," aka the business for whom the code is being verified. A "reseller's" mobile terms of service page will result in rejection. 
  4. The page must state clearly that "Mobile information will not be shared with third parties/affiliates for marketing/promotional purposes." If other data sharing is referenced, an exception should be included to state that "All the above categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties."
  5. The Terms of Service must have an SMS disclosure that includes the brand name, types of messages consumers can expect to receive, purchase is not required and message frequency disclosure, message and data rates may apply, privacy policy links, and opt-out and help instructions. 



See Related Article: How to I create a "Branded" Terms of Service Page for my client?



<< Back to Top >>



Sample Calls to Action (CTAs) 



For various reasons, it is preferable to use TEXT CTAs for all submissions. Initiation by the handset is the best form of express written consent. And text CTAs tend to avoid the high scrutiny and rejections commonly experienced with kiosk and webform CTAs. We strongly advise Text CTAs whenever possible. 


Effective January 2025, ALL TEXT, WEBFORM and KIOSK CTAs must...

  • Explicitly state the type of messages the consumer will receive. Displaying "Join Mobile Alerts" or "VIP Text Club" alone is insufficient. 
  • Display a complete SMS disclaimer and a live T&C/Privacy Policy URL branded to the sender. A "reseller's" Mobile Terms of Service page will no longer suffice. 
  • Display the sender's company name in the logo, and, or, SMS disclaimer language.



Text CTAs must also...

  • Display the same messaging code identified on the submission. Old CTAs displaying the sender's previous code will not be accepted. 
  • If present, display an SMS QR code that opens with the messaging code identified on the submission and the keyword displayed on the CTA.



Webform CTAs must also....

  • Include a live URL to the webform, where vetting partners can see the complete disclaimer and access the T&C Privacy Policy for the brand. A screenshot of the form is still required, but the image alone will no longer suffice. Effective January 2025, 10-DLC and TF submissions require a URL to the live Webform.
  • Include a check-box option for mobile consent if the form is used for collecting email and other contact consent. Otherwise, additional details must be included in the "opt-in flow" of the submission explaining how the form is encountered by the consumer, and that the webform is used solely for the purpose of opting-in to text messaging. 



Kiosk CTAs must also...

  • Include additional details in the opt-in flow of the submission explaining how the kiosk is encountered by the consumer, and that the interface is used solely for the purpose of opting-in to text messaging. 




New Sample CTA Templates for 2025 are available in the Reseller Google Drive.



<< Back to Top >>



Use Case and Opt-In Flow Descriptions

 

The sample language that auto-populates on the 10-DLC  Brand Registration and TF Verification forms are intended only to guide. It is important that these fields are reviewed before submission to us, and edited to match the details on the calls to action specific to the client. Below are some of the expected details.


  • The same verbiage displayed on the CTA sample must also be included in "use case summary" of the submission. If the CTA states "class updates, events, and schedule changes," then the use case must also include reference to "class updates, events, and schedule changes." 
  • If an online Webform is used, that also collects consent for emails and other channels, then the mobile field cannot be required and the webform must display a check-box option to join messaging. 
  • Otherwise, if a Webform or Kiosk is solely use to join text opt-in, then "opt-in flow" must explain how the webform or kiosk is encountered by the consumer, and that the interface is used solely for the purpose of opting-in to text messaging. 



<< Back to Top >>



Sender's Email, Phone & Address 


Vetting partners review the company details provided on the submissions in order to validate them with the website provided. More times than not, verifications are denied when provided with personal emails for the contact, or phone numbers and addresses that are different than what appears on their website.  





<< Back to Top >>




For questions or concerns about creating CTAs and submitting 10-DLC and TF Verifications, please open a ticket and reach out to our support team.