New Requirement: December 14, 2023


Subject: NEW TF Verification Rule - Pending State Disabled Effective 1/31/2024 

 


Our upstream partners have notified us that new rules will be going into effect January 31, 2024 for Toll Free Numbers. 


ALL MESSAGING BLOCKED FOR UNVERIFIED TF CODES 


Beginning January 31, 2024, upstream partners will remove "pending state" as an intermediary to official verification and will begin blocking all traffic sent on toll-free numbers that are unverified. 


Toll free messaging codes will need to be fully verified before sending messages. 


Upstream partners are targeting 5-days as a reasonable window for verifying codes and are bringing on new staff to ensure optimal turnaround times. 


To help ensure that submissions do not encounter delays, pay close attention and avoid the most common causes for delays:


  • Verify the company's URL is secure - Unsecure websites cannot be used and will be immediately rejected. If the client has SSL issues or an unsecure page, provide a social website like Facebook or YELP.


  • Provide descriptive use cases and opt-in flows - The auto-filled content is a great guide, but it should not be the only source relied on to explain how the client is using messaging. Always review them to ensure that it fits how contacts are asked to join and how the client is using messaging. 


  • Sample messages need to match the use case and opt-in flow - Review the auto-filled sample messages and make sure that they match with the campaign type and use case for the client. 
    • Ex: the use case "Real Estate" should not have a sample message stating that the contact will receive $5 off their next visit. 
    • Ex: a client sending alcohol promotions needs to reference how age verification is collected in the opt-in flow


  • Age Verification - If the client is promoting services or products in messaging that require age-verification (ex: Alcohol), then age-verification is required for the mobile campaign and the option needs be selected when completing the form so that the sample message is populated. Age-verification should also be referenced in the opt-in flow, and a sample of an opt-in exchange needs to be uploaded along with the CTA (see sample below).   





  • CTA disclaimer is visible and compliant - Uploaded calls to action need to match the selected opt-in method. If selecting Kiosk as the opt-in methos, upload a sample image the KIOSK. All CTAs must have a visible, legible, and compliant disclaimer. Preferably, the client's logo is included and, or, the client's name is visible in the disclaimer (see sample below).