← All guides

A2P 10DLC in plain English: why your business texts stopped delivering

July 2026 · 6 min read · Plain-language guidance, not legal advice.

If your business texts customers from a regular 10-digit number — through any software, dialer, or texting app — and some (or all) of those texts have quietly stopped arriving, this article is probably why.

The short version

US carriers now require every business that sends application-to-person (A2P) text messages over regular 10-digit long code (10DLC) numbers to be registered: who you are (your “brand”) and what you send (“campaigns”). As of early 2025, the major carriers stopped merely throttling unregistered traffic and began blocking it outright. There’s no bounce notice to you and no voicemail equivalent — the message just doesn’t arrive. Your customer never got the reminder; you never found out.

The rules are carrier policy, not a statute — but they’re enforced at the network level, so they might as well be physics.

What registration involves

  • Brand registration: your legal business identity — EIN, legal name, address — registered through the industry’s central registry (via your texting provider). Sole proprietors without an EIN have a special, more limited registration path.
  • Campaign registration: a declaration of what you send (appointment notifications, customer care, marketing…), with sample messages, and proof you collect opt-in consent. Each campaign type is vetted.
  • Fees and timing: small one-time and monthly registry fees, and vetting that commonly takes days to a few weeks — plan for it, don’t discover it the week you switch software.
  • Ongoing conduct: carriers police content and complaint rates. Violations can carry per-message carrier fines (T-Mobile’s published penalties run into five figures for the serious categories), and high opt-out/complaint rates can get a campaign suspended.

The common alternative is a toll-free number, which has its own (generally simpler) verification process instead of 10DLC registration — same idea: verified sender, declared use, consent story required.

Why this matters more for trades than most businesses

Your texts are operational, not decorative. A blocked marketing blast is an inconvenience; a blocked appointment reminder is a no-show, and a blocked invoice link is money arriving late or never. Shops that set up texting informally in 2022 and never touched it are exactly the ones silently losing delivery today.

Quick self-check: do you know, for a fact, which registered brand and campaign your customer texts ride on today? If the answer is “I think the software handles it,” confirm it — with a test message to a phone on each major carrier at minimum.

One trap worth naming: 10DLC registration gets your messages delivered. It does not make them lawful. Consent under the TCPA is a separate obligation — carriers check that you have an opt-in story; the law cares whether you actually do, per customer, per message type. (We wrote a separate plain-language guide: TCPA for contractors →.)

How FieldLane handles it

FieldLane’s design principle is that sender registration is platform plumbing, not your problem: texting rides on infrastructure FieldLane registers and verifies, with the consent layer (per-contact, per-message-type, STOP/START, quiet hours) built into every send. You run the jobs; the delivery machinery and its paperwork are ours to keep in order. See how FieldLane’s texting works →

The paperwork you never did, done.

FieldLane handles right-to-cancel notices, consent-safe texting, and signed approvals automatically. Join the early-access waitlist.

Get early access