10DLC explained: registration, timelines and choosing a number type

If your business sends texts from a regular 10-digit phone number, such as payment reminders, appointment confirmations or one-time passcodes, U.S. carriers expect those messages to run through 10DLC. Registration tells carriers who you are and what you send. In return, you get carrier-approved routes and more predictable delivery. This FAQ answers the questions teams ask most about registration and timing.

What is 10DLC?

10DLC (ten-digit long code) is the U.S. carrier-sanctioned system for business application-to-person (A2P) text messaging from standard 10-digit local phone numbers. Businesses register their company (the "brand") and each messaging use case (the "campaign") so carriers can see who is sending what before they deliver messages at scale.

The Campaign Registry (TCR) runs the central registry that carriers use for 10DLC. It describes 10DLC as an A2P channel in which brands and their messaging providers are verified before they are allowed to send messages.

Why it exists: carriers built 10DLC in part to fight spam. Requiring registration lets them trace messages back to a verified business, which protects consumers and gives legitimate senders better delivery.

Who must register for 10DLC?

Any business that sends A2P text messages from a local 10-digit number to U.S. mobile subscribers needs to register. That includes alerts, reminders, two-factor codes, customer care and marketing texts sent by software rather than typed by a person.

A few points that often confuse teams:

• You register through a provider. TCR does not accept registrations directly from brands. You work with a registered Campaign Service Provider (CSP), usually your messaging or CPaaS vendor, which submits your details for you.
• Each provider registers separately. Plum's 10DLC FAQ notes that each CSP must register the brands and campaigns it works with, even if another provider already registered your brand.
• Existing numbers can be registered. You do not need new numbers if you already text from long codes; you need to register them.
• Toll-free numbers and short codes are separate. They do not use 10DLC registration. See the comparison table below.

What happens if you do not register? According to Plum's FAQ, unregistered 10DLC traffic can face higher carrier surcharges, lower throughput, penalty fees, filtering and blocking.

How do brand and campaign registration work?

Registration happens in two parts: first your company (the brand), then each use case (the campaign). Here is the typical process.

1. Gather brand details. Plum's FAQ lists what carriers ask for: legal company name, physical address, country of registration, EIN or tax ID, company type, website, industry vertical, stock symbol and exchange for public companies, and a contact who can answer carrier questions.
2. Submit the brand through your CSP. TCR runs an identity check that compares your EIN, legal name and address. The result is "Verified" or "Unverified." Typos or outdated details are a common cause of an Unverified result, so Plum recommends sending a copy of your IRS W-9 to make sure the details match.
3. Consider optional vetting. A third-party vetting partner can perform a deeper check and return a score. A higher score can lead to a higher messaging class and more throughput, but there is no guarantee.
4. Register each campaign. For each use case, you provide the use case type, the numbers it will use, sample messages and the campaign's life cycle. Use 2FA and account notifications as separate campaigns, for example. Standard use cases include 2FA, account notifications, customer care, delivery notifications, fraud alerts, marketing and polling. Special use cases, such as charity, emergency or political messaging, need extra review.
5. Wait for carrier approval, then send. Once the campaign is approved and linked to your numbers, messages flow over registered routes with the throughput your registration earned.

Across all of this, follow CTIA's Messaging Principles and Best Practices, the industry guidelines carriers use for consent, opt-out and message content.

How long does 10DLC registration take?

There is no single fixed timeline. The brand identity check is the first step, optional vetting adds time, and campaign review by carriers and their partners adds more. Special use cases take longer because they need extra approval, as Plum's FAQ notes.

To avoid delays:

• Submit details that exactly match your IRS records.
• Write sample messages that look like what you will actually send, with your brand name and opt-out language.
• Make sure your website and privacy policy describe how you collect consent.
• Register before your launch date, not the week of it, and leave room for a resubmission if a brand comes back Unverified.

10DLC vs toll-free vs short code: which should you use?

Choose 10DLC for local-presence texting at moderate volume, toll-free for national programs that want one recognizable non-local number, and short codes for the highest volume and speed. This table summarizes the differences.

How Plum Voice handles this

Plum's 10DLC FAQ explains that Plum acts as your Campaign Service Provider and submits brand and campaign registration to TCR for you; you supply the business and use-case details through Plum's registration form. Plum DEV supports two-way SMS, and the FAQ notes that Fuse (as of version 7.5) includes SMS features, so 10DLC applies to texts sent from local numbers in either product.

For texting alongside voice, see outbound messaging and notifications and Plum DEV. If your program also places outbound calls, read STIR/SHAKEN for outbound IVR.