Mass notification system
A mass notification system sends a single message to a large recipient group across multiple channels at once — typically SMS, voice, email and mobile push — and reports back on what actually arrived.
| Channel | Strength | Weakness | Typical cost driver |
|---|---|---|---|
| SMS | Highest open rate, fastest | 160-char segments; needs 10DLC registration | Per segment, per recipient |
| Voice | Reaches landlines and non-smartphone households | Slowest; often ignored | Per minute |
| Long-form, attachments, effectively free | Low open rate; spam filtering | Negligible | |
| Push | Free, instant | Requires an installed app and permission | Negligible |
What separates a real one from a bulk sender
Any tool can send a lot of messages. The properties that matter in a school context are mostly about what happens when things go wrong:
- Audience derived from the roster, not a list. A saved recipient list is stale the moment a student withdraws. The audience should resolve against current enrolment at send time.
- Per-family language. Translation applied per recipient from their stored preference, not one message in one language with a translate button.
- Channel preferences that are honoured — except in emergencies. Routine messages respect what a family asked for; emergency messages deliberately do not.
- Quiet hours, with the same emergency exception.
- Failover. If SMS fails terminally, the system should try voice rather than record a failure and stop.
- Idempotency. A retry after a partial failure must not send the same family the same message twice. This sounds academic until an emergency send double-fires at 6am.
- Honest reporting. Per-channel, per-family, distinguishing carrier acceptance from delivery. See true reach.
Emergency versus routine
These are different products wearing the same interface, and conflating them causes real harm in both directions.
An emergency message should bypass per-family channel preferences and quiet hours, prefer the fastest channel, fail over aggressively, and be gated behind a specific permission so that not everyone who can send a newsletter can trigger a lockdown alert. Districts also typically want it audited — who sent it, when, to whom, on what authority.
A routine message should do none of that. Overriding preferences for a picture-day reminder is how families opt out of everything, and an opted-out family is one you cannot reach in the actual emergency.
The costly mistake. Districts that route routine traffic through the emergency path train families to ignore the emergency path. The channel that always interrupts stops being the channel that means something.
Cost, and why it should be visible before you send
SMS and voice are metered; email and push are effectively free. That means the cost of a send is driven almost entirely by two choices made in the composer: which channels are selected, and how long the message is.
Message length is the part people miss. SMS bills per segment, and a message that runs a few characters past a segment boundary silently doubles its cost across the whole recipient set. At district scale that is a meaningful number for a sentence nobody needed.
Very few platforms show cost before sending, which is why cost discipline in this category is usually retrospective and usually a surprise. Showing a live per-channel estimate as the sender types turns it into a design decision instead of a line item.
Questions people actually ask
What is the difference between a mass notification system and an emergency alert system?
Usually the same platform with a different message class. Emergency sends bypass channel preferences and quiet hours, prefer the fastest channel, fail over aggressively, and sit behind a separate permission. Routine sends should do none of that.
How much does it cost to text every family in a district?
It scales with SMS segments and recipients. A single-segment SMS to 5,000 families is a small number; the same message running to two segments doubles it. Voice is billed per minute and is materially more expensive. Email and push are effectively free.
Do schools need consent to text parents?
Consent should be recorded per contact point rather than assumed from a number appearing in the SIS, and opt-outs must be honoured at the carrier level. Emergency messaging is treated differently from routine. Take specific legal advice for your state.
What should a school mass notification system report?
Per-channel and per-family outcomes, distinguishing carrier acceptance from confirmed delivery, with queued messages excluded from the denominator — plus a list of families not reached at all, which is the only part you can act on.
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.