# How Bold Commerce uses incident.io

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

- Company: [Bold Commerce](https://www.usedby.ai/companies/bold-commerce.md)
- Tool: [incident.io](https://www.usedby.ai/tools/incident-io.md)
- Teams: Engineering, Product, Operations, Security

## What the story says

Bold Commerce uses incident.io for incident response and also as a general workflow tool for security incidents, tiger teams, Black Friday and Cyber Monday preparedness, product launches, and planned maintenance. Incidents are created in Slack to coordinate people, record activity, and track follow-ups.

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

> At Bold Commerce, incident management isn’t just reactive work for common and critical errors. It’s an opportunity to funnel tasks and fast-moving projects into a well-defined process that allows for better collaboration, learning, and outcomes across the board.

> It's the intuitiveness that’s really essential to the platform being successful. The documentation and training we have on incident.io is much less than anything we have with other tooling because it's intuitive. If you can work Slack, you can probably work in incident.io.
>
> Craig Kinloch-Melia, Head of Technology

## 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 Bold Commerce.
- Checked: the publication date is read from the page’s own metadata, never guessed.
- Checked: Bold Commerce 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/bold-commerce-incident-io · How we check: https://www.usedby.ai/methodology