A2P 10DLC: Registration, Fees, and Trust Scores Explained

TL;DR

A2P 10DLC is the registration system US wireless carriers require before a business can send application-to-person text messages from a standard 10-digit local number. You register in three layers: your brand (who you are), your campaigns (what you send), and your lines (which numbers send it). Unregistered traffic gets filtered, throttled, or blocked.

• What registration costs: a one-time $47.50 brand registration fee, a $15 one-time vetting fee per campaign use case, and $10 per month for every registered campaign.
• What sets your ceiling: The Campaign Registry assigns your brand a trust score. A brand scoring 75-100 can send 200,000 SMS segments per day. A brand scoring 1-24 gets 2,000.
• Sole proprietor brands are capped at 1,000 messages per day no matter what their score is.
• The expensive mistake: picking a Mixed use case out of convenience. Mixed campaigns carry a lower daily limit, a higher cost per message, and slower carrier approval than two dedicated campaigns would.
• Registration is not consent. A2P 10DLC satisfies the carriers. The TCPA governs whether you were allowed to text that person at all. Passing one does nothing for the other.

Your messages say delivered. Your customers never saw them.

That gap is the single most common symptom of a 10DLC problem, and it is invisible from inside most dashboards. The message left your system, so your logs are clean. It died at the carrier, where a filter decided an unregistered or poorly-scored number sending promotional-looking text was probably spam. Nobody bounces it back to tell you.

Carriers built A2P 10DLC to end exactly that guessing game, in both directions. Register properly and you get a known identity, a published ceiling, and predictable delivery. Skip it and you are sending into a filter.

What is A2P 10DLC?

A2P 10DLC stands for Application-to-Person 10-Digit Long Code. It is the carrier-sanctioned route for sending automated or business text messages from an ordinary local phone number, the same format your reps already call from.

The distinction that matters is application-to-person. A text a rep thumbs out one at a time is person-to-person. A text your CRM fires when a lead fills in a form, a bulk broadcast, an appointment reminder, a drip sequence: all application-to-person, all in scope, even when a human clicked the button that started it.

The Campaign Registry describes 10DLC as a channel "in which Brands and Campaign Service Providers (CSPs) are verified prior to being allowed to send messages." That word prior is the whole design. Both the "who" and the "what" of a campaign are on file before the first message moves, which is why carriers will pass registered traffic they would otherwise filter.

Before 10DLC, businesses ran automated text from local numbers on an unwritten understanding, and carriers policed it by pattern-matching for spam. Legitimate senders got caught constantly. Registration replaced the pattern-matching with an identity check.

Key takeaway: if software triggers the text, it is A2P traffic and it needs to be registered, no matter how personal the message reads.

What "registered" actually means: three layers

Most teams think of registration as one form. It is three, and they gate each other in order.

1. Brand registration: who you are

Your brand is your legal business identity as the carriers will know it. Legal name, business type, registration number (an EIN in the US), address, website, and a named point of contact.

The details are matched, not just collected. Two rules cause most rejections: your legal name must be an exact match to your tax documents, and the domain on your point-of-contact email must match the domain of the website you submit. A real estate brokerage that files as "Cascade Realty Holdings LLC" but registers as "Cascade Realty," using a Gmail address for the contact, gets rejected on both counts.

Brand registration costs a one-time $47.50. If your brand is rejected and you want to appeal, that appeal costs $11.

2. Campaign registration: what you send

A campaign describes a category of message. This is where you declare the use case, and it is the most consequential choice in the entire process, because it is tied to both your approval odds and your sending limits.

The registration form asks how end users consent to receive your messages, and it wants a real answer between 40 and 2,048 characters listing every opt-in path you use. Not a sentence of boilerplate. If customers can opt in at checkout, by texting a keyword, and on a paper form at your counter, name all three.

Each campaign carries a $15 one-time vetting fee, charged when you submit it whether or not it gets approved, plus $10 per month once it is registered, including while it sits pending. Carrier review usually takes three to five business days.

