10DLC for US business messaging: registered, trusted, two-way

10DLC means 10-digit long code applied to application-to-person traffic on US numbers. A long code is simply a normal 10-digit US phone number, the kind people text every day. The problem 10DLC solves is that carriers had no way to distinguish an app sending a message to a customer from a person texting a friend, and no basis for deciding whether an unfamiliar sender was legitimate. 10DLC is the answer to that problem: the sender registers, and the traffic is carried as known A2P rather than guessed-at person-to-person.

In practice 10DLC is the mainstream route for business text messaging in the United States. It carries transactional messages such as order updates, appointment confirmations and one-time passwords, supports two-way conversations where customers reply, and handles marketing traffic with consent and opt-out handling in place. Recipients see a local 10-digit number, which is also how replies work: customers press reply on a number, not a brand name.

It is not a phone number type you buy separately and it is not a short code. It is a registration status applied to a 10-digit number and the campaigns you run on it.

Registration exists because spam exists. When every application could send text messages from a plain US number, carriers had no way to know whether the sending was legitimate, what the message was about, or whether the sender respected opt-outs. The result was either too much spam reaching inboxes or too many legitimate messages being filtered to stop it.

The registry model answers that by making senders identify themselves. Registration records who the brand is, what it is sending and for which use case, and gives carriers a basis to apply rules: whether to accept, throttle, filter or block. For senders the trade-off is real and non-negotiable. A small amount of upfront registration work buys predictable delivery, and skipping it means your traffic is evaluated without an identity, which rarely ends well for the sender.

The way to treat registration is as infrastructure, not paperwork. It is part of the same setup as choosing a provider and buying numbers, and it should be started before launch rather than after delivery problems appear. Our US compliance page covers the rules that sit alongside registration, including consent and opt-out.

Registration happens through The Campaign Registry (TCR), the industry body that administers 10DLC, and it has two distinct parts. Brand registration is about who you are: legal name, tax status and identity details, which are vetted and which may be re-vetted or subject to secondary vetting. Campaign registration is about what you send: the use case, sample message, and opt-out behavior for each distinct campaign. The same brand can register multiple campaigns, and transactional and marketing traffic should normally be separate campaigns.

The registries charge fees for this: one-time brand and vetting fees, a fee per campaign, and a monthly fee per campaign. Figures change periodically, so treat them as approximate: currently around $2 per campaign per month for the recurring element. They are registry fees, not provider fees, and they are the cost of being a recognized sender rather than a number nobody can identify.

Timing is the part senders underestimate. Brand vetting can complete in hours to a few days, campaign vetting and carrier sync can take longer, and re-vetting or secondary vetting can add time. Plan for days rather than hours, and start well before launch. WorldText works through the registrations with you and provisions the numbers alongside.

Brand vetting produces a trust score, and the score matters because carriers use it to decide how much of your traffic to accept and how fast. Throughput scales with the score, broadly from about one message per second for low scores up to about 75 messages per second for the highest scores. The exact figures are per-carrier and change, so treat that range as the shape of the curve rather than a table of guarantees.

For most businesses the practical implication is burst capacity. A registration that completes with a low score supports steady operational volumes but can throttle a one-off blast; a higher score gives headroom for launches, verification campaigns and seasonal volume. If your traffic is genuinely high-volume, an SMPP interface is available on request and is normally activated within 24 hours.

The score is not a reward to be gamed; it is a measure of trustworthiness, and the honest levers are accurate vetting data, clean sender behavior and disciplined opt-out handling. Throughput is the carrier-side consequence of doing those things.

Registered 10DLC numbers carry the traffic that matters to a US business: transactional messages like one-time passwords, order and dispatch updates, appointment confirmations and security alerts; two-way conversations where customers reply to confirm, reschedule or ask a question; and marketing messages where consent and STOP handling are in place. Registration applies per campaign, which is why keeping auth traffic, operational messages and marketing in distinct campaigns is both cleaner and safer.

Compared with the alternatives, 10DLC is the everyday route. Short codes are five or six digits with very high throughput, but they are expensive and slow to approve. Text-enabled toll-free numbers bypass the local-number look and must be verified before A2P use. Our 10DLC vs Toll-Free guide and comparison of 10DLC, short codes and toll-free take the trade-offs apart in detail.

WorldText supports the whole path: provisioning registered 10DLC numbers, working through brand and campaign registration, delivering receipts to your callback, and carrying traffic over a documented HTTP API or SMPP. US destinations are 8 credits per single-part message, with multipart messages charged as multiple messages. See the US SMS API page for the integration side and our pricing page for rates.