Do not disturb needs an exception channel
Aliases: focus allowlist · breakthrough contacts · DND exceptions
What it is
Do Not Disturb (Focus) is a window the user deliberately closes against interrupts. If that window also blocks "the school is calling," an alarm they set, or "your account just signed in," people will refuse to enter it, or will abandon it after one missed critical event. An exception channel is a small, predeclared set of sources that may still break through—not a hole for high-tier marketing during quiet hours.
This is about the focus mode itself needing a hole. It is not a product's night-time send policy, and not how held items later appear in history.
Why it happens
The value of the mode is predictable quiet. People use it only if quiet will not cause irreversible loss. With no exception, that premise fails: one miss brands the mode as dangerous. The later strategy is never to enter, or to enter and still watch the phone face-down. The name remains; the mode does not.
Exceptions must stay narrow or the mode decays into ordinary notification. Holes that work are usually tied to a relationship or intent the person already expressed: starred contacts, repeating alarms, navigation or a timer they started, security events from the system. Sender-declared "urgent" must not become a hole on its own, or business teams will stuff promotions into the urgent field.
Studying it
Compare a total block with a configurable-exception focus mode: days the mode is actually on, why it is turned off mid-window, and whether exception events are later judged worth it.
Independent variables: whether exceptions exist, whether the user or the system chooses them, whether sender-declared urgency counts. Dependent variables: enable rate and dwell, early exits caused by fear of missing, later endorsement of exception events.
Labs struggle to manufacture the real loss of "missed once, never again." Diaries and product logs are closer: after the first miss of a class while in-mode, does that person's enable rate drop. Exception click-through is not success—exceptions should be rare; success is that the mode is still dared.
Where it stops holding
On shared devices the allowlist may belong to someone else (a parent's stars are not a child's). An on-call account's exceptions are almost "every work channel"; focus is then meaningless for work apps and should apply only to personal ones. Exceptionless settings also exist: exam lock, sterile theatre—miss cost is carried by the institution, not by a personal mode. Legally required public alerts often sit outside focus; products must not turn them into a user-toggled exception.
Applying it
- When focus turns on, show the exceptions: at least starred contacts, with the person's own alarms and system security events admitted by default.
- Sender-marked "urgent" must not pierce on its own; the breakthrough list is objects the user has named.
- Mark exception deliveries as "delivered during focus" so the mode is not read as broken.
- Verify with a day in-mode and two arrivals: a starred call should sound, a routine promotion should not. If the promotion gets in, the hole is too wide; if the star does not, the mode will be abandoned in real life.