A call backlog triage process

Freeze and inventory the backlog

Build a backlog register with one row per caller need, not one row per attempt. Add priority class, evidence for that class, current owner, next action, and a due time that can be sorted.

Resolve duplicates and uncertain deadlines

Potential safety issues leave the normal backlog for the named urgent path. Unknown callback details go to research status; disputed priority goes to the queue manager; systemwide incidents may be grouped only if each caller record remains traceable.

Create a triage register

Capture record ID, first contact time, latest attempt, caller, callback number, request category, affected service, stated deadline, safety or access flag, customer impact, duplicate links, last promise, priority, owner, due time, and disposition.

Limit triage authority

A triager may merge duplicates, apply documented priority rules, and assign approved queues. They may not erase old attempts, classify a loud caller as more urgent without evidence, make technical judgments, or promise resolution order.

Score consequence instead of emotion

Work in short sweeps: first remove safety and fixed-deadline cases, then protect existing promises, then process routine work by age. Recheck the queue after every sweep because new information can change ownership.

Pilot on the oldest mixed batch

Triage a batch containing a duplicate voicemail, a missed deadline, a vague “urgent” message, and a safety-related statement. Have a second reviewer compare classifications before scaling.

Track whether the backlog is truly shrinking

Watch open item count by age band, oldest item age, items completed, new items arriving, overdue promises, reassignment count, duplicates merged, and reopened work. Report inflow and outflow together.