Customers Who Cannot See Where Their Request Stands Keep Phoning to Ask

The customer who phones to ask "Where is it?"

A homeowner in Pretoria orders custom-built kitchen cupboards. The deposit is paid, the measurements are taken, and then nothing is heard for nine days. On day ten she phones the office. The receptionist does not know, so she walks to the workshop, asks the foreman, comes back, and promises to phone back. She does not, because a delivery arrives and the afternoon fills up. The homeowner phones again the next morning, slightly less patient.

Nothing has gone wrong with the cupboards. They are on schedule. The only problem is that the customer cannot see that, and neither can the person answering the phone without a small investigation. The business pays for that gap twice: once in staff time spent answering status questions, and again in the trust that erodes when a customer is left guessing.

This article is about customers who do not know where their request stands, and about the inbound follow-up it generates. The related problem of staff who must investigate before they can answer is covered in when a status update requires a staff member to investigate. Here the focus is on the customer's side of the experience and the cost it creates.

Why silence feels like failure

People tolerate waiting far better when they can see progress. The Nielsen Norman Group lists visibility of system status among its core usability heuristics, explaining that people should always be kept informed about what is going on through appropriate feedback within a reasonable time. You can read the reasoning in their article on the visibility of system status. The same group's piece on progress indicators explains why showing that something is moving reduces uncertainty during a wait.

Those articles are about digital interfaces, but the human reaction is general. A customer with no information fills the gap with the worst available assumption: the order is lost, nobody is working on it, the business does not care. The customer then acts on that assumption by phoning, emailing, copying a manager or posting a complaint.

What the inbound chasing looks like

• Calls and messages that ask only "Is there any news?"
• The same customer contacting you by phone, email and WhatsApp in a single day because no one channel gives an answer.
• Escalations to the owner for questions that have a simple answer somewhere in the business.
• Staff who stop work to find out, then forget to call back.
• Customers who ask for confirmation of things they have already been told.
• Reviews and complaints that mention "no communication" even when the work itself was fine.

These contacts are rarely logged as a category. They are absorbed into the working day, which is why the business underestimates them. The same pattern is described from the customer side in when customers know less than your internal systems do.

How the pain becomes money

• Labour on status calls. Each query takes several minutes of a paid employee's time, plus the interruption cost of breaking away from other work.
• Repeat contacts. A call that ends in "I will find out" creates a second call, and sometimes a third.
• Escalation time. Owners and managers are pulled into simple questions because customers believe nobody else can answer.
• Reduced trust. Customers who feel uninformed are slower to approve variations, less willing to pay on time and less likely to refer others.
• Lost repeat business. A well-run job communicated badly may still not be repeated.
• Cash flow drag. Customers who are unsure about progress sometimes hold back a final payment until they are satisfied, which links to the collection issues in inconsistent payment follow-up.

An illustrative cost model

The figures are illustrative assumptions for a hypothetical Cape Town installation company handling about 150 active customer jobs at any time.

• First contacts: 60 × 9 minutes = 9 hours a week at R180 = R1,620
• Second contacts: 18 × 9 minutes = 2.7 hours at R180 = about R486
• Manager escalations: 6 × 20 minutes = 2 hours at R400 = R800
• Weekly total: about R2,906. Over 48 weeks: about R139,500 a year

The figure covers only the direct time. It excludes the cost of interruptions to productive work, the customers who quietly choose another supplier next time, and any payment delays. Reduce the enquiry volume by two thirds, and a substantial part of the cost disappears with it.

Why it is tolerated

Businesses often see status enquiries as a normal part of customer service. People answer the phone, apologise and move on. The work of updating customers is also nobody's job in particular. The technicians are busy doing the work, the office assumes the technicians will report in, and the customer sits in the middle. Meanwhile the real status is spread across a job card, a text message and the foreman's memory.

What better looks like

The goal is not to build a grand portal. It is to make sure customers receive the answer before they have to ask for it.

1. Define five or six stages that matter to the customer. For example: order confirmed, materials ordered, in production, ready for delivery or installation, completed. Stages should be recognisable to the customer, not internal jargon.
2. Record the stage where the work happens. If updating the status requires walking to the office, it will not be updated. A phone tick-box or a short form at the workshop is enough.
3. Send a short proactive message at each stage change. The method for removing manual effort from this is covered in manual customer progress updates and the labour they consume.
4. Give front-line staff the same view the customer receives. The person who answers the phone should be able to see the stage in seconds, without leaving their desk.
5. Set expectations on delay. A customer told early that a part is late is usually more understanding than one who finds out on the delivery day.
6. Offer a self-service way to check. Service tools such as service request management describe how requests move through defined steps with visible status, and the same idea works for non-IT businesses.

When it becomes urgent

• complaints repeatedly say "nobody told me anything";
• the owner is receiving customer calls that the office should handle;
• a customer cancels an order because they assumed it had been forgotten;
• growth is adding jobs faster than the office can keep track of them.

Practical next actions

1. For one week, tally every inbound contact that asks for status and note how long each takes.
2. Pick the three most common questions and write down who currently knows the answer.
3. Define the customer-facing stages for your most common job type.
4. Pilot an automatic message at two stage changes and compare enquiry volume after a month.
5. Add "what does the customer see next?" to your job checklist.

Bottom line

Customers who do not know where their request stands will find out the only way open to them: by asking. Each question costs staff time, each unanswered one costs trust, and most of it is avoidable. A handful of clear stages, recorded where the work happens and communicated without being asked, turns an anxious wait into a predictable one.

Sources and further reading

• Visibility of System Status (last verified 10 October 2026)
• Progress Indicators Make a Slow System Less Insufferable
• Service Request Management: Definition & Process - Atlassian

Related Mellorca reading

• Customers on Hold While Staff Search Five Systems: The Cost of Scattered Answers
• Urgent Customer Issues Treated Like Routine Questions: The Revenue Cost
• Answering the Same Customer Questions Daily: The Labour Cost of Hidden Knowledge