Exception analysis
Call-center exception aging analysis research
Research on measuring unresolved call exceptions by age, owner, next action, and risk without treating an old item as completed.
Headline finding
Exception age is useful only when paired with owner, next action, risk, and source evidence. An age count by itself can hide abandoned or duplicated work.
Methodology
Define the clock start, pause rule, duplicate rule, eligible population, age bands, exception categories, and owner before reviewing a queue. Separate ordinary, urgent, unreachable, disputed, privacy, and safety exceptions. Report missing timestamps and unknown owners as findings.
Key findings
- The oldest item is not necessarily the highest-risk item; risk and age should be analyzed separately.
- A visible unresolved state prevents a closed label from masking missing action.
- External guidance can frame governance, privacy, and security controls, but local records are required for any business-specific rate.
Interpretation
For each exception, retain the source event, current owner, next action, last reviewed time, and reason for escalation. Limit notes to what the owner needs. Review the queue with the responsible business owner when rules conflict or a sensitive decision is required.
Sources
1. NIST Cybersecurity Framework 2.0 2. NIST Privacy Framework 3. FTC small-business cybersecurity 4. SBA manage your business 5. W3C WCAG overview 6. FCC consumer guide to unwanted calls