The alert
The message that arrives before the tag exists
Support reporting is downstream of a taxonomy, and a taxonomy is downstream of a human noticing. This skips both. It names the area, the day, and the twenty tickets a lead needs to read to name the issue.
S
SupportAPP#eng-alerts🔴 Tickets mentioning topic jumped +363%area=payments
Baseline
26.63
Now
123.33
Confidence
99.9%
Started
Aug 13
Queue
tier-1 (4 areas)
Area
payments
Topic
unnamed cluster #7
First seen
Aug 12
Likely cause · A topic cluster with no tag and no macro starts appearing in payments tickets on Aug 12. First-contact resolution on that area falls at the same time, which is the signature of contacts arriving faster than the playbook does. Escalation rate and handle time follow. Total volume is flat because these contacts replace other payments contacts rather than adding to them, so nothing on the queue dashboard moved.
- 1.Read the 20 highest-similarity tickets in cluster #7 and name the failure mode.
- 2.Create the tag and a macro before the next shift so first-contact resolution recovers.
- 3.Send the cluster to the payments team with the Aug 12 date attached and ask what shipped.
AcknowledgeFalse positiveCUSUM · q < 0.0001 · BH-corrected
S
SupportAPP#eng-alerts🔴 Escalation rate jumped +197%area=payments
Baseline
6.56%
Now
19.5%
Confidence
99.9%
Started
Aug 12
Queue
tier-1 (4 areas)
Area
payments
Topic
unnamed cluster #7
First seen
Aug 12
Likely cause · A topic cluster with no tag and no macro starts appearing in payments tickets on Aug 12. First-contact resolution on that area falls at the same time, which is the signature of contacts arriving faster than the playbook does. Escalation rate and handle time follow. Total volume is flat because these contacts replace other payments contacts rather than adding to them, so nothing on the queue dashboard moved.
- 1.Read the 20 highest-similarity tickets in cluster #7 and name the failure mode.
- 2.Create the tag and a macro before the next shift so first-contact resolution recovers.
- 3.Send the cluster to the payments team with the Aug 12 date attached and ask what shipped.
AcknowledgeFalse positiveCUSUM · q < 0.0001 · BH-corrected
Clustering finds it, statistics prove it
Topic clustering on ticket text produces candidates every single night, most of which are nothing. What separates a real emerging issue from a cluster that happened to grow is whether first-contact resolution, escalation, and handle time broke with it, in the same area, on the same day. The model proposes. The changepoint decides.