TCPA
The Telephone Consumer Protection Act is the US federal law governing automated calls and text messages. It applies to school districts. There is a school-related carve-out, it is narrower than most districts assume, and the gap between the two is where the risk sits.
| Message class | Examples | Consent position |
|---|---|---|
| Emergency | Lockdown, evacuation, early closure for weather, a health emergency | Treated as an emergency purpose; the strongest footing a district has |
| School-related informational | Attendance, conferences, bus changes, grades, testing dates | Generally relies on prior express consent, which the FCC has treated as given when a number is provided to the school for these purposes |
| Transactional to a specific family | Meal balance, a form that needs signing, a nurse callback | Same footing, provided it stays specific and not promotional |
| Promotional or fundraising | Booster sales, third-party photo offers, sponsored content | Prior express written consent territory; keep it off the mass channel entirely |
| Third-party on the district's list | A vendor messaging families using district data | The riskiest thing a district can do with its contact list |
What the carve-out covers, and where it stops
The FCC has addressed school calling directly, and the practical shape of it is this: automated calls and texts to numbers that families provided to the school, for messages closely related to the school's educational mission, sit on solid ground — emergency notifications most solidly of all. That is the basis on which every district in the country runs attendance calls and snow-day alerts.
The boundary is purpose, and it moves without anybody noticing. The same phone number, the same platform, the same sender, and:
- A closure notice is an emergency message.
- An attendance notice is school-related informational.
- A reminder that the yearbook order deadline is Friday is arguably still informational.
- A message about a partner's discounted photo package is marketing, sent to a list assembled for a different purpose.
Districts almost never get into trouble over the first three. They get into trouble when the PTA list, a vendor promotion, or a bond-campaign message goes out through the emergency channel because that is the channel that reaches everyone. None of this is legal advice; it is the boundary worth having your counsel draw explicitly and in writing before somebody draws it for you.
Consent, revocation and reassigned numbers
Three operational obligations follow, and each has a records requirement attached:
| Obligation | The evidence that satisfies it | Common gap |
|---|---|---|
| Consent is documented per number | Source of the number, date captured, purpose it was given for | The number exists in the SIS with no provenance at all |
| Revocation is honoured | A timestamped record of the request and when suppression took effect | An opt-out captured by the front office and never entered anywhere |
| Revocation is accepted on any reasonable channel | A defined intake for STOP, a phone call, an email and a form | Only carrier STOP is captured; a verbal request to the office is lost |
| Reassigned numbers are managed | Regular validation, and prompt retirement of numbers that fail | A disconnected number kept on file for years and then reassigned to a stranger |
The reassignment case deserves attention because it is the one that produces genuine complaints from people with no connection to the district. A mobile number surrendered in 2023 belongs to somebody else now, and that person receives attendance calls about a child they have never met. The defence is hygiene: validate, retire what fails, and keep the record of when you did.
The systems consequence
All of the above collapses into one design requirement. A phone number is not a string. It needs at least two independent pieces of state, and most systems collapse them into one flag and get both wrong:
- Validation state — is this number technically deliverable? Is it a mobile? Did it hard-fail last time?
- Consent state — has this person agreed to receive this class of message, and have they since revoked?
A number can be perfectly deliverable and not consented, or consented and disconnected. Kastr models these separately on every contact point, alongside the source the number came from and its rank, and every change is written to a per-organisation SHA-256 hash-chained audit log that is append-only at the database level. That is the evidentiary half of the answer.
Honest limitation. Storing consent state and enforcing it at send time are two different things. Kastr records consent per contact point today; our audience resolution does not yet filter on it when a broadcast is sent. Until it does, carrier-level STOP is what actually stops SMS. We are stating that because a compliance claim you cannot verify is worth less than nothing.
Questions people actually ask
Are school districts exempt from the TCPA?
Not exempt — accommodated. The FCC has recognised that automated calls and texts closely related to a school's educational mission, sent to numbers families gave the school, sit on solid consent footing, with emergency notifications strongest of all. Promotional and third-party messaging does not benefit from that reasoning.
Does a parent providing a phone number on an enrolment form count as consent?
For school-related messages it is the usual basis, and it is stronger when the form states what the number will be used for. It does not extend to marketing, to third parties, or to message types a reasonable parent would not have anticipated. Record where each number came from and when.
How quickly must an opt-out be honoured?
Promptly, and on any reasonable channel the person uses to make the request — not only a carrier STOP. Districts should treat a revocation as effective immediately in policy and make sure a verbal request at the front office reaches the platform rather than dying on a sticky note.
What happens when a parent's phone number is reassigned to someone else?
The new subscriber starts receiving district messages, and they have every right to complain. The defence is contact-data hygiene: validate numbers regularly, retire numbers that hard-fail, and keep a record of when each check happened. Stale contact data is both a compliance exposure and the main cause of poor reach.
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.