The 10DLC registration form asks you to choose a use case from a dropdown. It looks like a piece of metadata you fill in and forget. It’s actually the single choice that most shapes how your program runs — it sets your throughput ceiling, influences your per-message surcharges, and accounts for a large share of whether you’re approved at all.
Standard and special use cases
Most programs register under a standard use case — two-factor authentication, account notifications, customer care, marketing, delivery notifications, and the like. A smaller set are special use cases — charity, political, emergency, K-12, sweepstakes — that carry extra vetting and, in some cases, extra requirements. Declaring a special use case when a standard one fits only adds friction; declaring a standard one when your traffic is actually special invites a rejection.
Mixed use case: flexibility with a cost
A mixed use case lets one campaign carry several message types — say, notifications and marketing on the same number. It’s the right tool when your traffic genuinely spans categories, but it’s vetted and priced for that breadth. If your program really only sends one kind of message, a single well-matched use case is cleaner, cheaper, and easier to approve.
Use case drives throughput
Your use case, combined with your brand’s trust score, maps to the throughput carriers will grant you — the messages-per-second and daily volumes each network allows. Two campaigns with identical content can carry very different ceilings because they declared different use cases. If you’re not getting the throughput you need, the use case is one of the first places to look.
The alignment rule
Whatever you declare, everything else has to match it: your sample messages, your opt-in language, and the traffic you actually send. A campaign registered as account notifications whose samples read like promotions gets judged on the samples, not the label. Misalignment is one of the most common reasons campaigns are rejected — and it’s entirely avoidable.
How to choose well
- Match the use case to your dominant traffic, not your aspirations.
- Reach for mixed only when you truly send multiple message types.
- Make your samples and opt-in read like the use case you picked.
- If you’re unsure, start from the full use-case breakdown rather than guessing.
Frequently asked questions
Can I change my use case later?
You can re-register a campaign under a different use case, but it’s treated as a new submission — with the vetting and turnaround that implies. It’s worth getting right the first time.
Does the use case affect what I pay?
Indirectly, yes. Use case influences throughput classification, and carrier surcharges vary by program and message type — so two use cases can carry different effective costs for the same volume.
Standard or mixed by default?
Default to the narrowest standard use case that covers your real traffic. Mixed is a deliberate choice for genuinely multi-purpose programs, not a safety hedge.
Disclaimer: This article is general information, not legal or compliance advice. Carrier rules, CTIA guidelines, and 10DLC and toll-free requirements change often and are enforced at the discretion of the carriers and their vetting partners. Tychron makes no warranty as to its accuracy or completeness and accepts no liability for actions taken in reliance on it — confirm current requirements with the relevant authorities and your own counsel before acting.