3. Line registration: which numbers send it

Finally you attach phone numbers to a campaign. A single campaign holds up to 400 numbers, and each use case allows up to 50 campaigns.

Because the monthly fee is per campaign and not per number, sprawl is what costs you. Take an insurance agency with 18 producer lines. ❌ Wrong: 18 campaigns. ✅ Right: one campaign, 18 lines. Same coverage, $170 a month cheaper.

Key takeaway: group aggressively. Fees scale with campaign count, not with how many numbers you hang off each campaign.

What A2P 10DLC costs

📊 TABLE 1 — Sahoora to replace this paragraph with the Webflow Embed component using the styled embed code from your Slack DM.

Two line items surprise people. The campaign vetting fee is charged on submission, not on approval, so a sloppy application you have to resubmit costs you twice. And the monthly fee runs on pending and denied campaigns until you delete them, which is how teams end up paying for three campaigns they abandoned in month one.

Separately from registration, carriers charge a pass-through fee on the messages themselves. Aloware's pricing page puts that at $0.005 to $0.015 per segment, billed on top of your per-message cost, on both agent-sent and automated traffic. Budget it as a real line item: at the high end, a team pushing 60,000 segments a month is looking at roughly $900 in carrier fees alone.

How your trust score sets your ceiling

Once your brand is registered, The Campaign Registry assigns it a numeric trust score. That score, not your plan and not your number count, decides how much you can send.

📊 TABLE 2 — Sahoora to replace this paragraph with the Webflow Embed component using the styled embed code from your Slack DM.

Those limits reset at midnight Pacific. Note the shape of the curve: it is not linear. Moving from the 50-74 band into 75-100 multiplies your daily ceiling by five. No other lever on this list comes close to that.

The same score also governs your rate, measured in message segments per second. At 75-100 a brand gets 225 segments per second in total across the major US networks, 75 each toward AT&T, T-Mobile, and Verizon. At 50-74 that drops to 120 total, 40 per network. At 49 or below it collapses to 12 total, 4 per network.

The rate matters more than the daily cap for anything time-sensitive. A home services company texting 5,000 customers about a storm-related schedule change moves that list in about 22 seconds at 225 segments per second. At 4 segments per network per second, the same list takes over an hour, and the last person to hear from you hears from you after the truck was supposed to arrive.

Key takeaway: your trust score is a throttle on both volume and speed. Treat it like a credit score, because it behaves like one.

How to improve a low score

Appeals are free within 45 days of scoring. After that a re-vetting costs $40, or $95 for enhanced vetting. Aloware's support documentation is blunt about the odds: appeals are manual, can take weeks or months, and do not guarantee an increase. Processing typically runs two to four weeks and stretches to four to six during busy periods.

Which makes accuracy at registration the real lever. Scores are assigned on business registration accuracy and messaging history, so the cheapest points are the ones you do not lose to a typo. After that, clean opt-in practice and sane message frequency protect the score you have.

If you need capacity now rather than in six weeks, toll-free numbers carry higher volumes without being heavily restricted by brand score, and short codes support sustained high volume at meaningfully higher cost and setup time.

Choosing your use case: the Mixed trap

Three use cases cover most businesses. Customer Care for conversational support, account follow-up, and appointment reminders. Marketing for promotions, offers, and announcements. Mixed for a campaign doing more than one of those jobs.

Mixed looks like the safe pick. It is the expensive one. A Mixed campaign carries a daily limit typically under 2,000 messages, a higher cost per message, and slower approval, because carriers scrutinize combined-purpose traffic harder.

❌ Wrong: a medical practice registers one Mixed campaign covering appointment reminders and its quarterly wellness promotion, then wonders why reminders stop going out mid-afternoon on a busy day.

