Notification triage: tier your channels so urgent still gets through
Most notification advice fails in the same place. It tells you to silence everything, and the first time a genuinely urgent message sits unread for three hours, the whole system gets switched off and the badges come back. The problem was never the muting — it was that every message arrived on the same tier. A newsletter, a teammate's question, and a client emergency all produced the same buzz, so the only safe setting was “everything on.” Triage fixes the tiers first. Once each channel has a job and a response window, silencing the lower tiers stops being a gamble.
The three tiers: what each channel is for
Sort channels by how fast a message on them can actually go bad, not by which app it lives in. Three tiers cover most jobs:
Tier 1 — the escalation channel (minutes). One channel, agreed in advance, is allowed to interrupt you: a phone call, or a direct message in your chat tool. It is reserved for the short written definition of urgent your team settles on — someone is blocked now, a customer is affected now, money or safety is moving now. Everything else is forbidden from this tier, including “a senior person sent it.” Seniority is not urgency.
Tier 2 — chat (same day, at set windows). Team chat is where work questions live. Notifications stay on for direct mentions only; busy channels are muted by default, which is the setup notification guides for chat tools recommend — mute high-traffic channels and enable alerts only for direct mentions. You read chat fully at published windows, a few times a day, and answer in a single pass.
Tier 3 — email (batched, twice or three times a day). Email is the slowest channel and should be treated that way. The evidence for batching it is unusually direct: in a within-subjects experiment, Kushlev and Dunn (2015) had 124 adults limit email checking to three times a day for one week and check freely in another; daily stress was significantly lower in the limited week, and the lower stress predicted higher well-being. Email's own norms support the batching — colleagues can generally wait two to three hours for a routine email response without business impact, precisely because genuinely urgent matters travel by other channels. Two to three scheduled processing windows a day — morning, midday, late afternoon — is the range that guidance lands on for most professionals.
Setting it up: the procedure
- Write the urgency definition first. One or two sentences, concrete enough that a new hire could apply it: what events qualify for Tier 1, and — just as important — what does not. If the team cannot define it, the tiers will collapse back into “everything is urgent.”
- Assign each tool to a tier and set its notifications to match. In chat: mentions and direct messages notify, channels do not. In email: notifications off entirely, or on only for a small VIP list of senders — combining a VIP designation with filtering is the standard recommendation for keeping urgent mail visible while routine mail stays silent. Automated mail (alerts, digests, system notices) gets filtered to a separate view so it never competes with human mail.
- Set the windows and publish them. Pick two or three chat-and-email windows and put them where people can see them: your chat status, your email signature, the team norms note. In Slack, for example, you can set a notification schedule for the hours you allow alerts, and pause notifications outside them; colleagues see a snooze icon next to your name, so the pause is visible rather than mysterious.
- Wire the escalation path. Tier 1 needs a mechanism, not just a promise. In Slack, a sender can override a paused notification once per day to flag a genuinely urgent direct message, and a VIP list lets specific people's messages through even while notifications are paused. The equivalent on other tools is the phone: the agreement is that a real emergency arrives as a call, twice if the first is missed.
- Run it for two weeks, then adjust the windows — not the tiers. The UBC researchers found most participants struggled to hold a three-checks-a-day limit at first, even as their stress fell. The friction is normal and temporary; the fix is moving a window, not reopening the floodgates.
The agreement is the system
Settings are private; triage only works when it is a team agreement. Three sentences, pinned where the team works — notification guidance for teams suggests exactly this: a simple norms document in the team space covering response windows and escalation. Sentence one: the windows (“chat and email are answered at 10:30, 13:30 and 16:00”). Sentence two: the response promise per tier (“Tier 2 questions get a same-day answer; Tier 3 by the next window after that”). Sentence three: the escalation rule (“if it cannot wait for the next window, call — a call always means drop everything, so use it only for the definition above”). One consulting team that limited chat checks to two windows a day and muted all non-mention alerts found response quality improved and end-of-day fatigue eased — the windows made replies better, not just later.
The agreement also protects you politically. A person with published windows who answers reliably inside them reads as dependable. A person who replies instantly for a week, then vanishes into a deadline, reads as flaky — even with the same average response time. Predictability is what the team actually experiences as responsiveness.
When an urgent message gets missed anyway
It will happen once. Treat it as a system test, not a verdict. Ask two questions. Did the message arrive on the wrong tier — someone emailed an emergency? Then the agreement failed, not the muting: restate the escalation rule, with the incident as the example. Or did it arrive on Tier 1 and still get missed — the call went to a phone in another room? Then the mechanism needs a backup: a second named person, or the override feature on the chat tool. What you do not do is turn every notification back on. A system that survived a miss and got repaired is stronger than the always-on default, which “works” only by taxing your attention all day, every day.
Check it on yourself: after two weeks, count how many Tier 1 interruptions actually met the written urgency definition. If most did, the system is calibrated. If most were ordinary questions wearing an emergency costume, the definition — not your settings — is the thing to renegotiate.
Frequently asked questions
Won't people think I'm ignoring them? Only if the windows are secret. Published windows with a kept promise read as reliability; it is unexplained silence that reads as ignoring.
What if my manager expects instant replies? Then the negotiation is about Tier 1, not about everything: offer the escalation channel and the windows, and put the manager on the VIP list so their messages always notify. Instant access for one person is cheap; instant access for every app is the tax you were paying.
How many windows is right? The research-backed anchor is three checks a day for email; chat usually wants the same windows or one more. Fewer than two windows a day makes Tier 2 promises hard to keep; more than four and the batching benefit mostly evaporates.