Skip to main content
usedby

As published on incident.io, March 2024. Captured by usedby on Oct 7, 2026.

What happened

Intercom replaced PagerDuty, Atlassian Status Page and manual in-house Slack workflows with incident.io for on-call, incident response and regional status pages. Engineering, customer support and go-to-market teams now handle incidents in one place.

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

Adoption rapidly spread beyond engineering to customer support and go-to-market teams, creating a transparent, company-wide incident response culture.

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

The transition was incredibly smooth. Our engineers immediately preferred incident.io over PagerDuty, and adoption across the broader company quickly followed.

Mark Gorman, Technical Program Manager, Intercom. 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 passage quoted aboveCheckedCopied word for word from the page, near the name of Intercom.
  • The publication dateCheckedRead from the page’s own metadata, never guessed.
  • Intercom 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.

less than one minute“Inter has a first response time of less than one minute”Intercom uses Intercom. Another tool at Intercom80%“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.io