# How WorkOS uses incident.io

As published on [incident.io](https://incident.io/customers/workos), January 2024. Captured by usedby on 2026-10-07.

- Company: [WorkOS](https://www.usedby.ai/companies/workos.md)
- Tool: [incident.io](https://www.usedby.ai/tools/incident-io.md)
- Industry: [DevTools & Infrastructure](https://www.usedby.ai/companies/industry/devtools-infrastructure.md)
- Teams: Engineering, Customer Support, Non-technical teams

## What the story says

WorkOS replaced its manual, runbook-document-based incident response with incident.io, using automated workflows and follow-ups synced to Linear. This lowered the bar for declaring incidents and brought non-technical teams into the process.

Summary written by usedby from the source page, in English. The figures are those of incident.io and WorkOS, not ours.

> Workflows are really impactful. Because we're declaring more incidents, being able to have rules around what happens during them is really useful. We've leaned into creating automation around what types of incidents need to have more of a focus on them.

> The biggest shift for the team has been the realization we can include anything reactive as an incident.
>
> Alon Levi, VP of Engineering

## What usedby checked

We compared the story with its live page on 2026-10-07.

- Checked: the passage quoted above is copied word for word from the page, near the name of WorkOS.
- Checked: the publication date is read from the page’s own metadata, never guessed.
- Checked: WorkOS uses incident.io. Confirmed line. Latest check across sources: 2026-10-07.
- Not checked: the result itself. We quote it; we did not measure it.

---
Source: https://www.usedby.ai/case-studies/workos-incident-io · How we check: https://www.usedby.ai/methodology