# How Kaizen Gaming uses incident.io

**80%**: “Approximately 80% of our initial incident-response workflow is now automated.”

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

- Company: [Kaizen Gaming](https://www.usedby.ai/companies/kaizen-gaming.md)
- Tool: [incident.io](https://www.usedby.ai/tools/incident-io.md)
- Teams: Site Reliability, Site Reliability Operations, Information Security, System Administration, Site Reliability Engineers, Network Reliability Engineers, Incident Managers

## What the story says

Kaizen Gaming's Site Reliability team uses incident.io to automate the start of major incidents, including creating Slack channels, assigning roles, paging responders and notifying stakeholders. It also manages customer-facing status pages across its markets from the same incident record, and tracks post-incident follow-up actions.

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

> Approximately 80% of our initial incident-response workflow is now automated. The team can spend less time administering the incident and more time resolving it.

- **two minutes**: “The initial response workflow launches in under two minutes, compared with five to ten minutes previously.”
- **20 status pages**: “Following a one-month phased rollout, Kaizen Gaming migrated its incident-response workflows and 20 status pages to incident.io.”
- **one working day**: “Today, the equivalent end-to-end process can be completed within one working day.”

> The hardest part of an incident isn't always the technical problem. It's coordinating the response.
>
> Vaggelis Kosvyras, Incident Manager

## What usedby checked

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

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