The usual reason to skip 10DLC registration is that it looks like paperwork with a monthly fee attached, and nobody seems to be checking. That was partly true a few years ago. It isn't now. The enforcement that matters doesn't come as a letter from a regulator. It shows up as a quiet failure: your texts stop arriving and your dashboard still says "sent."
This post covers what happens if you send business texts from a regular 10-digit number without registering. It separates the carrier side (blocking and non-compliance fees) from the legal side (FCC rules and TCPA lawsuits), because owners mix them up all the time. It also works through the math on what registration costs next to what skipping it costs. We make Ready, so we'll be specific about how our platform handles this. We'll also be clear about what registration does not protect you from.
Who actually enforces 10DLC
10DLC is not a law. It's a framework the major US carriers built and run through The Campaign Registry (TCR), under industry messaging guidelines. No government agency approves your brand or campaign. Carriers do, through your messaging provider.
The rule itself is privately enforced, but the carriers control the pipes. They don't need to sue you. They can decline to deliver your traffic.
The government enters through a separate door: the FCC's rules on text messaging and the TCPA, which give recipients a private right to sue. Registration helps with carriers. It does very little for the legal side, which comes down to consent. If you want the full background, start with what 10DLC requires.
What happens to unregistered traffic, step by step
Carriers phased in enforcement through 2023 and into early 2024. They moved from filtering some unregistered traffic to blocking it outright on the major networks. If you send application-to-person (A2P) traffic from an unregistered 10-digit number today, expect this:
- Messages are blocked or silently filtered. The carrier drops the text before it reaches the handset. Depending on your provider, you may get an error code, or you may see "sent" with no delivery receipt.
- Your provider refuses to send at all. Most reputable providers now block unregistered A2P sends on their side before the carrier has to. This protects their own standing with the carriers.
- Non-compliance fees can be passed down. Carriers keep fee schedules for unregistered traffic and prohibited content. They charge these to the messaging provider, and provider terms usually let the provider pass them on to the account that sent the traffic.
- The number's reputation degrades. A number that carriers have flagged for spam-like unregistered traffic can stay filtered even after you register. Sometimes the cleanest fix is a new number.
We won't quote a specific carrier fine amount here. The schedules are set by the carriers, they differ by carrier and violation type, and they change. The honest summary is that carriers do charge these fees, they land on providers first, and your provider's terms decide whether you end up paying them.
The blocking is the real cost
Owners focus on fines, but the bigger cost is usually invisible: messages you paid to send that nobody received. Take a 2,000-contact appointment reminder campaign at one segment per text.
On Ready Standard, that's 2,000 × $0.0075 = $15, plus 2,000 × $0.0045 in carrier fees. (That excludes the optional $0.003-per-segment compliance surcharges, which are off by default.)
If most of those reminders are filtered, the send cost isn't the expensive part. Each no-show is the expense. For a business where a missed appointment costs $100 or more, losing even a few percent of reminders costs more than a year of registration fees. Blocked traffic also tends to look fine in the send log, so you might not notice for weeks.
What registration costs, worked out
On Ready, registration is handled in the app. Here's what it costs:
- At submit: $25, which is the first month. There's no setup fee.
- Monthly after that: $25/mo for registration + $2 per number.
- With one number: about $27 a month.
- Optional brand vetting: $79 Standard or $179 Enhanced, one-time. Most senders don't need it. It raises your trust score, which can move your daily throughput cap. See whether vetting is worth $79.
Most approvals take 2 to 7 days. During that window you aren't stuck. An account can send up to 500 texts a month before it registers, at its normal per-text rate. An account that bought its number before registering sends on Ready's shared registration while its own registration is in review. The first 20 texts are free (one-to-one sends only), and those end the moment a registration is paid for, so use them first. For a full fee breakdown across providers, see 10DLC cost, every fee explained.
Side-by-side: skipping vs registering
| Unregistered | Registered | |
|---|---|---|
| Delivery on major carriers | Blocked or filtered | Delivered, subject to content filtering |
| Carrier non-compliance fees | Possible, passed through by provider | Only for content violations |
| Throughput | Effectively zero | ~1 to 4 segments/sec for a fresh standard campaign; higher tiers reach tens |
| T-Mobile daily cap | N/A | ~2,000 to ~200,000/day by trust score |
| Monthly cost (1 number, Ready) | $0 | ~$27 |
| TCPA lawsuit exposure | Unchanged | Unchanged |
The last row matters most, and it's the subject of the next section.
The FCC and TCPA angle, without the hype
Registration and legal compliance are two separate tracks. Plenty of owners register, feel safe, and then get sued anyway.
The FCC side. Over the last few years, the FCC has adopted rules requiring carriers to block texts from certain categories of numbers, such as invalid or unallocated numbers. It has also moved to apply Do Not Call protections more clearly to texts. The FCC isn't checking your 10DLC status. Its rules push carriers toward more blocking, which is part of why unregistered traffic gets so little benefit of the doubt.
The TCPA side. This is where real money changes hands. The TCPA allows statutory damages of roughly $500 per text, and up to $1,500 if the violation is found willful. Recipients, not regulators, bring these claims, often as class actions. A 10DLC registration doesn't defend against a TCPA claim. What defends you is proof that each recipient consented.
There's also a practical overlap. Carriers review your opt-in flow during registration. That's why the consent wording you submit gets scrutinized, and why a sloppy opt-in tends to fail registration and create TCPA risk at the same time.
What reduces risk on both fronts
No platform makes you lawsuit-proof, and compliance is ultimately the sender's responsibility. Some controls do lower exposure, though. Here's what Ready provides:
- Automatic STOP handling. Inbound STOP or UNSUBSCRIBE is honored, and the opt-out applies across campaigns, so a contact who opted out can't be re-texted by a different campaign. Opted-out numbers are refused up front and not charged.
- Quiet-hours enforcement. Sends outside permitted hours, based on the recipient's area, are held and sent later. You're charged only when they actually send. Campaigns, drip campaigns and automations wait up to 24 hours for the window; a one-to-one or API text is held only if the window opens within 6 hours, otherwise it is refused and must be resent; a one-to-one reply to someone who texted you in the last 24 hours goes out at any hour.
- Litigator and DNC scrubbing. Known TCPA-litigator and DNC numbers can be screened out before a send. This is $0.003 per segment when switched on for an account, or $0.005 per contact as a standalone scrub.
- Sender attestation records. Each campaign you send and each API send that attests consent logs who sent it, to how many people, and when. That's an audit trail of your attestation. It is not a per-contact consent record. Your store or signup form has to keep each recipient's opt-in time, wording and page URL. Our guide to documenting SMS consent covers what to keep.
If you're a platform texting on behalf of your own customers, each sub-account carries its own registration. You can check status programmatically with GET /v1/registration. The quickstart walks through the setup.
One more note: SMS is for consented or replied leads. If your plan involves texting a purchased cold list, registration won't save it. Carriers will likely reject the campaign, and the TCPA math gets ugly fast. Use phone and mail for cold outreach.
Registered and still filtered?
Registration gets you onto the road. It doesn't exempt your content. Carriers still filter individual messages for things like link shorteners, prohibited categories and spam-like phrasing. If your campaign was approved but delivery is still poor, the cause is usually content, not registration. We cover that in why approved campaigns still get filtered.
The practical takeaway
The enforcement that hits small senders first isn't a fine. It's blocked messages that look sent. Carrier non-compliance fees exist and can be passed down to you, but lost delivery usually costs more. Separately, TCPA exposure of roughly $500 to $1,500 per text depends on consent, not registration.
Registering on Ready costs $25 at submit, then about $27 a month with one number, and most approvals take 2 to 7 days. You can send up to 500 texts a month while you wait, and your first 20 one-to-one texts are free if you use them before you register. If you'd rather see the flow than read about it, you can create an account and start the registration in the app.