Measuring Customer Request Aging Without Hiding Handoffs

Research question

How can teams describe request age without collapsing unlike states into one misleading clock?

Method

The protocol reconstructs state transitions from timestamps and samples source evidence for classifications, reopens, and closure claims.

Key findings

Total age should be reported beside time in each state.
Clarification loops reveal intake quality problems.
Closure requires evidence that matches the request.

Clock and state definitions

The primary clock begins at accepted intake, while a separate received timestamp preserves earlier contact. States have mutually exclusive definitions and named entry events. Pauses are never deleted; they are labeled by reason and owner.

Sampling design

Select records across request classes, channels, and age bands using a documented rule. Inspect the originating request, transition evidence, assignment trail, and closure artifact. Report records excluded because required evidence was unavailable.

Metrics with context

Publish median and distribution bands for total age and state duration, plus clarification count, transfer count, reopen rate, and evidence-backed closure rate. Avoid combining request classes whose workflows or authority differ materially.

Operational use

Use findings to improve intake criteria, routing ownership, decision capacity, and customer updates. Do not turn an observational baseline into a service promise or employee performance conclusion without a separately governed process.