# How Favor uses incident.io

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

As published on [incident.io](https://incident.io/customers/favor), October 2025. Captured by usedby on 2026-10-07.

- Company: [Favor](https://www.usedby.ai/companies/favor.md)
- Tool: [incident.io](https://www.usedby.ai/tools/incident-io.md)
- Teams: Engineering, Operations, Trust & Safety

## What the story says

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.

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

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

> 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

## What usedby checked

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

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