Skip to content
  • There are no suggestions because the search field is empty.

Carrier-Defined 10DLC Campaign Use Cases

Carriers and The Campaign Registry (TCR) require campaigns to be categorized under standard 10DLC use cases.

While TextBetter works with you at the time of registration to select the right use case, we understand your messaging needs and workflow can change over time.

This reference helps you understand the difference between categories — for example, which messages count as Customer Care versus Marketing — as sending messages outside your approved use case could lead to delivery issues or carrier filtering.

💡 Pro Tip

If you plan to send text messages outside of your registered 10DLC use case—or are unsure whether your message content falls within the approved use case—please contact TextBetter before sending.

We can review your intended use, discuss whether additional registration or campaign updates are needed, and help ensure alignment with carrier requirements and industry guidelines.

Below are the standard 10DLC use cases as defined by carriers and TCR:

10DLC Standard Use Cases

  • 2FA: Any authentication, verification, or one-time passcode.
  • Account Notification: Standard notifications for account holders, relating to and being about an account.
  • Customer Care: All customer care interaction, including but not limited to account management and customer support.
  • Delivery Notifications: Notification about the status of the delivery of a product or service.
  • Fraud Alert Messaging: Notifications regarding potential fraudulent activity on a user's account.
  • Higher Education: Messaging created on behalf of Colleges or Universities, including School Districts and education institutions. This use case is NOT for the "free to the consumer" messaging model.
  • Low Volume Mixed: For Brands that have multiple use cases and only need very low messaging throughput. Examples include: test or demo accounts, small businesses (single Doctor's office, single Pizza shop), etc. Maximum of 5 sub Standard use cases.
  • Machine-to-Machine (M2M): Machine-to-Machine (M2M) is a process that implies wireless communication between two or more physical assets. There is no human interaction in the Machine-to-Machine campaign. Subscriber-facing campaigns are prohibited. This is a dedicated use case.
  • Marketing: Any communication that includes marketing and/or promotional content
  • Mixed: For brands that have multiple use cases and want to run them on the same campaign. Minimum of 2 sub use cases and a maximum of 5 sub use cases.
  • Polling and voting: The sending of surveys and polling/voting campaigns.
  • Public Service Announcement: Informational messaging to raise an audience's awareness about important issues.
  • Security Alert: A notification that the security of a system, either software or hardware, has been compromised in some way and there is an action you need to take.