Skip to main content
usedby
Search tools, companies

How Favor uses incident.io

37%

“The results: a 37% reduction in MTTR transformed operations”

As published on incident.io, October 2025. Captured by usedby on Oct 7, 2026.

What happened

Favor uses incident.io in Slack to automate incident coordination, replacing a manual process of creating channels, pulling in engineers, setting up calls and updating the status page. It also routes alerts to service owners via the service catalog and is used across several departments.

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

  • 214%“But the more telling metric is that incident detection increased by 214%.”

Mean time to resolution dropped almost 40%. But the more telling metric is that incident detection increased by 214%.

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

It was uncanny how incident.io built a product that matched what we were trying to do by hand. It was automating things we didn't even think to automate.

Ross McKelvie, Director of Engineering, Favor. Source, 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: 37%CheckedPrinted word for word on the page, near the name of Favor.
  • The passage quoted aboveCheckedCopied word for word from the page, near the name of Favor.
  • The publication dateCheckedRead from the page’s own metadata, never guessed.
  • Favor 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