What is a backlog and when is yours a problem?

A backlog of eighty conversations can be healthy or alarming, and the number itself doesn't show which. Eighty conversations all from today is a normal Tuesday. Eighty of which twelve are older than a week is a team no longer touching part of its work.

So look at the age distribution and at the oldest conversation. That second number is the most honest figure in your whole overview, because it points precisely at the customer who's worst off.

Nearly every backlog has a tail of conversations nobody picks up. They usually share something: there's no clear next step, or the question belongs to another department, or the answer is uncomfortable. They get skipped every day because there's always something that finishes faster.

That tail grows not from capacity but from the absence of an owner with a date. A conversation waiting on something shouldn't be a ticket any more but a task, and a conversation nobody knows what to do with should be escalated rather than skipped.

The reflex is working the list top to bottom. That rarely works, because the oldest conversations are precisely the hardest. What does work is first sorting the pile by what's needed: an answer, a decision, or waiting on someone else.

With a large backlog an honest message to the waiting customers is nearly always the cheapest step. An email saying it's taking longer and when you'll be back removes the chaser emails that would otherwise pile on top. Do that once only, and keep to the date you name.