# How Flagstone uses incident.io

**114%**: “Responder deployment reached 114% of contracted seats”

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

- Company: [Flagstone](https://www.usedby.ai/companies/flagstone.md)
- Tool: [incident.io](https://www.usedby.ai/tools/incident-io.md)
- Teams: Engineering, Risk, Compliance, Client services, Legal, Operations

## What the story says

Flagstone, a regulated UK savings platform, replaced PagerDuty and its Azure DevOps incident tickets with incident.io running on Microsoft Teams. Engineering, risk, compliance, client services, legal and operations now raise, coordinate and run postmortems for incidents in one place.

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

> Responder deployment reached 114% of contracted seats as non-engineering teams joined the platform organically without mandates or much pushing from leadership.

- **4.7 out of 5**: “The internal satisfaction score sits at 4.7 out of 5.”
- **294**: “In the first two and a half months, Flagstone managed 294 incidents through the platform.”

> Don't hesitate if you're on Teams — it works exactly as you'd need it to. And I'm genuinely excited about where the integration is headed.
>
> Dewi Rees, Senior Engineering Manager

## What usedby checked

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

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