The use case: how Thrive Learning deploys incident.io
Thrive replaced PagerDuty and a manual text-file incident template with incident.io, running incidents inside Slack with auto-built timelines, Jira ticket syncing, overdue action reminders and post-mortems drafted from transcripts. They also use its MCP server with Claude to analyze incident data for trends and weaknesses.
More reported results
Figures published in incident.io’s case study. They are not independently measured by usedby.
Two weeks from POC → purchase
One day to migrate
In the customer’s words
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.Other AI tools used by Thrive Learning
Other public relationships recorded on usedby.
Explore Thrive Learning’s AI stackOther companies using incident.io
Customers across industries, with public evidence.
See all incident.io customersGo straight to the source
Based on incident.io’s published case study. We check the public evidence; the results are reported by the vendor.
incident.io- Source published
- May 7, 2025
- Last checked
- Nov 11, 2026
Open source capture What the story claims, and what we checked
What we compared with the page.
- The figure: 4 departmentsChecked
Printed word for word on the page, near the name of Thrive Learning.
- The passage quoted aboveChecked
Copied word for word from the page, near the name of Thrive Learning.
- The publication dateChecked
Read from the page’s own metadata, never guessed.
- Thrive Learning uses incident.ioChecked
Confirmed line.
- The result itselfNot checked
We quote it; we did not measure it.
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.








