Customer chasing is usually treated as a communication problem. Sometimes it is. But when customers repeatedly ask for updates at the same stage, the underlying problem is often structural.

Silence creates uncertainty

Customers usually know what they have done. They completed the form, accepted the quote, sent the information or paid the invoice.

What they often do not know is what happened next. Internally, the business may be waiting for another team member, a supplier, stock, approval or a scheduled action. None of that is visible unless somebody explains it.

When there is no update, the customer has to guess. Chasing is the natural result.

Internal status is not customer visibility

A process can have an internal status and still leave the customer completely uninformed.

Labels such as awaiting review, pending supplier confirmation or ready for dispatch may make sense to the team, but they do not automatically answer the customer's questions: Has my information been received? Is anything missing? What happens next? When will I hear from you?

A useful process needs both internal visibility and appropriate customer communication.

Chasing often reveals unclear ownership

When a customer asks for an update, who should answer? The person who took the order, the administrator, the person doing the work, or whoever notices first?

When ownership is implied rather than explicit, updates become inconsistent. One person assumes somebody else has replied. Another checks three systems before they can give an answer.

The communication delay is a symptom. The process visibility is the underlying problem.

The next action matters more than the status

A reliable process should make the next action visible, not just the current label.

For every piece of active work, somebody should be able to identify the current stage, what is outstanding, who needs to act, when that action is due and what happens afterwards.

Without that information, a status is only a description. It is not an operational instruction.

Better communication does not mean constant email

The answer is not to send an update at every tiny internal step.

Instead, identify the points where silence is likely to create uncertainty: confirmation of receipt, missing information, work starting, a meaningful delay, completion, or a clear customer action.

A small number of well-timed updates can prevent a large amount of chasing.

What to review

Ask where the customer loses visibility. Check whether staff can immediately see the current position. Confirm whether the next action and owner are recorded clearly. Separate customer actions from internal actions. Define when the process is complete.

The aim is not simply to reply faster. It is to create a process where fewer customers need to ask in the first place.

One process needs untangling?

Admin Untangled provides a written diagnostic of one clearly defined business process, with practical recommendations and no meetings required.

Request a review