Skip to main content
usedby

3 hours

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

As published on incident.io, February 2021. Captured by usedby on Oct 7, 2026.

What happened

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.

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

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.

From the page. incident.io, captured Oct 7, 2026

What the story claims, and what we checked

We compared the story with its live page on Oct 7, 2026.

  • The figure: 3 hoursCheckedPrinted word for word on the page, near the name of Giant Swarm.
  • The passage quoted aboveCheckedCopied word for word from the page, near the name of Giant Swarm.
  • The publication dateCheckedRead from the page’s own metadata, never guessed.
  • Giant Swarm uses incident.ioCheckedConfirmed line. Latest check across sources: Oct 7, 2026.
  • The result itselfNot checkedWe quote it; we did not measure it.

Same company, same tool or same industry.

80%“Approximately 80% of our initial incident-response workflow is now automated.”Kaizen Gaming uses incident.io. Another customer of incident.ioUp to 10x“Up to 10x faster response time”Turbopuffer uses incident.io. Another customer of incident.io4+ hours“4+ hours saved on post-mortems”Built uses incident.io. Another customer of incident.io