cx-backlog-triagelisted

# Backlog triage "How many open tickets do we have" is the wrong question, and the number that answers it is close to meaningless. An open-ticket count mixes together work that is legitimately parked, work waiting on the customer, spam that will never close, and a small number of genuinely abandoned customer requests that are the entire reason anyone asked. The useful question is: **which conversations have a customer waiting on us, and how long have they been waiting?** ## Why the naive count misleads - **It counts work waiting on the customer.** In most helpdesks a large share of "open" work is parked awaiting a reply. Including it makes the backlog look frightening and hides the part that is actionable. - **It counts spam and automation.** Notification emails, no-reply bounces, accounts-payable traffic and marketing blasts open tickets that nobody will ever work. On a real backlog these can dominate the "never touched" bucket entirely, which is why the untouched count on its own convinces nobody. - **It has no age distribution.** A thousand tickets a day old and a thousand a month old are different situations with the same count. - **It measures a stock, not a flow.** A stable backlog with high throughput is healthy. Report arrivals, closures and the resulting net change alongside the level, or the number cannot be interpreted. ## The four segments that matter Segment by **who owes the next action**, and age from **the last action on your side** — not