MELLORCATalk to Mellorca
Patterns

Data, Reporting & Management Visibility

When Customers Know Less Than Your Internal Systems Do

Your systems know the order has shipped, the invoice is issued and the ticket is resolved, yet the customer is still in the dark and phones to ask. Here is why information stays inside.

Mellorca Patterns2026-10-09

Observable condition

Somewhere inside the business, the answer already exists. The warehouse system shows the parcel left at 10:40. The accounts package shows the invoice was issued on Tuesday. The technician's job card is marked complete. Meanwhile the customer has heard nothing, and phones the office to ask where their delivery is, whether the invoice was sent and whether anyone is coming.

The person who answers the phone does not have the answer either. They message the warehouse, wait, and call the customer back. The information was always available to the company. It simply never reached the person who needed it most.

An illustrative example: a Johannesburg office-furniture supplier delivers to corporate clients across Gauteng. Its dispatch system knows when each load leaves and which driver has it. Receptionists at client offices, however, are told only that "the delivery is on its way". On a typical busy day the supplier's two customer-service staff spend most of the morning answering "where is my order?" calls, each of which requires a call to the depot.

Realisation

The realisation is that the business has treated information as something it holds, when to the customer it is something they are owed. Every internal system records events that matter to a customer: accepted, scheduled, dispatched, delayed, delivered, invoiced, paid, resolved. Few businesses have connected those events to a channel the customer can see.

The result is an asymmetry. The company knows a great deal and says very little, and the customer fills the silence with phone calls, emails and, eventually, doubts about reliability. A delivery that arrives on time can still feel late if the customer was never told it was coming.

This is the kind of contact that service-improvement writers call failure demand: demand created by a failure to do something right, or to communicate it, the first time. The calls are not customers being difficult. They are customers doing the business's communication for it.

Realisation prompt: list the last ten reasons a customer contacted you. How many of them were asking for something your systems already knew?

Identification

This is a pattern of internal-only information. The visible symptom is a steady flow of status enquiries. The common assumption is that customers are impatient, or that the service team needs more staff. The structural cause is that events are recorded in internal systems and are not passed on to customers automatically, so the only route to the information is through a person.

The published Pattern why customers have to ask what is happening describes the experience from the customer's side. This Pattern concentrates on the internal arrangement that keeps the answer inside: which events exist, which of them are shared and why most are not. The related Pattern when customers call for records your systems already hold covers requests for documents, whereas this one covers status and progress.

Diagnosis

  • Events are recorded but not published. The system logs dispatch, delay or completion, but nothing turns that log entry into a message, a portal update or a line on a statement.
  • The customer-facing tool is separate. Staff who talk to customers work in the CRM or a shared inbox, and the operational facts live in a different system they cannot see.
  • Messages are manual. Where notifications exist, they depend on a staff member remembering to send them. On a busy day, they are the first thing to slip.
  • Bad news travels slowest. A delay is recorded internally but nobody is assigned to tell the customer, because telling them feels like admitting a problem.
  • Internal wording is unusable. Statuses such as "picked, awaiting consolidation" mean something to the warehouse and nothing to a customer.
  • Privacy is used as a reason for silence. Teams sometimes hesitate to share information because they are unsure what the law allows. POPIA does not forbid telling a customer about their own order. Its provisions on access to personal information, for example, exist to give people reasonable access to what is held about them.

Commercial impact

The commercial value at stake is service capacity, customer confidence, collection speed and reputation.

The direct cost is staff time. Each status call takes a few minutes for the customer and a few more for the employee who has to find the answer. Multiplied across a month, this often amounts to the working time of one or two people whose capacity could be used on problems that really need a human.

The indirect cost is confidence. Customers who have to chase draw conclusions about how well run the business is. They may remain loyal, but they are quicker to compare alternatives at renewal. In business-to-business work, the person chasing you is often a junior employee whose own manager is asking them for updates, so your silence becomes their stress.

There is also a cash effect. An invoice that the customer did not realise had been issued waits longer for payment. A completed job that the customer does not know is complete may be disputed. The Pattern why sending an invoice requires so much work shows how effort at the billing step also delays the message that the invoice exists.

Common misidentification

The usual response is to add people to the phones or to build a longer FAQ page. These measures treat the calls as a permanent feature of the business. A larger team answers the same questions faster, but the questions keep coming, and the cost grows with every new customer.

Another response is to buy a customer portal. A portal can help, but only if the data behind it is connected to the operational systems. A portal that staff have to update by hand is the same silence in a better frame. A third response is to tell staff to be more proactive. They already are, but they lack the information at the moment they need it.

Possibility

In a better state, the customer's view follows the company's own. When the order is accepted, they are told. When it is dispatched, they receive a message with an expected time. When something slips, they hear about it before they have to ask, together with the new date. When the invoice is issued, it arrives with a plain description of what it covers.

Customer-service staff see the same operational facts that the warehouse and finance see, and spend their time on the exceptions: the order that is genuinely lost, the customer who needs a decision. The number of status calls falls, and the remaining calls are the ones worth having.

Intervention

  1. Count and classify the contacts. For two weeks, tag every incoming query as status, document, change or genuine problem. The status and document share is your opportunity.
  2. List the events customers care about. Usually five to eight: accepted, scheduled, dispatched, delayed, completed, invoiced, paid.
  3. Find where each event is recorded. Identify the system and the field that changes when it happens.
  4. Translate it into customer language. Write the message once, in plain words, with the information the customer needs to act on.
  5. Send it automatically from the record. Use the workflow features most business systems already have, or a light integration, so that the message follows the event without a person in the middle.
  6. Give staff the same view. Make sure that whoever answers the phone can see the latest event. The Insight broken handoffs are systems problems explains why this is a design question, not an attitude question.

Diagnostic questions

  • What proportion of customer contacts ask about something a system already records?
  • Which events does a customer hear about without asking, and which do they not?
  • Can the person answering the phone see the same status as the warehouse?
  • When a delay occurs, who is responsible for telling the customer, and how?
  • Would your own status messages make sense to someone outside the business?

Bottom line

When customers know less than your systems do, the business is paying people to carry information that software could carry for free. Connecting the events you already record to the messages customers need turns a daily stream of enquiries into a few conversations that matter, and makes the business look as organised as it actually is.

Sources and further reading

Related Mellorca reading

Article summaryYour systems know the order has shipped, the invoice is issued and the ticket is resolved, yet the customer is still in the dark and phones to ask. Here is why information stays inside.
Explore our solutionsStart a conversation