✅ Right: the same practice registers a Customer Care campaign for reminders and a Marketing campaign for promotions. Cost goes up by $10 a month and one $15 vetting fee. The reminder traffic gets its own ceiling and never competes with marketing volume.

Specialized use cases exist beyond those three, including 2FA, account notifications, delivery notifications, fraud alerts, higher education, polling and voting, public service announcements, and security alerts. If your traffic genuinely is one of those, register it as that rather than burying it in Mixed.

Key takeaway: split by purpose, not by team. Two dedicated campaigns beat one Mixed campaign on limit, price, and approval speed.

What happens if you don't register

Unregistered A2P traffic on a 10-digit long code does not fail loudly. It degrades:

• Filtering. Carriers drop messages silently. Your logs show sent. The recipient shows nothing.
• Throttling. Delivery slows to a trickle, which quietly destroys anything time-sensitive.
• Blocking. Sustained unregistered sending gets the number blocked outright.
• Number damage. A number that accumulates spam signal carries that history. Replacing it means starting over on reputation.

The operational cost lands on whichever team depends on text the most. For an auto dealership running service reminders, a filtered reminder is a no-show bay. For a solar installer, it is a rescheduled site survey and a truck roll wasted.

A2P 10DLC is carrier permission, not legal consent

This is the conflation that gets businesses in trouble, so be precise about it. Registration and consent are separate obligations with separate enforcers.

A2P 10DLC is a carrier requirement. It answers: will the networks carry your traffic, and how much of it?

The TCPA is federal law. It answers: were you permitted to contact this person? Under 47 U.S.C. § 227, a plaintiff may recover $500 in damages for each violation, and a court that finds the violation willful or knowing may increase the award at its discretion.

A perfectly registered brand with a 90 trust score texting people who never opted in is fully compliant with the carriers and fully exposed under the TCPA. Registration is not a defense. Our TCPA compliance checklist covers the consent side properly, and if you are weighing 10DLC against other business messaging routes, iMessage vs A2P 10DLC compares the channels directly.

One mechanical detail teams routinely get wrong: a STOP reply suppresses texts. It does not stop calls. Calls stop when the contact goes onto your internal do-not-call and suppression list, which is a separate action you have to actually take. Treat them as two obligations, because that is what they are.

None of this is legal advice. Where real exposure is on the table, have counsel review your consent language and your records.

Key takeaway: carrier registration gets your message delivered. Consent determines whether you were allowed to send it. You need both.

Registering A2P 10DLC in Aloware

Registration is genuinely tedious, and the tedium is mostly in translating your business into the fields carriers want. Aloware collects the required information and handles the submission from inside the platform, under Account > Compliance. The brand registration guide walks the fields, and your trust score is visible in the same tab once the brand is approved, so you are not guessing at your own ceiling.

What that score gates on the Aloware side is worth knowing before you plan a campaign. Business texting, Broadcast for bulk sends, Sequences for automated follow-up, and CRM-triggered workflows all draw on the same registered capacity. A low score does not disable those features. It just makes them slow, which is harder to diagnose.

Seat pricing starts at $30 per user per month on iPro with a 10-user minimum, $60 on uPro and $85 on xPro with 5-user minimums, on the discounted cycle. Registration fees and carrier pass-through fees are separate from the seat, as is the AloAi Voice Agent, which starts at $0.10 per minute and rises by model tier. The Pickup Stack, meaning NumberGuard, Branded Calling, and Local Presence, is an add-on rather than part of the seat price.

Bottom line

A2P 10DLC is not a compliance chore you file once and forget. It is a capacity decision. Your brand score sets your ceiling, your use-case choices set your cost, and your registration accuracy sets your score. Teams that treat it as paperwork end up throttled at 4 segments per second and cannot work out why their reminders arrive late.

Register the brand carefully. Split campaigns by purpose. Group your lines. Then check your score, because everything downstream of texting is capped by it.

Book a demo if you want to see the compliance workflow and the texting stack together before you commit.