Ask any support team whether they lose conversations and they will say rarely. Audit the inbox and you will find them: waiting on a colleague who left, snoozed indefinitely, or marked resolved when they were only deferred.
The five places conversations disappear
- Assigned to someone absent. On leave, off shift, or no longer employed. The conversation is owned, so it looks handled.
- Waiting on another team. Escalated to warehouse or finance, and now in nobody's queue while it waits.
- Snoozed without a wake time, or with one nobody sees when it fires.
- Closed prematurely to clear a queue, with the underlying issue unresolved.
- Never assigned at all — arrived during a busy period and scrolled out of view.
Rules that close each gap
Nobody owns work while away. When an agent's status changes to away, their open conversations reassign automatically. This is the single highest-value rule on the list.
Escalation keeps an owner. When a conversation goes to another team, the support agent stays accountable for the customer even though someone else is doing the work. Otherwise it is genuinely nobody's.
Snoozing requires a time. No indefinite snoozes. When it wakes it returns to a named person's Open queue, not to a shared pool.
Closing requires resolution. If you are waiting on something, the status is Waiting, not Closed. Closing to make a number look better is how issues vanish.
The daily sweep
Once a day someone checks three lists: unassigned conversations, conversations open more than 48 hours, and conversations assigned to anyone currently away. Five minutes, and it catches essentially everything before a customer has to chase.
Escalation needs a defined shape
- Who receives it — a named role, not "the tech team".
- What information must accompany it, so it is not bounced back for detail.
- What the customer is told, and when.
- How long before it is chased, and by whom.
Without the last two, escalated conversations become invisible to the customer, and the next thing you hear is a complaint on a public channel.
Keep the customer informed while waiting
If something takes three days, a message on day one saying so, and a message on day two saying it is still moving, prevents almost all the frustration. People are markedly tolerant of delay and intolerant of silence, and the cost of that second message is nothing.
Beware the 24-hour window here: if the customer has gone quiet while you investigate, a proactive update may need to be a template. Have an approved "we are still working on this" template ready, because needing one and not having one is what produces three days of silence.
Audit backwards occasionally
Once a month, take twenty conversations closed in the last week and check whether the customer came back within days with the same issue. That repeat rate is the truest measure of whether things are being resolved or merely cleared — and it is invisible on any dashboard that counts closures.