Definition
An incident is a service-management record for an unexpected event that interrupts a service or makes it work less well. A service can be unavailable, slow, unreliable, or missing an important function. The issue may affect one person, a team, or a large group of users.
Incident handling is focused on restoring service. Teams may diagnose the cause, apply a workaround, roll back a change, restart a component, or provide another temporary recovery path. A permanent fix may be planned separately through problem management or change management.
An incident is different from a service request, which is usually a planned request for information, access, or assistance. It is also different from a problem: a problem is the underlying or potential cause of one or more incidents, while the incident is the user-visible disruption that needs attention now.
What does that mean
Think of an incident as something that unexpectedly stops a digital service or makes it weaker—such as a login failure, an unavailable application, or a system that suddenly becomes much slower. Teams first work to get the service usable again; finding the deeper cause can come next.
Why this matters.
A shared definition helps teams classify work consistently, set priorities, communicate clearly, and measure restoration time. For IT, it supports triage and ownership; for Product and Data teams, it connects technical symptoms with user and business impact.
Use cases
Restore service after an outage
When an application, integration, or critical workflow becomes unavailable, teams need a reliable way to record the symptoms, affected users, timing, and current status. Incident handling routes the work to the right responders, coordinates updates, and supports a workaround or recovery action while the service is being restored. The expected benefit is shorter disruption, clearer ownership, and more consistent communication with affected users.
Relevant for: IT; Product
Triage a degraded service before it becomes an outage
A service does not need to be completely down to create an incident. Rising latency, intermittent failures, or a key feature that works only for some users can reduce service quality and trigger an incident response. Teams compare monitoring signals with affected services, regions, devices, or user groups, then prioritize the response according to impact and urgency. The expected benefit is earlier intervention and a smaller user impact.
Relevant for: IT; Data
Separate immediate recovery from the permanent fix
A recurring issue may need a quick workaround even when its root cause is still being investigated. The incident record tracks restoration and user communication, while a linked problem record can investigate the cause and a change record can govern the permanent correction. The expected benefit is faster recovery now without losing the longer-term work needed to prevent recurrence.
Relevant for: IT; Product
How Contentsquare helps
Alerts can notify teams about unusual changes such as error spikes, performance degradations, or drops in conversion, helping them spot potential user-facing incidents earlier.
Error Analysis surfaces technical and non-technical errors, ranks them by impact, and provides investigation context for incidents affecting websites and apps.
Speed Analysis combines real-user and synthetic monitoring to help teams assess availability and performance issues across key pages and workflows.
Session Replay shows what users experienced during an issue, giving responders evidence to distinguish a technical failure from confusion or another experience problem.
Contentsquare supports investigation of user-facing digital issues; it does not replace an IT service desk or incident-management system for assigning owners, managing escalation, or maintaining the formal incident record.
FAQs on incident
Incident management is the coordinated process of detecting, logging, classifying, prioritizing, communicating, resolving, and closing incidents. Its immediate objective is to restore normal service and minimize disruption. The process can include a temporary workaround when a permanent fix is not ready.