General context on 10DLC and opt-ins
Many clients have been asking whether 10DLC should change their approach to who they text, particularly whether organizations now need prior express permission (aka opt-in) for peer-to-peer texts sent via GetThru. This article provides our best current understanding of how to approach that question.
- First, we'll start with a disclaimer. GetThru has never monitored texting universes for opt-ins, and we have no plans to do so. Clients choose who they want to text through our software, and we send those texts on their behalf.
- Second, we believe that any enforcement of the new 10DLC rules will be complaint-based. It is our understanding that carriers have no way to monitor 10DLC texts for opt-in. But they can and will notice when a texting campaign results in many complaints or "unwanted" messages. So the most important thing GetThru clients can do is to avoid texting behavior that is likely to generate complaints. That means not texting people who are highly unlikely to be receptive to your message and not over-texting your supporters. Our clients should always honor opt outs.
- Third, it's important to remember that 10DLC does not change the widely stated best practices from the carriers regarding opt-ins. CTIA, the industry association for telecom carriers, has been encouraging opt-ins since July 2019. So have Twilio, Bandwidth, and other intermediaries who facilitate P2P texting through their APIs. But, in spite of those guidelines, many organizations have chosen to send texts without opt-ins because they believe (as do we) that it is 100% legal to do so under the TCPA and because it's an essential tool for reaching key audiences.
Update as of February 23, 2023
As 10DLC continues to evolve, carriers are now requesting that organizations have a space on their website where a contact can knowingly add themselves to texting lists. At GetThru, we know that organizations gather their texting lists from multiple sources. Clients will still choose who they want to text through our software, and we will continue to send those texts on their behalf.
This is the kind of language carriers are looking for with phone input fields: “By providing your phone number, you agree to receive text messages from (organization). Message and data rates may apply. Message frequency varies.”
If your site doesn’t include that already, adding it would help your organization be more compliant with 10DLC rules. Carriers are confirming that the language exists on the website through a process called "Manual Vetting."
GetThru has made the following changes:
- The opt-in URL is collected during Use Case registration.
- If organizations have already registered their Use Case, GetThru has provided an pop-up on the Brand Registration page.
- As use cases pass through Manual Vetting, they go through a series of statuses until they are approved. We have made the statuses visible on the Use Case Registration page, and the statuses are communicated through a series of emails sent to account owners.
Update as of November 16, 2022
As part of 10DLC, carriers have requested additional information:
- Carriers are asking to know more about how your organization creates its texting lists. During use case creation, admins will now have to specify the "Contact Source" of their texting lists, as described in this article. Admins should select every option that applies to how a contact could be added to your texting list.
Update as of May 18, 2022
Implications of November 1, 2021 Deadline
The only thing that is different from an opt-in perspective as of November 1, 2021, is that there is a threat of fines from T-Mobile. Here's what we know about these fines:
- T-Mobile is the only carrier proposing these fines. Neither AT&T nor Verizon have announced any fines related to 10DLC traffic.
- These proposed T-Mobile fines are brand new and have never been levied, so we don't know how serious T-Mobile is about actually applying them.
- One of the fines -- the Content Violation fine -- appears relevant to the question of opt-ins because one of the content categories that could trigger this fine is "messaging that meets the Severity 0 violation threshold per the CTIA Short Code Monitoring Handbook." That Severity 0 threshold includes "Messaging sent without a valid opt-in." We don't know why T-Mobile uses guidelines established for Short Codes to govern 10DLC traffic.
- We also lack information about enforcement. T-Mobile has indicated that the Content Violation fine would only be levied after a third offense. This suggests that organizations should have warning before any fines are levied because they will first have to receive notice of multiple offenses that do not trigger a fine.
- Numerous advocacy organizations, party committees, elected officials, and vendors (including GetThru) are actively pushing back on these proposed fines, which we think are a massive overreach. T-Mobile knows that if they begin taking steps towards instituting the fines, they will experience considerable opposition.