10DLC Registration for School Districts
If your district's texts are arriving for some families and silently vanishing for others, this is almost certainly why. A2P 10DLC is the carrier registration regime for application-to-person traffic on ordinary ten-digit numbers, and unregistered or mis-registered traffic is not rejected loudly. It is filtered quietly, and your platform reports it as sent.
| Entity | Brand type | EIN on file must match | Vetting | Typical lead time | Common failure |
|---|---|---|---|---|---|
| Public school district | Government | The district's IRS-registered legal name | Government vetting path; may need documentary evidence | 2–6 weeks | Submitting the trading name, not the legal name |
| County office of education / intermediate unit | Government | The office's own EIN, not a member district's | Government path | 2–6 weeks | Registering on behalf of member districts under one brand |
| Public charter school | Depends on incorporation | Whichever entity holds the EIN | Government or non-profit depending on structure | 2–6 weeks | Charter management org name vs school name mismatch |
| Charter management organisation | Non-profit | The CMO's EIN | Non-profit path | 2–5 weeks | One campaign for schools with different opt-in flows |
| Private or independent school | Non-profit or standard | The school's EIN | Standard vetting | 1–4 weeks | DBA name on the submission |
| Diocesan school system | Non-profit | The diocese or the school, consistently | Non-profit path | 2–5 weeks | Mixing diocese brand with per-school sender identity |
| Regional consortium buying jointly | Each member registers separately | Each member's own EIN | Per member | Runs in parallel | Assuming the consortium can register once for all |
Lead times are what districts and their carriers commonly report; they move, and they lengthen in August. The load-bearing point is the middle column. Vetting compares the name you submit against authoritative business records, and a district that trades as "Riverton Schools" while its IRS record says "Riverton Unified School District No. 4" fails on a string comparison and then waits three weeks to find out.
The sequence, and where districts stall
- Get the legal name exactly right. Not the name on the website. The name on the IRS EIN assignment letter, character for character, including the number, the abbreviation and the punctuation.
- Submit the brand. Legal name, EIN, address, entity type, a website that resolves and describes the organisation, and a named contact with an email at the district's own domain.
- Vetting produces a score. The score drives what throughput you can be assigned and which campaign types you may run. A government-entity brand that verifies cleanly generally scores well; the failures are almost always identity mismatches rather than judgements about the organisation.
- Submit the campaign. This is where the use case, the sample messages, the opt-in description, the opt-out language and the help response are declared. Schools generally register informational or notification-style use cases; declare what you will actually send.
- Carrier review. Each major carrier reviews independently and can reject or throttle independently. It is normal for one carrier to approve while another queries.
- Throughput assignment. You are given a messages-per-second rate that determines how long a district-wide blast takes.
Districts stall at step one and step four. Step one because nobody in the technology department has the EIN letter and the business office does not know why they are being asked. Step four because the sample messages submitted are aspirational rather than real, and the campaign is later found to be carrying traffic it was not registered for.
The EIN mismatch checklist
Six ways a district's name fails vetting, and the fix for each:
- Trading name submitted instead of legal name. "Riverton Schools" against a record reading "Riverton Unified School District No. 4". Fix: use the EIN assignment letter as the single source of truth.
- District number omitted or formatted differently. "No. 4" against "Number 4" against "#4". Fix: copy the punctuation exactly.
- Abbreviation expanded or contracted. "USD" against "Unified School District". Fix: match the record, not the letterhead.
- Address is the school site rather than the registered administrative address. Fix: use the address the IRS and the state hold.
- Website does not resolve, redirects, or is a portal login. Vetting looks at it. Fix: submit the public district homepage.
- Contact email on a vendor or personal domain. Fix: use an address at the district's own domain.
Before anyone submits anything, get three documents in one place: the IRS EIN assignment letter, the state entity registration if your state maintains one, and the district's current W-9. If the name is not identical across all three, resolve that first — the registration will not fix it for you.
Throughput arithmetic, applied to a real closure blast
Throughput is expressed in message segments per second and it is the number that decides whether a closure message is an event or a trickle. Work it against your own peak: a 05:15 closure to 12,000 families, one segment each in English.
- At 1 segment/second: 12,000 seconds, or three hours and twenty minutes. The last family hears at 08:35, long after the buses would have run. Unusable.
- At 10 segments/second: 20 minutes. The last family hears at 05:35. Workable but uncomfortable, and it means the households at the end of the queue are the ones making the wrong decision.
- At 60 segments/second: 3 minutes 20 seconds. Operationally fine.
- At 100 segments/second: 2 minutes. Comfortable.
Two multipliers districts forget. First, segments, not messages: if 40% of your households receive an accented Spanish message that runs to three segments, your 12,000-message send is not 12,000 segments, it is roughly 16,800, and the blast takes 40% longer. That is a throughput consequence of serving Spanish-speaking families that nobody in this category writes down. Second, bilingual households frequently receive both, which doubles their contribution again.
Rework the same send for a district that is 40% Spanish-speaking with accented Spanish: 7,200 English segments plus 4,800 households at three segments each, so 21,600 segments in total. At 10/second that is 36 minutes rather than 20.
Fees, and what to put in the budget
Three cost layers, all of which appear on a district invoice and none of which most districts model in advance:
- One-time brand registration and vetting. A single charge, typically in the low tens of dollars for registration with an additional vetting charge. Not material at district scale, but it needs a purchase order and that is where a week goes.
- Per-campaign monthly fee. Charged for each registered campaign, every month, whether or not you send. This is the argument for one well-scoped campaign rather than six narrow ones. Districts that register a campaign per school pay for a campaign per school, permanently.
- Per-message carrier surcharges. Charged per segment, on top of whatever your platform or carrier charges. Small individually and the largest line at volume, because it scales with segments — which means it scales with your Spanish traffic faster than with your English traffic.
Model it as: (segments per year) × (carrier surcharge + carrier rate) + (campaigns × monthly fee × 12) + one-time vetting. For a 4,000-student district sending 30 district-wide messages a year plus daily absence notifications, the segment count is the dominant term and the campaign fees are noise. For an 18,000-student district the same is true, more so. The mistake is budgeting per message rather than per segment.
Said plainly: Kastr's own 10DLC brand and campaign registration is not complete. We are pre-launch, registration has a two-to-six week lead time, and we are not going to tell you we hold something we do not. This page is subject expertise, not a capability claim. What Kastr does have that is relevant: every contact point carries a validation state and a consent state as separate fields, with its source and rank, which is the data you need to answer a carrier or a counsel question about where a number came from and what the household agreed to. When our registration is complete it will appear on the trust page with a date on it, like everything else.
Questions people actually ask
Does a school district need 10DLC registration to text parents?
If you send application-to-person traffic from a standard ten-digit US number, yes in practice. Unregistered traffic is subject to filtering and reduced throughput, and the filtering is silent — the platform records a send and the family receives nothing. Short codes and toll-free numbers sit under different regimes with their own verification requirements.
How long does 10DLC brand and campaign registration take for a district?
Commonly two to six weeks end to end, and longer in August when everyone is doing it at once. The variable is not the platform, it is identity verification: a district whose legal name matches its IRS record cleanly moves fast, and one with a name mismatch spends the time in a resubmission loop. Start in spring for an autumn launch.
Why are our school text messages being filtered or blocked by carriers?
In order of likelihood: unregistered or mis-registered campaign; traffic that does not match the registered use case; public URL shorteners in the message body; sudden volume spikes from a long code; or content patterns that resemble commercial messaging. Check registration status first, then the link handling, then whether the campaign's declared samples resemble what you actually send.
How much does 10DLC cost a school district per year?
Three layers: a one-time brand registration and vetting charge, a monthly fee for each registered campaign, and a per-segment carrier surcharge on every message. At district volume the surcharge dominates, so budget per segment rather than per message — and remember that accented Spanish messages are two to three segments each, which makes the surcharge scale disproportionately with the families you most need to reach.
Does 10DLC apply to emergency notifications?
10DLC is a carrier registration regime, not a consent regime, and it applies to the traffic regardless of its purpose. An emergency message from an unregistered brand can still be filtered. This is why registration is an emergency-preparedness task rather than a marketing one, and why throughput tier belongs in your emergency operations plan next to the blast-completion time.
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.