If you've tried to launch business texting and hit a wall of acronyms, 10DLC, TCR, A2P, CTIA, this is the plain-English decoder. Getting the sender type right is the difference between messages that deliver and messages that get filtered.
What is A2P messaging?
A2P stands for application-to-person: any text a business sends through software, a reminder, an alert, a promotion, an OTP, as opposed to P2P (person-to-person), which is two humans texting.
The distinction matters because US carriers treat the two completely differently. A2P traffic sent from unregistered numbers gets filtered, throttled, or blocked, and businesses caught routing A2P over P2P channels face penalties.
Since the industry-wide registration push completed in 2023, effectively all US business texting must go through a registered sender type, which brings us to the three options.
What is 10DLC?
10DLC means "ten-digit long code", a standard local phone number (like 971-XXX-XXXX) that has been registered for business messaging. Registration happens through The Campaign Registry (TCR), the industry body that vets brands and campaigns for the carriers.
Registering involves two layers. First, your brand, your legal business identity, EIN, and details, is registered and vetted. Then each campaign, the specific use case you'll message about (marketing, notifications, account alerts), is registered under that brand and reviewed.
Typical fees, as documented in provider pricing: a one-time brand registration around $4 to $44, one-time campaign vetting around $15, and a recurring $1.50 to $10 per month per active campaign, with amounts varying by brand type and use case.
Carriers then assign your brand a trust score that influences your daily throughput.
10DLC is the right fit when you want a local presence (customers recognize and can call a local number), your volume is moderate, and two-way conversation matters, it's the workhorse sender for most SMBs and mid-market businesses.
Watch out for: registration rejections from mismatched business information (your EIN, legal name, and website must line up), campaign descriptions that don't match your actual traffic, and the throughput ceilings that come with lower trust scores.
What is toll-free texting?
Toll-free texting sends from a verified 8XX number (800, 833, 844, 855, 866, 877, 888). Instead of TCR registration, toll-free numbers go through a verification process with the toll-free aggregator, you submit your business details and use case, and once verified, your number is approved for A2P traffic.
Toll-free is the right fit when you want a single national number (support lines, national brands), higher default throughput than entry-level 10DLC, and a simpler verification path. Customers can also call the number free of charge, which suits support use cases.
Watch out for: unverified toll-free traffic is heavily filtered, verification isn't optional in practice. And a toll-free number reads "national company," which is a mismatch if your brand is deliberately local.
What are short codes?
Short codes are 5 to 6 digit numbers (like 55123) built for maximum throughput, the sender type behind the biggest brands' high-volume campaigns and time-sensitive alerts.
They're leased (not owned), provisioned through carrier review, and priced at a premium: dedicated short codes historically run on the order of $500 to $1,000+ per month for the lease alone, plus setup and carrier approval time measured in weeks.
Short codes are the right fit when you send very high volumes on tight timelines, flash sales to hundreds of thousands of subscribers, national alerting, and the economics of premium leasing pencil out.
Watch out for: cost (they're by far the most expensive sender), the lead time for provisioning, and the fact that customers can't call them, which rules out phone-support use cases.
The comparison table
| 10DLC | Toll-Free | Short Code | |
|---|---|---|---|
| Number format | Standard 10-digit local | 8XX national | 5 to 6 digits |
| Registration | TCR brand + campaign registration | Toll-free verification | Carrier provisioning & review |
| Typical fees | ~$4 to $44 brand (one-time), ~$15 campaign vetting, $1.50 to $10/mo per campaign | Verification (often provider-handled); number cost | Premium lease ($500 to $1,000+/mo) + setup |
| Throughput | Tiered by trust score | Higher default | Highest |
| Voice-capable | Yes | Yes (free to caller) | No |
| Best for | Local presence, SMB/mid-market, two-way | National support lines, higher volume | Maximum volume, time-critical campaigns |
Where does RCS fit into this?
Here's the part most guides miss: RCS runs on a separate registration track, an RCS Agent verified through Google and the carriers, with your brand name, logo, and checkmark, but it doesn't replace the sender types above.
Because RCS falls back to SMS/MMS on unsupported devices, you still need a registered SMS sender (10DLC, toll-free, or short code) underneath your RCS program for the fallback traffic.
A complete US messaging setup in 2026 is typically: a verified RCS Agent for the rich, branded experience, plus a registered 10DLC or toll-free sender carrying the fallback.
The good news: on a unified platform, your company profile is captured once and feeds every registration, RCS agent, TCR brand and campaigns, toll-free verification, rather than re-keying the same KYC into three portals. See how SimplyRCS handles every channel on one platform, with registrations managed for you.
How to choose your sender type (a decision path)
Sending branded, interactive campaigns?
Lead with a verified RCS Agent, with fallback on one of the senders below.
Local business, moderate volume, two-way conversations?
→ 10DLC.
National brand or support line, single recognizable number, higher throughput?
→ Toll-free.
Very high volume, time-critical, budget for a premium lease?
→ Short code.
Not sure?
Most businesses start with 10DLC or toll-free and add capacity as volume grows, and a platform that supports all of them lets you change without re-platforming.
The registration pitfalls that stall launches
Registration is where timelines slip.
The most common failure modes: mismatched business data (legal name, EIN, and website must agree across every filing), vague campaign descriptions (carriers reject use cases they can't understand, "marketing" is too thin; "weekly promotional offers to opted-in retail customers with STOP opt-out" passes), missing consent language on your opt-in surfaces, and sending before approval (which earns filtering that's hard to undo).
This is exactly why white-glove registration matters: a provider that files, tracks, and corrects submissions for you, as SimplyRCS does across RCS, 10DLC, and toll-free, typically cuts weeks off the launch.
A realistic registration timeline, week by week
Here's what a clean, provider-managed registration actually looks like, useful for setting internal expectations:
Week 1: Data assembly and filing
You supply legal name, EIN, address, website, and use-case details; the provider audits for consistency (the step that prevents most rejections), then files TCR brand registration and drafts campaign descriptions. Brand registration often clears in days when data is clean.
Week 2: Campaign and verification review
Campaign vetting completes; toll-free verification (if using an 8XX number) is submitted in parallel. If you're launching RCS, agent creation and brand review run alongside, one company profile feeding every registration, which is the whole argument for a unified platform.
Weeks 2 to 4: Carrier approval and launch
Carriers accept the registrations onto their networks; your provider chases any stalled queues (this chasing is half the value of white-glove management). You send verified test messages to your own phones, confirm rendering and fallback, and go live.
Where the timeline blows up: a rejected filing adds one to three weeks per rejection cycle, which is how self-managed registrations stretch to months.
The three highest-yield preventions: audit your legal-name/EIN/website consistency before anything is filed; write campaign descriptions specific enough that a reviewer understands exactly what customers receive and how they opted in; and don't send a single message before approval clears (pre-approval traffic earns filtering that lingers).
Budgeting note: beyond the registry fees themselves, ask your provider two questions, are the fees passed through at cost or marked up, and is registration management included or billed as professional services? The answers vary more than the fees do. SimplyRCS includes registration management in onboarding with fees at cost; some providers charge hundreds per sender for the same filings.
Porting an existing number vs. starting fresh
A practical question most guides skip: if your business already texts from a number customers know, you can usually port it into a new platform rather than starting over, keeping the recognition while upgrading the infrastructure.
Porting a local number preserves your 10DLC registration lineage (though the campaign typically re-registers under the new provider), and toll-free numbers port similarly with re-verification.
Two cautions: schedule ports for low-traffic windows since cutover can briefly interrupt delivery, and never port a number with a history of spam complaints, you'll inherit its reputation.
Starting fresh makes sense when your old number's traffic was unregistered (its filtering history is a liability) or when you're restructuring senders anyway, say, consolidating three ad-hoc numbers into one registered local number for conversations and a toll-free line for national alerts.
A provider managing the port end-to-end, registrations included, turns this from a project into a form.
Frequently asked questions
What is A2P messaging?
A2P (application-to-person) messaging is any business text sent through software, reminders, alerts, promotions, verification codes, rather than from a person's phone. In the US, A2P traffic must be sent from a registered sender type (10DLC, toll-free, or short code); unregistered business traffic is filtered or blocked by carriers.
Do I need 10DLC to send business texts?
If you're sending A2P messages from a standard 10-digit local number in the US, yes, 10DLC brand and campaign registration through The Campaign Registry is required. Alternatives are a verified toll-free number or a short code. A provider can handle the registration for you as part of onboarding.
How much does 10DLC registration cost?
Typical documented fees: a one-time brand registration around $4 to $44, one-time campaign vetting around $15, and $1.50 to $10 per month per active campaign, varying by brand type and use case, plus whatever your provider charges to manage it. Some providers pass these through at cost; others add margin, so ask.
What's the difference between toll-free and 10DLC texting?
Both send SMS/MMS. 10DLC uses registered local numbers (local presence, TCR registration, trust-score-based throughput); toll-free uses verified 8XX numbers (national feel, higher default throughput, free for customers to call). Local SMB and two-way use cases lean 10DLC; national support lines lean toll-free.
Do I still need 10DLC or toll-free if I use RCS?
Yes. RCS uses its own verified-agent registration, but RCS messages fall back to SMS/MMS on devices that can't receive them, and that fallback traffic must be sent from a registered SMS sender. A complete setup pairs a verified RCS Agent with a registered 10DLC or toll-free sender underneath.
How long does sender registration take?
10DLC brand registration can complete in days when filings are clean; campaign approval adds days to a couple of weeks; toll-free verification typically takes days to weeks; short codes take weeks to provision; RCS agent verification adds its own brand review.
Clean, consistent business data and a provider managing submissions are the biggest accelerators, SimplyRCS customers typically go live in two to four weeks across all registrations.