Know who an outage hit, and what to tell them

Supahelp matches the incident to your customers, then drafts the update for your approval before the tickets pile up.

USE CASE · ON CALLEnds resolved
Starts with
“Is checkout down?”
Checks
PagerDutyDatadogSlack
Who
The support lead on call
You approve
The customer update
Ends with
Affected list in #support, update sent
TodayPagerDuty→ Datadog→ spreadsheet→ Slack→ wait→ one reply per ticketWith SupahelpAsk who was hit→ read the list→ approve the update

01

The ticket

An incident fires overnight and support asks the obvious question.

02

What it checks

Three tools, in 21 seconds. GitHub stays closed because the cause is already known.

03

What it found

Who was hit, for how long, and why, each with its source.

04

What you approve

The list and the update wait for your yes. Nothing reaches customers before you approve.

05

The reply

One update for everyone affected, written from what was confirmed.

06

The playbook

The next incident gets the same list and update in minutes.