10DLC Use Cases

The Campaign Registry requires that use case is declared at the beginning of the campaign registration process. Pre-defined Standard Use Cases are immediately available for all qualified, registered brands. Special Use Cases are sensitive or critical in nature and may require third-party vetting or pre/post-registration approval by MNOs. Note, this additional vetting may take up to five (5) business days. Requirements may vary according to each MNO. 

Note that use cases below with a value greater than zero indicated in the “Min Sub-usecases” column must include the indicated minimum number of sub-usecases at the time of submission. Use cases which do not indicate a value cannot include sub-usecases. Use cases which indicate a value of zero may include sub-usecases if desired. The maximum number of sub-usecases which can be included with one campaign use case is five. Use cases marked with a “YES” as a “Valid Sub-usecase” may be used as a sub-usecase for other campaigns.

* Post-registration approval by MNO required (up to five business days).
** Available to MNO pre-approved resellers only.

Agents & Franchises

The Agents & Franchises special use case applies the carrier limitations listed in the following article at the per-number level instead of at the campaign level as it would with all other use cases. This is ideal for call centers and agencies assigning individual 10DLC numbers to each agent, enabling the agents to use the numbers freely without the risk of one or more agents maxing out limitations for the entire campaign. The Agents & Franchises use case is an ideal applicant for a T-Mobile Number Pool submission, as it would enable the campaign to also contain more than 49 numbers at a time. Note, as this is considered a special use case, it is also subject to post-registration approval by MNOs. This may take up to five (5) business days. 

Group Messaging

Depending on a use case’s specific implementation, group messaging may utilize phone numbers not assigned to a unique individual, with characteristics inconsistent with consumer (P2P) messaging. In these cases, the service may be treated as an A2P service and require the numbers to be registered. It is recommended that group messaging services:

• Have strong anti-abuse controls and mechanisms appropriate for systems with potentially large message distribution.
• Support the ability of any member to opt out of the group at any time.
  Employ mechanisms to prevent recursive and/or cyclical messaging involving more than one group (in which one group is a member of another group).

Sole Proprietor and Platform Free Trial

Convey does not support sole proprietor or platform free trial use cases at this time. Our focus is on supporting enterprise, ISVs and resellers who also support messaging for enterprise. Reseller customers are responsible for managing MNOs’ requirements for outbound daily message caps (at the brand level) and the throttling of throughput (at the campaign level) on behalf of their downstream customers.

About Sole Proprietor (SP)

“Sole Proprietor” is a 10DLC business type and campaign use case and is limited to entities without an EIN/Tax ID. In other words, an individual with low volume sending. It is limited to one campaign and five (5) numbers.

Convey reseller customers supporting SP campaigns must:

• Ensure SP customers do not send more than their carrier-mandated daily outbound and per-minute message limits.
• Throttle traffic as-needed to comply with MNO requirements.
• Send monthly reports to Convey with data on SP usage toward T-Mobile, including daily message counts from each SP campaign.
• Execute a separate agreement with the SP entity.

Violations of the above principles may lead to suspension or disabling of the SP traffic, or of the reseller or Campaign Service Provider accounts per MNO directives.

About Platform Free Trial (PFT)

“PFT” use cases are available for 10DLC only for non-paying, time-limited trial customers of a reseller or CSP, where the reseller or CSP restricts the sending of messages to one (1) opted-in number per trial participant and caps the message volume at the carrier-mandated daily limit.

Convey reseller customers supporting PFT campaigns must:

• Provide a single dedicated sending number to each PFT campaign.
• Register each PFT campaign individually for 10DLC. This includes use cases involving Independent Software Vendors (ISVs).
• List themselves (the reseller) as the brand in 10DLC for the purposes of PFT campaigns and identify the ISV in the TCR reseller attribute (if ISV is applicable).
• Execute a separate agreement with the PFT entity.

10DLC Non-Profit & Government Brands

There are some key things to keep in mind when registering a 10DLC brand as a non-profit or government entity.

