Alerts that go out when they should

One alert too many, and you stop reading them. Alert rules serve a single purpose: that every message that arrives deserves to be read.

The rules

• Confirmation: require several failures in a row before alerting, so a network hiccup wakes nobody.
• Quiet hours: a window, in your time zone, when only the pages that sell still ring.
• Minimum delay, working hours, severity by page type, grouping: four more rules, each on its own switch. A payment page always comes first.
• Muting a URL: silence one specific page for the length of a job.

Maintenance

A maintenance window takes three gestures: click the day on the calendar, where windows already planned are marked; choose the start time and a length — 30 min, 1 h, 2 h, 4 h or the night —; a sentence reads the window back before setting it (“Tuesday 22 September, 22:00 to 23:00”). During the window, alerts stay quiet; before it starts, the status page announces it rather than showing an outage on the hour.

Once for the whole workspace

The workspace's alert settings — quiet hours and their time zone, number of confirmations — apply to every new project. And each member can set their presence (available, or away until a date, with their alerts redirected to the team meanwhile) and sign with their name the line that closes their alert emails.