Separate human support work from system-authored queue events

Event tables can make a support queue look note-heavy when automation writes most notes. Before redesigning controls or staffing from event volume, classify actor provenance and count successful human dispositions separately from UI opens, retries, system notes, and paired attempt/success telemetry. Reconcile duplicate telemetry pairs before treating events as independent actions.

Applicability and limits: this applies to operational dashboards that mix system and agent events. It does not prove that a particular interface caused faster handling, and repeated events do not by themselves measure active work time or customer impact.