Charity / Non-Profit

When a brand’s legal entity type is “Charity / Non-Profit,” TCR will automatically perform vetting to confirm the specific non-profit tax status of your organization (e.g. 501(c)(3), 501(c)(4)). The specific 501c status will have an impact on which campaign use cases your non-profit will quality for.

• 501(c)(3) non-profits qualify for the Charity/501(c)(3) special use case, which provides substantial discounts on A2P carrier fees.
• • 501(c)(4), 501(c)(5), and 501(c)(6) non-profits qualify for the Political special use case, which provides increased messaging throughput for advocacy-related messaging.

Once a brand has been registered as a non-profit and its status is “Verified,” you can move on to registering its campaigns and their use cases.

501(c)(3)

Verified 501(c)(3) non-profit organizations can access reserved use cases - “Emergency” and “Charity / 501(c)(3).” In the future, the Charity use case will offer discounts on carrier fees associated with registered 10DLC messaging (date TBA). Most 501(c)(3) brands should register with the Charity use case, unless the “emergency” use case applies. “Emergency” use cases are defined as notification services designed to support public safety/health during natural disasters, armed conflicts, pandemics and other national or regional emergencies. Additional post-approval by carriers is required for the Emergency use case.

Government Agencies

Government agencies are eligible for increased messaging throughput on the T-Mobile network, regardless of their campaign use case. Verified Government brands will receive unlimited daily message caps on T-Mobile. Throughput on AT&T will be determined based on the campaign use case.

Providing accurate information about your agency and selecting Government as the company type during brand registration will trigger automatic vetting of your organization. If confirmed by TCR as a Government entity, the increased throughput will be applied.

Government agencies can begin to register with all Standard Campaign use cases, and will also be eligible for the Emergency Special Use Case if you will be sending alerts that meet the definition of the Emergency use case.

Registration for 527 Political Organizations

All 527 Political Organizations including political action committees (PACs) sending political communications on behalf of a Federal, State, or Local political campaign must be verified by Campaign Verify in order to successfully onboard to 10DLC and use the “Political” Special Campaign Use Case. This use case supports increased messaging limits. Campaign Verify is a secure, non-partisan verification solution for U.S. Political organizations who wish to engage with voters via text messaging.

Listed below are some important pieces of information about Campaign Verify registration:

• There is a one-time $95 fee from Campaign Verify per entity verification per two-year election cycle.
• If a Committee EIN is set during Campaign Verify verification (for state, local, or tribal verification only), this EIN will be cross referenced with the EIN used to register your A2P brand and must match.
• If you have additional questions about Campaign Verify registration, please refer to their FAQ or email support@campaignverify.org
• A Campaign Verify token can only be imported once. If a 527 organization is using multiple messaging providers, they should generate multiple Campaign Verify tokens - one per brand, created on their behalf.
• 501(c) advocacy organizations (e.g. 501(c)(4) social welfare groups) do not register with Campaign Verify. These groups will unlock the “political” special use case based on an automatic verification of their 501(c) status during brand registration and do not provide a token.

Campaign Verify Tokens

Verification will involve submitting information about your political organization to Campaign Verify, as well as verifying your identity as an authorized person associated with the political organization. Successfully importing a Campaign Verify token will assert your brand status as a verified 527 Political Organization with the carrier ecosystem.

After completing verification with Campaign Verify, you will receive a Campaign Verify Token (CV token) that you will then use during A2P 10DLC registration. Once a Campaign Verify token is imported, the A2P brand will qualify for the Political use case.

As a political service provider, you should instruct all of your 527 customers to register with Campaign Verify. If you are using Convey’s platform for 10DLC registration, you will need to securely collect the tokens from your clients, register their brands and then provide the tokens and brand id to Convey via a support ticket and we will submit them to TCR. If you are using TCR Portal for registrations, you may apply on your customer’s behalf within the external vetting section of the Brand Registration form. Ensure a valid Campaign Verify token is on-file for their Brand on an ongoing basis.