Quiet hours
Quiet hours are the time window during which a messaging platform will not deliver, holding messages until the window opens. They exist because the alternative is a phone call at 04:50 to every household in the district, which is a local news story roughly every winter.
| Window | Source | Applies to |
|---|---|---|
| 8:00–21:00 recipient local time | Federal telemarketing rules | Strictly, telemarketing; widely adopted by districts as the default courtesy floor |
| Narrower state windows | State consumer-protection statutes | Several states set tighter hours or stricter weekend rules; check your own |
| Typical platform default | Vendor configuration | Commonly 21:00–07:00 as a hold window for routine traffic |
| Board or district policy | Local | Usually the binding one in practice, and usually stricter than the law |
| Emergency | Exception in all of the above | Genuine emergencies, narrowly defined and specifically authorised |
The three ways districts send at 4am by accident
Nobody sets out to call 6,000 households before dawn. It happens through a mechanism, and there are three of them.
| Trap | How it happens | Fix |
|---|---|---|
| Server timezone, not local time | The platform holds until 07:00 UTC, which is 01:00 Central | Evaluate the window in the recipient's local time and confirm which clock the vendor uses |
| Cross-boundary districts | Families live across a state or time-zone line; area codes lie about where people actually are | Use the district's declared timezone as the governing clock and state that policy publicly |
| The snow-day queue | A message composed at 04:30 is queued, the window releases it at 07:00, and by then school has already been cancelled for two hours | Decide in advance that closure decisions are emergency-class, and make the 05:30 send a deliberate authorised act |
| Daylight saving | A recurring schedule set in local time drifts by an hour twice a year | Store schedules with a timezone identifier rather than a fixed offset |
| Retry storms | A failed send retries hours later, outside the window nobody re-checked | Re-evaluate quiet hours at delivery time, not at composition time |
The last one is the subtle one and the most common in production systems: quiet hours checked when the message is composed rather than when the worker actually attempts delivery. A retry queued at 20:55 and attempted at 21:40 has escaped a window that was technically enforced.
Who should be allowed to override, and what should be recorded
Every district needs an override. Weather closures, a lockdown, a water main under the bus loop — these do not respect a 07:00 window, and a platform without an override is a platform that will be worked around with a phone tree.
The governance question is not whether to have one but who holds it and what happens when it is used:
- The permission should be separate from the ability to send. Everyone who can write a newsletter should not be able to wake the district.
- It should be a small named list — superintendent, a designated deputy, the safety or operations lead, the communications director. Roles, and a real off-hours contact for each.
- Every use should be logged immutably with who, when, to whom, on what authority and with what justification text.
- Every use should be reviewed afterwards, against one question: would a 07:00 send have produced a materially worse outcome? If the honest answer is no more than twice a year, the override is being used correctly.
In Kastr the default hold window is 21:00 to 07:00, bypassed only by an emergency-flagged send, and the emergency flag is gated on a specific capability rather than on being an administrator. Emergency sends also bypass per-family channel preferences. Every action lands in a per-organisation, append-only, SHA-256 hash-chained audit log, so the after-action review has a record that nobody can tidy up.
The cultural cost of getting it wrong
Quiet hours look like a technical setting and behave like a trust policy. A district that calls at 05:00 for a two-hour delay teaches families that district calls arrive at unreasonable hours. Some of them silence the number. A subset of those will not hear the call that matters.
That is the same mechanism described on opt-out and STOP handling, and it compounds: every unnecessary interruption spends a little of the attention you are holding in reserve for a real event. The channel that always interrupts stops meaning anything.
A workable rule of thumb. Publish your windows to families, in the enrolment packet and on the website: routine messages between these hours, emergencies at any hour. That single sentence does two useful things — it sets an expectation you can be held to, and it makes an off-hours message meaningful precisely because it is rare.
Then hold to it for the boring cases. The discipline is not in the emergency; it is in the Tuesday evening when somebody wants the reminder to go out tonight because they will forget tomorrow.
Questions people actually ask
What hours can a school legally call or text parents?
Federal telemarketing rules set an 8:00 to 21:00 window in the recipient's local time, and several states are stricter. School-related messaging is treated differently from telemarketing, but most districts adopt the same window as a courtesy floor and set policy tighter. Confirm your own state rules with counsel.
Whose timezone applies when a family lives across a state line?
Practically, the district's declared timezone is the governing clock, and it should be stated as policy. Area codes are unreliable indicators of where anyone lives. What matters more is that the platform evaluates the window at delivery time rather than at composition time.
Should emergency alerts ignore quiet hours?
Yes, for genuine emergencies — that is what the exception is for. The controls that keep it honest are a narrow definition of emergency, a separate permission held by a short named list, an immutable log of every use, and a review afterwards asking whether waiting until morning would have been worse.
Who should be allowed to override quiet hours?
A small, named group by role rather than by seniority: superintendent, a designated deputy, the safety or operations lead, the communications director. The permission should be separate from ordinary send rights, so that the ability to publish a newsletter is not the ability to wake the district.
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.