A2P 10DLC
A2P 10DLC — application-to-person, 10-digit long code — is the framework US mobile carriers use to register and police business text messaging sent from ordinary 10-digit phone numbers.
| Type | Registration | Throughput | Typical use |
|---|---|---|---|
| 10DLC (long code) | Brand + campaign, days to weeks | Moderate, trust-score dependent | Most district messaging |
| Short code | Heavy vetting, 8–12 weeks, expensive | Very high | Large-scale emergency notification |
| Toll-free | Verification, faster than short code | High | Overflow and some notification traffic |
Why it exists and what it requires
10DLC was introduced to deal with the fact that ordinary 10-digit numbers were being used for high-volume commercial messaging with no accountability. Carriers now require that the organisation sending, and the purpose it is sending for, are both registered before traffic is trusted.
Registration has two layers:
- Brand. The legal entity doing the sending, verified against tax identity information. For a district, that is the district.
- Campaign. The specific use case — what the messages are, sample content, how consent is collected, and how opt-out is handled. Different use cases may need separate campaigns.
Both are reviewed. Approval is not instant and is not guaranteed, and the registration determines the throughput and trust score the number receives. Practically, this means a district that decides to switch messaging vendors in July has a registration lead time to plan around, and it is measured in weeks rather than days.
What happens if you skip it
Unregistered A2P traffic on a long code is not blocked with a clear error. It is filtered — carriers silently drop or heavily throttle it. From the sending system's perspective the message was accepted; from the family's perspective nothing arrived. There is frequently no error to investigate.
This is the single most damaging failure mode in school messaging, because it is invisible on both ends until somebody notices that a segment of families never responds to anything. It is also why delivery reporting that counts "sent" as "delivered" is actively misleading rather than merely imprecise.
Ask your vendor two questions. First: does your delivery report distinguish "accepted by the carrier" from "delivered to the handset"? Second: what is our 10DLC registration status, as a date? Both have precise answers and neither should require escalation.
Consent, opt-out and the emergency question
10DLC sits alongside the Telephone Consumer Protection Act (TCPA), which governs consent. The two are often conflated but are separate obligations: 10DLC is carrier policy, TCPA is federal law.
For schools the practical rules are:
- Consent should be recorded, per contact point, not assumed from the existence of a phone number in the SIS. A number that arrived through enrolment paperwork is not automatically consented for all message types.
- STOP must always work, and it must work at the carrier level regardless of what your application does. A family that opts out of a long code has opted out.
- Emergency messaging is treated differently from routine messaging, and most districts run them as distinct message classes for exactly that reason. This is why platforms separate emergency sends, which bypass channel preferences and quiet hours, from everything else.
The design consequence is that a contact point needs two independent pieces of state: whether the number is deliverable, and whether it is consented. Systems that collapse those into one flag get both wrong.
Questions people actually ask
Do school districts need 10DLC registration?
If the district sends application-generated SMS from a 10-digit US number, yes. The registration is done by or on behalf of the district as the brand, with campaigns covering the message types being sent. Short codes and toll-free numbers follow different processes.
How long does 10DLC registration take?
Brand verification is usually quick; campaign approval is the variable part and typically runs from several days to a few weeks depending on the use case and how clearly consent and opt-out are documented. Plan the lead time into any vendor change rather than discovering it at cutover.
What happens to unregistered SMS traffic?
Carriers filter it — silently dropping or throttling messages. The sending platform generally records the message as accepted, so the failure is invisible unless your delivery reporting distinguishes carrier acceptance from handset delivery.
Does TCPA apply to school messages?
TCPA governs consent for automated calls and texts, and schools are not blanket-exempt. Emergency notifications are treated differently from routine and promotional messaging. Record consent per contact point, honour opt-outs at the carrier level, and take specific legal advice for your state rather than relying on a vendor's summary.
One price. Every feature. Locked for three years.
$3.50 per student per year under 5,000 students. No tiers, no add-on modules, no per-message fees. Published on the site because you should not have to book a call to learn a price.