A2P messaging — Application-to-Person messaging — is any text message sent by software on behalf of a business to an individual’s phone. Appointment reminders, delivery notifications, two-factor codes, marketing blasts — if an application generated the message instead of a human thumb-typing it, US carriers classify it as A2P and hold it to a completely different set of rules than person-to-person texting. Those rules decide whether your messages get delivered or silently dropped.
This is the pillar guide for the A2P topic. It covers what A2P means, how it differs from P2P, the three sending routes (10DLC, toll-free, short codes), and why the registration system exists at all. SIPNEX is an FCC-licensed carrier that provides SMS and MMS messaging alongside voice, and handles A2P registration on behalf of messaging customers — so what follows is the carrier-side view.
A2P vs P2P: the line carriers actually enforce
P2P — Person-to-Person — is the texting the phone networks were built for: one human, one handset, one conversation at a time. A2P is everything else: messages originated by an application, a platform, or a business system, usually to many recipients. The distinction is not about content or intent. A friendly “your table is ready” text from a restaurant’s booking system is A2P. A business owner texting one customer from their personal cell is P2P.
Carriers enforce this line because the two traffic types behave differently on the network. P2P traffic is low-volume, conversational, and roughly balanced between sending and receiving. A2P traffic is high-volume, one-directional, and template-driven. Carrier systems profile traffic on exactly those signals — volume per number, send/receive ratio, message similarity — and traffic that behaves like A2P gets treated as A2P regardless of what the sender calls it.
The practical consequence: there is no compliant way to run business messaging over P2P routes. Sending bulk texts from consumer lines or unregistered numbers to dodge A2P rules is the pattern carrier filters are specifically built to catch. Legitimate A2P traffic goes through one of three sanctioned routes.
The three A2P routes: 10DLC, toll-free, and short codes
Every registered business message in the US travels over one of three number types, each with its own registration path, cost profile, and throughput characteristics.
10DLC — 10-Digit Long Code. A standard local phone number, like (214) 555-1234, registered for A2P use through The Campaign Registry (TCR). This is the default route for most businesses: local numbers are inexpensive, recognizable, and can carry voice and text on the same DID. Registration means filing your brand (business identity) and campaigns (use cases) with TCR, then linking numbers to approved campaigns — each number attaches to exactly one campaign at a time. The full process is in our A2P 10DLC registration guide, and the entity behind the vetting is covered in our Campaign Registry explainer.
Toll-free verified. Messaging from 800/888/877/866/855/844/833 numbers runs on a separate track: carrier-managed toll-free verification rather than TCR registration. It suits national brands and customer-service use cases where a toll-free identity fits. Since early 2026, new toll-free verifications require a business registration number — an EIN for US businesses — along with entity type and country of registration.
Short codes. Five- or six-digit numbers like 12345, built for the highest-volume use cases — short codes can handle hundreds of messages per second, versus the 1 to 75 messages per second typical of 10DLC depending on trust score. They carry the highest cost and a dedicated provisioning process, which is why they make sense for large-scale alerting and marketing programs rather than everyday business texting. Our short codes guide covers when the economics work.
There is also a legacy fourth path worth naming so you can avoid it: email-to-SMS gateways, the old address-style route (number@carrier domain). Carrier support for it has been shrinking, and it was never a sanctioned A2P route — anything business-critical belongs on one of the three registered paths above.
Why A2P registration exists: the economics of spam
Before the registration framework, any business could blast texts from any number with no oversight. SMS is cheap to send and nearly always read, which made it irresistible to spammers — and carriers could not tell a pharmacy’s refill reminder from a phishing blast at the network level. Their only tool was blunt content filtering, which blocked spam and legitimate messages indiscriminately and degraded the channel for everyone.
The A2P framework flips the economics. Instead of guessing at message legitimacy after the fact, carriers require senders to identify themselves up front: who you are (brand registration, vetted against IRS and business records), what you send (campaign registration with sample messages and opt-in methods), and from which numbers. Verified identity is expensive for spammers to fake at scale and cheap for legitimate businesses to provide once.
The framework rolled out between 2019 and 2023 — the timeline and the entity behind it are covered in our Campaign Registry explainer — and since 2023 carriers have moved from surcharging unregistered traffic to filtering and blocking it. For the current state of fees, rules, and deadlines, our A2P 10DLC news tracker is updated monthly.
What sanctioned traffic means in practice
Registration is not a formality — it changes how the network treats every message you send.
Registered traffic gets preferential routing. Your brand’s trust score, assigned during TCR vetting, determines your throughput — messages per second and daily limits. Brands that vet cleanly — real EIN, live website, some operating history — get workable throughput; brand-new entities and sole proprietors start at the bottom tiers. Higher-trust transactional campaigns are provisioned more generously than low-trust marketing campaigns.
Unregistered traffic fails silently. T-Mobile, AT&T, and Verizon filter unregistered A2P traffic aggressively, and the failure mode is the worst kind: your platform reports “sent” because the carrier accepted the message at ingestion, but the recipient never receives it. You discover the problem only when you track delivery confirmations per carrier.
Registration still is not the whole job. Carrier policies restrict content categories (the SHAFT set — sex, hate, alcohol, firearms, tobacco — is limited on some carriers), require opt-out handling on every campaign, and monitor STOP compliance. And TCR approval addresses deliverability, not consent law — TCPA obligations are a separate legal layer that applies whether you send one message or one million. Political senders face an additional vetting layer on top of standard registration, covered in our Campaign Verify guide.
The carrier layer under every message
Whatever tool sits on top — a marketing platform, a CRM integration, an SMS API — the message ultimately hands off to carrier infrastructure, and that is where delivery is decided. The plumbing between your application and the mobile networks is an SMS gateway, and the gateway’s carrier relationships determine how your traffic is scored and routed.
The carrier layer is also where the cost stack lives. On top of your provider’s per-message rate, T-Mobile, AT&T, and Verizon each add pass-through surcharges on A2P traffic — small per-message fees that vary by carrier and message type, and that change over time. A provider should itemize those surcharges separately rather than burying them in a bundled rate; our per-message pricing breakdown walks through the full stack, and the SMS vs MMS comparison covers how the two payload types differ in cost and carrier treatment.
This is why the provider question matters more in messaging than almost anywhere else in telecom. Two platforms with identical features can have very different delivery rates because one has stronger carrier standing than the other. Deliverability is a property of the carrier layer, not the software layer.
Where to go from here
This page is the map; the destinations are covered in depth elsewhere in this series:
- Register your brand and campaigns — A2P 10DLC registration, step by step
- Track rule and fee changes — A2P 10DLC news, updated monthly
- Understand the vetting entity — What is The Campaign Registry?
- Political and advocacy senders — Campaign Verify political SMS vetting
- Send at volume — How to send mass text messages
- Run the operational checklist — SMS compliance checklist
- Understand the plumbing — What is an SMS gateway?
- Evaluate short codes — SMS short codes explained
- Retire legacy paths — Email-to-SMS gateways
- Budget the cost stack — SMS pricing per message
Frequently asked questions
What is A2P messaging?
A2P (Application-to-Person) messaging is any text message sent by software on behalf of a business to an individual’s phone — appointment reminders, delivery notifications, two-factor codes, and marketing texts all qualify. US carriers classify traffic as A2P based on how it behaves (volume, send patterns, template similarity), not on what the sender calls it, and they require A2P traffic to be registered through a sanctioned route: 10DLC registration, toll-free verification, or a short code program. Registered traffic gets preferential routing; unregistered traffic is filtered or silently dropped.
What is the difference between A2P and P2P messaging?
P2P (Person-to-Person) is texting between two individuals — one human, one handset, conversational, and roughly balanced between sending and receiving. A2P (Application-to-Person) is traffic originated by an application or business system, typically high-volume, one-directional, and template-driven. The distinction is behavioral, not about content: a business owner texting one customer from a personal cell is P2P, while an automated “your order shipped” text is A2P. Carriers profile traffic on those behavioral signals and apply A2P registration requirements to anything that behaves like business messaging.
Which A2P route should I use: 10DLC, toll-free, or short code?
10DLC is the default for most businesses — local numbers that carry voice and text on the same DID, registered through The Campaign Registry, with throughput assigned by trust score. Toll-free verified numbers suit national brands and customer-service messaging, using a separate carrier-managed verification track. Short codes handle the highest volumes — hundreds of messages per second versus the 1 to 75 typical of 10DLC — at the highest cost, which limits them to large-scale programs. Start with 10DLC unless you have a specific national-identity or extreme-volume requirement; our short codes guide covers when the upgrade makes sense.
Why are business text messages filtered by carriers?
Because SMS is cheap to send and nearly always read, it became a prime spam channel, and carriers could not distinguish legitimate business messages from phishing at the network level. The A2P registration framework fixes that by requiring senders to verify their identity and declare their use cases up front. Carriers then route registered traffic preferentially and filter everything else — and the filtering is silent, so an unregistered sender’s platform reports “sent” while the recipient gets nothing. Registration through the framework described in our registration guide is the only reliable way through the filters.
Is a text sent from my cell phone to a customer A2P or P2P?
A single conversational text from your personal handset to one customer is P2P. But the classification is behavioral: if you send the same message to dozens of customers, use software to automate sends, or run one-directional notification traffic from a line, carriers will profile that traffic as A2P regardless of the device it came from. Businesses that text customers routinely should register a proper A2P route rather than relying on consumer lines — unregistered business-pattern traffic is exactly what carrier filters target. See our business messaging service for the registered path.
A2P messaging is table stakes for business texting in 2026: pick a route, register, and send from sanctioned infrastructure. SIPNEX provides SMS and MMS messaging on the same DIDs as your voice, with A2P 10DLC registration handled on your behalf and carrier surcharges itemized separately. Set up business messaging or call (833) 665-2220.
Keep reading.
The carrier built by operators, for operators.
FCC-licensed carrier with its own STIR/SHAKEN SP certificate. Operator-owned. SIP trunks built for operators who dial at volume.