Follow-up Research
Studying callback records that reopen after closure
A cohort design for measuring reopened callback work while distinguishing administrative closure from resolution of the caller's need.
Finding and scope
A reopened callback can point to premature closure, new information, a duplicate request, or a separate need. This protocol measures local reopen patterns after a recorded closure. It does not equate system closure with customer resolution and reports no observed result.
Evidence base
ISO 18295-1 covers service requirements for customer contact centres. NIST SP 800-92 addresses reliable event logging and analysis. The UK Government Data Quality Framework supports explicit definitions and quality controls. The sources do not prescribe a universal callback reopen target.
Methodology
Build a cohort of callback tasks first marked closed during a fixed period. Define a reopen before extraction, using a linked task, matching stable case identifier, or an explicit reopen event within a prespecified number of days. Exclude test records, merges without a reliable lineage, and closures at the end of the observation window that lack full follow-up time.
The primary measure is the proportion reopened within the window. Review a random sample of reopened cases using fixed categories: incomplete action, failed contact, new information, duplicate linkage, separate issue, or insufficient evidence. Have two reviewers code independently and publish agreement. Report time to reopen and the number of closure events per case as descriptive measures.
Inference boundaries
Reopening does not prove the original assistant made an error. Customer behavior, owner availability, system duplication, and new circumstances can all create a later task. A low rate does not prove resolution because callers may stop contacting the business or use another channel.
Limitations
Record linkage may miss callbacks created under a different identifier. The follow-up window can classify late events incorrectly. Narrative notes may not support a reason category. Results depend on local closure rules and should not be compared across systems without harmonized definitions.
References
1. ISO, ISO 18295-1:2017 2. NIST, SP 800-92 Guide to Computer Security Log Management 3. UK Government, The Government Data Quality Framework