What Is A2P Messaging? Definition, 10DLC Rules & Real Examples
A2P (Application-to-Person) messaging is any SMS originated by software — a CRM, marketing platform, or notification service — and delivered to an individual mobile subscriber. In the US, A2P traffic must be registered under 10DLC, regardless of volume. Automation, not volume, is what triggers A2P classification.
Key takeaways
- A2P = software → person. P2P = human → human, manually typed.
- Templates, scheduling, and fan-out automatically convert traffic to A2P.
- All A2P SMS to US carriers requires 10DLC registration with TCR.
- Carriers actively detect and re-classify A2P-on-P2P infrastructure.
- A2P enables higher throughput, deliverability, and traceability — when properly registered.
A2P Definition
A2P (Application-to-Person) describes SMS or MMS messages that originate from an application — software, a workflow, an API call — and are delivered to an individual mobile subscriber.
Examples include order confirmations from Shopify, OTP codes from Auth0, appointment reminders from a CRM workflow, and marketing blasts from Klaviyo. Even a single templated reminder sent automatically by your CRM is A2P.
A2P vs P2P: The Difference That Matters
P2P (Person-to-Person) is genuine 1:1 conversation between two humans, typed manually in real time. Think iMessage between friends or a salesperson texting one client from their personal cellphone.
A2P is anything else: anything templated, scheduled, automated, fanned out to a list, or sent through an API.
The boundary is automation, not volume:
- 30 templated appointment reminders/day = A2P.
- 1 manually-typed reply to a customer from a CRM inbox = arguably P2P, but only if the CRM truly sends without templates or scheduling.
- "Conversational" messaging that uses saved snippets or quick-replies = A2P.
Carriers profile traffic patterns; if your "P2P" line shows templating signatures, fan-out, or sub-second send latency, they will re-classify and suspend it.
Why A2P Classification Matters
Three reasons:
- Compliance: A2P traffic to US numbers must be registered under 10DLC. Sending A2P on unregistered infrastructure is a carrier policy violation that can suspend your numbers and trigger TCPA exposure.
- Deliverability: Properly registered A2P enjoys higher throughput, lower spam filtering, and clearer error codes. Unregistered A2P gets silently filtered.
- Cost: Carriers add per-segment surcharges to A2P traffic. Trust score (set by your TCR vetting tier) directly determines those surcharges.
A business operating "P2P" workflows on consumer phone lines almost always violates carrier ToS once volume creeps up.
How to Run A2P Messaging Compliantly
- Register your brand and campaign(s) with The Campaign Registry through your CSP (Twilio, Bandwidth, GHL, etc.).
- Match the campaign use case to your actual traffic — Marketing, Customer Care, 2FA, Account Notifications, Mixed.
- Run a public opt-in URL that demonstrates TCPA-grade consent: unchecked SMS box, brand name, "Msg & data rates may apply", STOP/HELP language.
- Capture consent proof — timestamp, IP, exact disclosure, ideally session replay — for every opt-in.
- Honor STOP automatically and maintain a per-brand suppression list checked before every send.
- Stay within carrier hours (8 a.m.–9 p.m. local) and respect message-frequency disclosures.
Common A2P Mistakes
- Treating low volume as P2P: 50 templated messages/day from a CRM is still A2P.
- Mixed use cases on one campaign: blending marketing into a 2FA campaign gets the campaign suspended.
- No opt-in URL during TCR submission, or one that's hidden behind a login.
- Consent records that can't be tied to a specific message recipient.
- Not honoring STOP across all CRMs / channels that share the consent.
Examples
Workflow trigger: appointment booked → CRM sends "Hi {{first_name}}, your appointment is confirmed for {{time}}. Reply STOP to opt out."Templated, automated, originated by software — this is A2P regardless of the per-day volume.
Sales rep manually types in iMessage: "Hey Maria, do you want me to swing by tomorrow at 3?"
True 1:1, manually typed, no template, no fan-out — genuine P2P. Most CRM 'conversation' workflows do NOT qualify.
Frequently asked questions
Related reading
Related glossary terms
10DLC (10-Digit Long Code) is the US carrier-mandated framework for sending Application-to-Person SMS from local 10-digit numbers, requiring brand and campaign registration with The Campaign Registry.
In SMS, P2P (Person-to-Person) messaging is a true 1:1 conversation typed manually by a human. P2P traffic is exempt from 10DLC registration, but the definition is narrow and routinely audited by carriers.
The Campaign Registry is the central authority that vets and approves brand and campaign registrations for 10DLC SMS in the United States.