Skip to content
Kaarne Superstore⌕
Customers & Sales

You Answered Every Message. Why Is the Queue Still Growing?

Separate replies from resolved cases before interpreting a growing service queue. Check arrivals, completions and open work with a simple weekly example.

A shop owner holds a completed-reply card beside a still-open case folder and incoming envelopes.

Every message received an answer. The team worked through the inbox, yet the open-case list is larger than it was on Monday. It is tempting to conclude that somebody has counted incorrectly.

First ask whether an answered message and a completed case mean the same thing in this process. A helpful reply may move a customer forward while leaving a question, investigation or promised follow-up open.

Count the event you actually mean

In this fictional sporting-goods shop, a customer asks about a delayed parcel. The team replies that it will check with the carrier. The message has been answered; the delivery enquiry has not necessarily been resolved.

Give each working measure a definition. New messages, new cases, replies and resolved cases can all be useful, but they should not be substituted for one another. One case can involve several messages before its agreed completion event.

Keep the definition close to the weekly report so a colleague can explain what the figure includes. A familiar label is not enough if people interpret it differently.

Reconcile the open work

Start with the cases open at the beginning of the period. Add the new cases and account for resolved work and any other movements your process uses, such as cancellations, transfers or reopenings.

Use a small fictional example before applying the rule to a live report. If the movements do not explain the closing balance, investigate the difference. A queue that grew for an understood reason is easier to discuss than a number nobody can reconcile.

Avoid interpreting an unexplained difference as evidence about an individual’s effort. Check the source, scope and definition first.

Look for work that replies do not finish

Review a few open cases together. Is the next step waiting for the customer, a supplier, an internal decision or a promised check? Record the owner and the next action where the team can see them.

A case should not disappear simply because an acknowledgement was sent. Equally, an old record should not stay open indefinitely when the agreed resolution event has happened. The working rule needs to support both decisions.

Choose a few representative examples rather than trying to redesign every status at once. The aim is a dependable explanation of the queue, not a perfect vocabulary exercise.

Decide what the next week needs

Once the balance makes sense, discuss the actual constraint. The team may need clearer follow-up ownership, better information or a review of recurring contact reasons. More reply activity is only one possible response.

A useful weekly report distinguishes effort, movement and unfinished promises. That lets the business acknowledge the work already done while still seeing what needs attention.

Continue with a related question

Explore Keep Customer Promises Visible Behind the Queue Count, or read The Queue Is Smaller. Why Are the Oldest Requests Still Waiting?.

For a written practice option, see Customer Service Planning with Matze: contents and requirements.

Review the provider’s course details. Affiliate link: Superstore may earn a commission if you buy.

0

Discussion 0

What did this article make you think about?

Join the conversation

Your email address will not be published. Required fields are marked *

Saved articles

Saved in this browser.