A2P vs P2P Messaging: What Actually Separates Them

There is a claim circulating in the business-messaging space that sounds convincing and is expensive to believe:

Route your SMS through a real SIM card in a real phone, and carriers classify it as P2P — person-to-person — so A2P rules and 10DLC registration do not apply.

It is wrong. We repeated a version of it on this site until recently, which is part of why this post exists.

Where the line is actually drawn

A2P — Application-to-Person. A software system decides what to send and when. The recipient is a person; the sender is a program.

P2P — Person-to-Person. A human composes a message to another human, one at a time.

The distinction is about authorship, not transport. It does not matter whether the message exits through a carrier gateway, an aggregator, or a SIM card in a device on a desk. If an application decided to send it, it is A2P.

This is not a grey area that clever architecture resolves. A booking system sending a reminder is A2P whether that reminder leaves via Twilio or via a phone plugged into a Mac.

Why the myth is appealing

Because the observable traffic can look similar. A message from a consumer SIM arrives at the carrier looking, at first glance, like an ordinary personal text. At low volume, from one number, nothing obviously distinguishes it.

The mistake is assuming carriers only look at individual messages. They look at patterns over time — volume, recipient diversity, reply rates, timing regularity, content repetition. A business workflow running on a consumer line produces a distinctive shape, and that shape is what triggers review.

What it costs to be wrong

This is not a technicality that gets quietly tolerated.

Since February 2025, the major US carriers — AT&T, T-Mobile, Verizon — block SMS from unregistered 10-digit numbers outright. Not filter, not throttle. Block.

T-Mobile fines $1,000 per incident for "10DLC evasion." The violation is named. Using a consumer line to avoid A2P registration is a category carriers anticipated and priced.

Content violations run up to $10,000 each.

And the practical failure mode arrives before any fine does: a consumer line running business volume gets its throughput cut or the number blocked. The business messaging stops working, usually at the worst possible moment, with no appeal path because there was no registration to appeal against.

The clearest statement of the pattern: a business running P2P-shaped workflows on consumer lines almost always breaches carrier terms of service once volume rises. Not "may". Almost always.

Where iMessage genuinely differs

One thing the myth gets right, for the wrong reasons.

iMessage never touches carrier infrastructure. It routes over the internet through Apple's servers. There is no carrier gateway, no SMS network, no 10DLC framework that could apply to it — the same way email is not subject to SMS regulation.

This is not a loophole or a classification argument. It is a different network.

Which means the honest summary is more nuanced than either camp usually admits:

• iMessage: no carrier involvement, no 10DLC, genuinely exempt
• SMS: A2P if software composed it, regardless of hardware, and registration applies

Anyone telling you their SMS avoids 10DLC through clever routing is describing a liability, not a feature.

What compliance actually looks like

A2P registration involves brand registration, campaign registration, carrier vetting and ongoing compliance. It takes days to weeks and costs money.

There are two legitimate ways to deal with that.

Register yourself. Necessary if you need throughput under your own brand, or operate in a regulated industry where the audit trail matters.

Use a platform that has registered. The requirement does not disappear — it moves. The platform holds the registration; you inherit compliant delivery without filing anything. This is how senderZ works: SMS goes over 10DLC infrastructure we have already registered.

The distinction that matters when evaluating a vendor: "no 10DLC needed" and "no 10DLC needed from you" are very different claims. The first is a red flag. The second is a service.

Why we corrected our own copy

We previously described senderZ's SMS as P2P-routed and therefore exempt. It was wrong, and it was wrong in the direction that flattered us, which is the kind of error worth being loud about fixing.

Business messaging is A2P. We register for it. What you skip is the paperwork, not the requirement.