# How Buffer uses incident.io

**50%**: “spending about 50% less time on them”

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

- Company: [Buffer](https://www.usedby.ai/companies/buffer.md)
- Tool: [incident.io](https://www.usedby.ai/tools/incident-io.md)
- Industry: [Marketing Tech](https://www.usedby.ai/companies/industry/marketing-tech-martech.md)
- Teams: Engineering, Customer Advocacy

## What the story says

Buffer uses incident.io to run incident response in Slack across engineering and customer advocacy, replacing manual Slack workflows, Atlassian status pages and inconsistent postmortems. It handles incident coordination, customer communications through status pages with templates, and postmortem follow-up.

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

> Buffer now logs more incidents overall while spending about 50% less time on them, allowing them to resolve minor issues before they escalate.

> We empower every teammate to declare an incident early: smaller fires beat big ones. We log more incidents because we see them sooner and fix them faster.
>
> Raf Leszczyński, Senior Engineering Manager

## What usedby checked

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

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