Skip to content
CaviusConnect

August 24, 2026 · CaviusConnect

The 10DLC registration guide: TCR, brands, and campaigns

If you send business SMS to US customers from a regular local number, 10DLC registration is the paperwork standing between you and reliable delivery. This guide explains what it is, how the registration chain works, why campaigns get rejected, and how it relates to (but differs from) the TCPA.

What 10DLC is

10DLC stands for 10-digit long code: an ordinary local phone number used for application-to-person (A2P) messaging. For years, businesses sent A2P traffic over long codes intended for person-to-person texting, and carriers responded with aggressive spam filtering that caught legitimate traffic too.

10DLC is the US carriers' answer: a sanctioned A2P route on local numbers, in exchange for knowing who is sending and what. Every brand registers its identity, every messaging use case registers as a campaign, and traffic from registered senders gets proper throughput and deliverability. Unregistered A2P traffic on long codes is now heavily filtered or blocked outright by US carriers.

The Campaign Registry (TCR)

Registration runs through The Campaign Registry, the central hub the carriers appointed. You generally don't deal with TCR directly (your messaging platform files on your behalf), but the two objects it tracks are worth understanding, because they're what approval hinges on.

Step 1: Brand registration

The brand is your business identity: legal name, address, tax ID (EIN for US companies), website, and vertical. TCR verifies this against public records, and the result includes a vetting outcome that influences your messaging throughput: higher-trust brands get higher per-carrier message rates.

Common friction points:

  • Details must match your tax records exactly. A trade name where the legal name should be is the classic silent failure.
  • Sole proprietors have a special, more limited registration class with low throughput caps.
  • Optional external vetting can raise throughput for brands that need volume.

Step 2: Campaign registration

A campaign describes a use case: marketing, two-factor authentication, customer care, delivery notifications, and so on. Each campaign declares its message flow, sample messages, and how recipients opt in. Carriers (or their reviewing partners) then approve or reject it.

There are real costs here: a small one-time brand fee and a recurring monthly fee per campaign, varying by use-case type. Budget for them, and resist the urge to cram unrelated traffic into one campaign to save a fee: mismatched traffic is a suspension risk.

Why campaigns get rejected

Most rejections trace to a handful of causes:

  • Opt-in isn't demonstrated. Reviewers want to see where and how a recipient agreed to receive these messages: a screenshot or URL of the actual consent flow.
  • Sample messages don't match the declared use case, or are too generic to review.
  • Public URL shorteners (bit.ly and friends) in samples, a known spam signal. Use a branded domain.
  • Missing required language: opt-out instructions (STOP) and help (HELP) handling in appropriate flows.
  • Brand/campaign inconsistency: the campaign describes a business the brand registration doesn't support.

10DLC is carrier policy. TCPA is the law.

These get conflated constantly, and the distinction matters:

  • The TCPA (Telephone Consumer Protection Act) is a federal statute. It requires prior express consent for marketing texts (prior express written consent for autodialed marketing), and it comes with statutory damages per message. Courts enforce it; class actions are common.
  • 10DLC is the carriers' private registration regime. It determines whether your messages deliver, not whether they're legal.

Registering a 10DLC campaign does not make your messaging TCPA-compliant, and TCPA-perfect consent doesn't get unregistered traffic delivered. You need both: registration for deliverability, consent management for legality. That pairing is exactly what the CaviusConnect compliance engine enforces: consent checks in the send path, on registered routes.

Alternatives to 10DLC

Two other sanctioned US routes exist: verified toll-free numbers (a lighter verification process, popular for support and notifications) and short codes (five/six-digit numbers with the highest throughput and the highest cost). Which fits depends on your volume and use case, and a platform can mix them under one campaign strategy.

How CaviusConnect handles it

On CaviusConnect's SMS channel, brand and campaign registration is run for you: we file with TCR, track approval status, and surface it in the dashboard. Once live, every send is checked against the recipient's consent record and your registered campaign before it leaves the queue, so the registration you paid for is actually enforced, and India's equivalent regime is handled the same way (see our DLT registration guide for how the two compare).

Start free and we'll walk your registration through, or read the getting-started guide to see the API side first.