# How Pleo uses incident.io

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

- Company: [Pleo](https://www.usedby.ai/companies/pleo.md)
- Tool: [incident.io](https://www.usedby.ai/tools/incident-io.md)
- Industry: [Fintech & Payments](https://www.usedby.ai/companies/industry/fintech-payments.md)
- Teams: Engineering

## What the story says

Pleo replaced its in-house incident tooling with incident.io to manage incident response and on-call. It uses Workflows to automate response actions, Slack channels for communication, and the Insights dashboard for post-incident learning.

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

> Before incident.io, Pleo’s in-house solution made even declaring incidents an exercise in frustration.

> incident.io saves us hours per incident when considering the need for us to write up the incident, root cause and actions, communicate it to wider stakeholders and overall reporting.
>
> Braedon Gough, Site Reliability Engineer

## What usedby checked

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

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