Non-Incident Tickets: Don't Confuse Them With Incidents
Customer tickets aren't all incidents. The discipline that separates.
Sort
Sorting tickets correctly is the first discipline. Single-customer issues belong in the support queue; multi-customer signal is the incident trigger. Mixing the two produces false alarms and missed incidents.
- Single-user issue. Single-customer scope per ticket. Routes to support queue, not on-call rotation.
- Multiple users. Ticket cluster triggers investigation. The pattern may hide an incident behind individual support reports.
- Pattern emerging. Cross-customer signal triggers incident declaration. Stop sorting; start responding.
- Routing tag per ticket. Named queue per ticket. The tag catches mis-routed reports before they age out.
Escalate when
Escalation triggers are explicit, not gut feel. Volume thresholds and time windows, both encoded in the support tool.
- 5+ similar in 1 hour. Volume threshold per window. Probably an incident; declare and start the response.
- Trend over 24 hours. Slow-burn pattern per day. Possibly an incident class rather than a one-off.
- Documented “similar” definition. Named keyword set per cluster. Inconsistent grouping produces inconsistent escalation.
- Auto-detection. Support-tool alarm catches what humans miss in noise. Pure-human triage misses fast-moving spikes.
Avoid
Two failure modes break the discipline. Over-declaration dilutes the incident term; under-declaration hides real incidents as “support spikes.”
- Calling everything an incident. Over-declaration devalues the term and floods the on-call queue. Reserve incident status for cross-customer impact.
- Ignoring multi-customer issues. Real incidents hide as “support ticket spike.” Under-declaration is the more dangerous failure mode.
- Weekly trend review. Support-data audit each week catches missed escalations. The pattern is visible in aggregate even when individual tickets look harmless.
- Quarterly threshold tuning. Volume thresholds need re-tuning as the customer base grows. Last quarter’s trigger may be loose at this quarter’s scale.