You registered your 10DLC campaign, picked "Marketing" from the dropdown because it seemed like the safe catch-all, got approved in a couple of days, and started sending. Then your appointment reminders started arriving late — or not at all — for a chunk of your list. No error. No bounce. Just quiet under-delivery that you only notice when someone says "I never got the text."
The campaign is approved. The number is registered. So what's throttling you?
The answer is buried in the field almost nobody thinks about after approval: the use-case category. That single dropdown is what carriers read to decide how fast you're allowed to send and how much scrutiny each message gets. Register the wrong one for what you actually send, and you inherit throughput limits and filtering rules built for a different kind of traffic.
Full disclosure: I work for Ready, an SMS platform that handles 10DLC brand and campaign registration in-app. So I've watched this exact mismatch trip up senders more times than I'd like. This post is the fix.
The use-case isn't a label — it's a throughput contract
When you register a 10DLC campaign, you're not just describing your business. You're telling the carriers what class of traffic to expect, and they assign throughput and trust based on that class.
Here's the part people miss: different use-cases get different treatment. A campaign registered as low-volume mixed marketing doesn't get the same per-second and per-day allowance as one registered for account notifications or 2FA. Carriers gate throughput by a combination of your brand trust score and your campaign's use-case — the two multiply together.
So "Marketing" isn't a neutral default. It's specifically the category carriers watch hardest, because marketing is where spam and complaints live. Promotional traffic gets tighter content filtering and, on some carriers, lower throughput ceilings than transactional traffic like reminders and alerts.
If you register Marketing and then send appointment reminders, you're getting the worst of both: the stricter filtering meant for promos, applied to messages that would have flown clean under a transactional use-case.
What "throttling" actually looks like
Throttling rarely announces itself. There's no red banner. Here's the shape of it:
- Silent queueing. Your platform accepts the send, but the carrier meters it out slowly. A 20,000-contact reminder batch that should clear in minutes trickles over an hour — and reminders that arrive after the appointment are worthless.
- Content filtering. Individual messages get dropped by carrier spam filters that are tuned more aggressively for marketing traffic. Delivery receipts come back "delivered to carrier" but never reach the handset.
- Per-day caps. Lower-trust campaigns hit a daily message ceiling. Once you cross it, everything else silently spills to tomorrow.
We wrote a whole piece on the mechanics of the cap that stalls big sends — the throughput ceiling that spreads your 'instant' send — and it applies doubly when your use-case is working against you.
The common mismatches (and which direction each one hurts)
The two directions of mismatch fail differently. One throttles, the other invites filtering.
| What you registered | What you actually send | What happens |
|---|---|---|
| Marketing | Appointment/order reminders | Reminders get promo-grade filtering + tighter throughput; late or missing delivery |
| Marketing | 2FA / OTP codes | Codes delayed past expiry; some filtered entirely — worst-case for auth |
| Low-Volume Mixed | High-volume promos | Daily cap hit early; back half of your blast queues to the next day |
| Account Notification | Actual promotional offers | Carrier flags content that doesn't match the transactional use-case — filtering or campaign review |
| Customer Care | Cold outreach to non-opted-in leads | Complaints spike, trust score drops, campaign can get suspended |
Notice the last row. Picking a friendlier-sounding use-case to dodge scrutiny doesn't work — carriers read your content, and content that doesn't match the registered use-case is itself a filtering trigger. We covered that in why approved campaigns still get filtered.
How to pick the right use-case
Match the use-case to the dominant thing you send, and be honest about it. A quick decision guide:
- Are you sending codes or login verification? → 2FA / OTP. This gets the highest-priority routing because carriers want auth to land. Never bury this under Marketing.
- Are you sending order updates, shipping notices, appointment reminders? → Account Notification (or the transactional/reminder use-case your platform exposes). These are triggered by a user action and expected — they route well and filter light.
- Are you sending back-and-forth support conversations? → Customer Care.
- Are you sending offers, promos, sales, newsletters? → Marketing. Accept the tighter filtering and make sure every recipient opted in.
- Do you genuinely send a blend of the above from one number? → Mixed / Low-Volume Mixed — but understand this is a compromise. It's convenient, and it caps your throughput. If reminders are time-critical, they deserve their own transactional campaign.
The cleanest architecture for a business that does both marketing and reminders is two campaigns: one Marketing, one transactional. Route promos through the first, time-sensitive reminders through the second. Yes, that's two campaign registration fees — roughly ~$20/mo per campaign in carrier fees on top of your ~$10/mo brand — but that's cheap insurance against a reminder that lands 40 minutes late.
If reminders are your bread and butter, don't hide them under Marketing
This is the one I'd underline. Reminders and notifications are the easiest traffic to deliver well — recipients expect them, complaint rates are near zero, and the transactional use-cases carriers offer are built exactly for them. Registering that traffic as Marketing throws away the advantage you were handed for free.
If you've already registered Marketing and your reminders are suffering, the fix isn't a support ticket begging for more throughput. It's registering a second, correctly-scoped campaign and moving reminder sends onto it. Same brand, new campaign, transactional use-case, usually approved in 1–3 days.
For senders who legitimately need more headroom even on a correctly-registered campaign, brand vetting can raise your throughput tier — we broke down when the $40 vetting actually pays off. But vetting won't rescue a mismatched use-case. Fix the category first; buy throughput second.
Where Ready fits
Ready handles brand and campaign registration inside the app, and the registration flow makes you pick the use-case up front — which is the point where most of these mistakes get made or avoided. Because we route over multiple carrier providers and register on standard 10DLC, you get the throughput your use-case earns, not a resold approximation of it.
If you run more than one type of traffic, you can register separate campaigns per use-case under the same brand and keep them cleanly split — reminders on transactional, promos on marketing. For GHL agencies, campaigns map per location/sub-account, so each client's use-case is isolated and correct rather than everyone jammed into one catch-all.
A practical note on cost, since throughput failures usually surface during a big send: a plain 150-character reminder is one segment. At Ready Standard that's $0.02 + $0.0045 carrier = $0.0245. A 20,000-contact reminder batch is 20,000 × $0.0245 = $490 — and every one of those needs to land on time, which is exactly what the right use-case buys you. (Past 50,000 segments in a month, per-segment drops to $0.016 automatically — no plan to pick.) You can start with 2,500 free credits, no card, at app.tryready.com/signup, or read the full 10DLC explainer first.
The takeaway
Your 10DLC use-case is a throughput and trust contract, not a label. "Approved" only means the campaign is registered — it says nothing about whether the category matches your actual sends. When it doesn't:
- Marketing-registered reminders get promo-grade filtering and slower routing.
- Auth codes buried under Marketing arrive after they've expired.
- The wrong category caps your daily volume and silently queues the overflow.
Pick the use-case that matches what you actually send most. If you send two genuinely different kinds of traffic, register two campaigns and route each to its own. It's a small setup cost that decides whether your time-sensitive texts land in seconds or forty minutes late — and in the reminder business, forty minutes late is the same as never.
If you're not sure which use-case your traffic falls under, that's a five-minute conversation worth having before your next big send — not after it under-delivers.