Alerting · Available on Starter+

3am pages should be for things that actually can't wait.

Give any SMS or push contact a daily do-not-disturb window — with overnight wraparound — so alerts inside it stay silent instead of waking someone up.

Start Free → See pricing

Free forever plan, no card required.

Why it matters

Per-contact quiet hours

On-call burnout is rarely caused by one bad night — it's caused by every night carrying the possibility of a page for something that could've waited until morning. Quiet hours draw that line for you, automatically. It's the cumulative effect that wears people down: knowing your phone might buzz at 3am for a monitor that flapped for ninety seconds and recovered on its own is enough to disrupt sleep even on the nights nothing actually happens, because the possibility alone is what keeps you half-listening. Confirmation thresholds cut down on false pages, but they don't eliminate the ones that are real but genuinely not urgent enough to justify waking someone up. Quiet hours handle that second category — the alerts that are worth knowing about, just not worth losing sleep over — by holding them until morning instead. It's a small setting that does a disproportionate amount of good for anyone who's ever been on a rotation. A well-rested on-call rotation responds better to the alerts that actually matter, which is the whole point of cutting the ones that don't.

Per-contact control

Each SMS or push contact sets their own window, in their own time zone — not one setting for the whole org. A distributed team with contacts in different time zones each gets a window that matches when they're actually asleep, rather than one org-wide setting that would be wrong for everyone except whoever set it up. It's a setup that respects the fact that a distributed team doesn't share a single bedtime. Nobody has to coordinate a single shared schedule that doesn't actually fit everyone.

Overnight wraparound handled

A 10pm–7am window works the way you'd expect, across midnight, with no edge-case math. There's no need to think through whether the window logic handles crossing midnight correctly — it just does, the same way you'd expect any calendar or scheduling tool to handle an overnight span without producing a weird off-by-one result. It's one less thing to double-check when setting the window up for the first time. It's one of those small correctness details that's easy to take for granted until it's missing.

Nothing critical is silenced

Email, Slack and webhook contacts are never muted — only SMS and push respect quiet hours. That split is deliberate: SMS and push are the channels that actually interrupt someone physically, while email, Slack and webhooks are channels a team checks on its own schedule anyway, so muting only the interrupting ones is what actually protects sleep without hiding information. The line is drawn around what physically wakes someone up, not around what's technically "important." It's a distinction that holds up well in practice, even if it isn't infinitely configurable.

FAQ

Per-contact quiet hours, answered.

Which alert channels respect quiet hours?

Only SMS and push. Email, Slack and webhook contacts are never muted, so critical integrations still fire even during a contact's do-not-disturb window. That distinction matters because SMS and push are the channels that physically interrupt someone, while the others are ones a team checks on its own terms. Everything else keeps flowing normally, so nothing critical is ever truly silent. It's a deliberate, narrow scope — quiet hours protect sleep, not visibility.

Does the window handle overnight spans correctly?

Yes — a 10pm–7am window works the way you'd expect across midnight, with no edge-case math required on your end. Set the start and end time once and it correctly treats the whole overnight span as quiet, without needing to split it into two separate rules to get the wraparound right. It's exactly the kind of detail that's easy to get subtly wrong by hand and easy to take for granted once it's automatic. It's one less thing to test manually before trusting it.

Can I set a different window for weekends?

Not yet — quiet hours apply the same daily window every day of the week, including weekends. For most on-call setups a single consistent window is close enough, but if weekend sleep schedules genuinely differ from weekdays, that's worth keeping in mind when picking a window that works across both. It's a reasonable trade-off for most teams, even if it isn't the most granular option imaginable. Most teams find one consistent window is simpler to reason about than several different ones.

Get Started

Per-contact quiet hours. Free, starting now.

Start Free →