The use case: how Flagstone deploys incident.io
Flagstone, a regulated UK savings platform, moved its on-call and incident management from PagerDuty and Azure DevOps to incident.io running on Microsoft Teams. Risk, compliance, legal, client services and operations teams now raise, coordinate and run postmortems for incidents in the platform.
More reported results
Figures published in incident.io’s case study. They are not independently measured by usedby.
In the first two and a half months, Flagstone managed 294 incidents through the platform.
The internal satisfaction score sits at 4.7 out of 5.
In the customer’s words
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.incident.io users in Fintech & Payments
Companies in the same sector, with public evidence.
See all incident.io customersGo straight to the source
Based on incident.io’s published case study. We check the public evidence; the results are reported by the vendor.
incident.io- Source published
- Mar 26, 2026
- Last checked
- Nov 11, 2026
Open source capture What the story claims, and what we checked
What we compared with the page.
- The figure: 114%Checked
Printed word for word on the page, near the name of Flagstone.
- The passage quoted aboveChecked
Copied word for word from the page, near the name of Flagstone.
- The publication dateChecked
Read from the page’s own metadata, never guessed.
- Flagstone uses incident.ioChecked
Confirmed line.
- The result itselfNot checked
We quote it; we did not measure it.
Responder deployment reached 114% of contracted seats as non-engineering teams joined the platform organically without mandates or much pushing from leadership.






