Slack Is Not a Pager (and Your Alerts Know It)

Every team tries it. Wire the store, the monitoring, the forms, the deploy bot into a #alerts channel, and for a while it feels like a control room. Then one Tuesday the site goes down for two hours, and the postmortem finds the alert exactly where it was sent: in #alerts, unread, seventeen messages above a GIF.

Nobody did anything wrong. Slack did exactly what Slack does. The mismatch is that alerting needs three properties a chat channel structurally cannot provide.

---

Property 1: a specific person must be responsible

A channel notifies everyone and therefore no one. When forty people see an alert, each one reasonably assumes someone closer to it will handle it — the bystander effect, now with emoji reactions. Paging works in the opposite direction: an alert has one owner at a time, that owner is named, and if they don't respond, responsibility moves — explicitly — to the next person. Slack has no concept of "this message is yours until you say otherwise."

Property 2: it has to be loud enough, at the right time, and only then

Slack notifications are tuned for conversation: batched, muted on mobile by default for channels, silenced by Do Not Disturb, softened by "you have 14 unread channels." That's the right design for chat — nobody wants their phone screaming about lunch plans. But it means the urgent alert gets the same treatment as the lunch plans. Pagers invert the priority: routine things stay quiet (quiet hours, normal priority), and the urgent tier is engineered to break through — a distinct sound, on the lock screen, until acknowledged.

Property 3: silence must escalate

The alert that matters most is the one nobody saw. In Slack, an unread message is just… unread, forever, indistinguishable from one that was handled. A pager treats silence as the failure it is: no acknowledgement in five minutes → the alert climbs to a backup → then to the owner → and the whole chain is recorded. Acknowledgement isn't a courtesy; it's the signal that stops the escalation, which is what makes "someone's on it" a fact rather than a hope.

What Slack is actually for

Discussion. Once the alert has an owner and the fire is being fought, Slack is the best place on earth to coordinate: threads, screenshots, "I'm rolling back," the postmortem doc. The right architecture keeps both: the pager decides that someone owns the problem; the channel is where they talk about it. Many teams post the acknowledged alert into Slack automatically for exactly that reason — visibility for the room, ownership from the pager.

The honest test

Ask one question about your #alerts channel: if the site went down at 2 a.m. and the on-call person's phone was face-down on a nightstand, who would find out, and when? If the answer involves the word "hopefully," the channel isn't a pager — it's a log with a friendly interface.

FlowAlert exists for teams that want the three properties without adopting an enterprise incident suite: alerts routed to one named person's phone, acknowledgement on the record, escalation on silence, at a flat price for the whole team — and yes, it'll happily post the result into Slack, where the conversation belongs.