# How Giant Swarm uses incident.io

**3 hours**: “I’d estimate that we save at least 3 hours onboarding each new oncaller”

As published on [incident.io](https://incident.io/customers/giant-swarm), February 2021. Captured by usedby on 2026-10-07.

- Company: [Giant Swarm](https://www.usedby.ai/companies/giant-swarm.md)
- Tool: [incident.io](https://www.usedby.ai/tools/incident-io.md)
- Teams: Customer Success

## What the story says

Giant Swarm uses incident.io to standardise and automate its incident response process through workflows, so on-call engineers, including new joiners, face less stress during incidents. It also uses post-mortem generation and custom fields to share incident information with Customer Success and to capture follow-ups and insights faster.

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

> We’re now able to encode the process itself which really helps new on-callers. We are approaching it in terms of making our on-callers' lives easier, and reducing that stress, allowing us to make changes to our process without having to retrain everyone.

- **40% vs 90%**: “before we probably captured 40% vs 90% now that we’re using incident.io”

## What usedby checked

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

- Checked: the figure 3 hours is printed word for word on the page, near the name of Giant Swarm.
- Checked: the passage quoted above is copied word for word from the page, near the name of Giant Swarm.
- Checked: the publication date is read from the page’s own metadata, never guessed.
- Checked: Giant Swarm 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/giant-swarm-incident-io · How we check: https://www.usedby.ai/methodology