Mandate 24-hour Sev-1 outage auto-escalation to estaff and AE

June 17, 2026 at 3:19 PMoperationalmedium

Situation

After the Fyr Fuzzball outage ran roughly 5 days without surfacing to leadership and the customer had to ping Horn directly to force escalation, Peter directed that any Sev-1 or customer outage open past 24 hours must automatically notify estaff and the account AE, built into tooling so it does not depend on a human judgment call. Ryan operationalized it as Zendesk automation plus CCing named-account AEs at ticket creation.

Reasoning

The technical recovery was handled competently; the real failure was that leadership and the AE learned about a multi-day Sev-1 from the customer rather than from internal channels. Peter wants escalation to be structural and automatic, not dependent on someone choosing to raise it. He framed it as a systemic fix and not blame (nobody is getting fired, I just want to understand the breakdown). He set a fixed 24-hour bound with no manual judgment because judgment is exactly what failed here.

Additional Context

Triggered by the Fyr/Fuzzball postgres cert expiry outage. Peter also asked Ryan for a COE and asked whether the rest of CIQ certs are at risk of expiring since the company just passed its one-year founding mark.

Observed Evidence

Peter in department-heads: Whatever we need to build to ensure that that happens should happen (re 24h estaff notification). Ryan back to Peter: Any Sev-1 open for 24 hours triggers automatic notification to the AE and estaff, no manual judgment, built into automation; AEs on named accounts CCd at ticket creation going forward.

Confidence Breakdown

30/35
Evidence
15/30
Pattern
19/20
Source
12/15
Corroboration

Reasoning Depth Analysis

Org Signal:Estaff visibility into customer pain is non-negotiable; bad news must travel up fast and automatically.
Who Affected:Ryan CS org owns the build; AEs now looped in at ticket creation; every named-account customer; Bjorn who wanted the escalation call.
Precedent:Time-bound auto-escalation with no manual judgment becomes the standard incident-handling rule, not a one-off.
Consequences:Real and in-flight: Ryan building Zendesk automation this week plus AE-at-ticket-creation process change; COE committed.
Timing:Now, because the Fyr incident made the gap concrete and customer-visible right before the board meeting.

Related Context

💬
department-heads — Fyr outage escalation

slack

I would like, in the future, if something is down for more than 24 hours, to ensure that estaff knows. Whatever we need to build to ensure that that happens should happen.

Outcome

No outcome recorded yet.

Decision ID: 3923e6c9-77e5-4200-b40c-85045ed6b9e7