Skip to main content
usedby

4 departments

“4 departments adopted organically”

As published on incident.io, May 2025. Captured by usedby on Oct 7, 2026.

What happened

Thrive replaced PagerDuty and a manual text-file incident template with incident.io. Incidents now run inside Slack with auto-built timelines, Jira ticket syncing, overdue action reminders and post-mortems drafted from transcripts, and the team also analyzes incident data via the MCP server.

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

  • Two weeks“Two weeks from POC → purchase”
  • half a day“Replicating their configuration on PagerDuty took about half a day.”
  • eight“With eight SRE engineers on the team, AI SRE is next on Leigh's radar”

Adoption spread without anyone forcing it. The SRE team started first, then support joined, then InfoSec started using it for security events. Account directors started getting notified when something was affecting a customer.

From the page. incident.io, captured Oct 7, 2026

People used to see incidents as a bad thing. Now they use them to mobilize teams and improve. That whole attitude and culture around it has changed as a result of this partnership.

Leigh Darlow, Head of Live Service, Thrive Learning. Source, captured Oct 7, 2026

What the story claims, and what we checked

We compared the story with its live page on Oct 7, 2026.

  • The figure: 4 departmentsCheckedPrinted word for word on the page, near the name of Thrive Learning.
  • The passage quoted aboveCheckedCopied word for word from the page, near the name of Thrive Learning.
  • The publication dateCheckedRead from the page’s own metadata, never guessed.
  • Thrive Learning uses incident.ioCheckedConfirmed line. Latest check across sources: Oct 7, 2026.
  • The result itselfNot checkedWe quote it; we did not measure it.

Same company, same tool or same industry.

80%“Approximately 80% of our initial incident-response workflow is now automated.”Kaizen Gaming uses incident.io. Another customer of incident.ioUp to 10x“Up to 10x faster response time”Turbopuffer uses incident.io. Another customer of incident.io4+ hours“4+ hours saved on post-mortems”Built uses incident.io. Another customer of incident.io