Observable condition
The customer sends an email: “Any update?” A service representative opens another system, asks operations, checks a spreadsheet or messages a colleague, then returns with the answer. A few hours later another customer asks the same kind of question.
Nothing appears broken. The service team is responding. But the business is repeatedly spending human effort to reveal information it already possesses.
Realisation
The significant question is not why customers ask. It is why they need to ask at all.
Salesforce's 2026 service research reports a gap between how proactive service teams believe they are and how proactive customers experience them to be. Zendesk's recent analysis makes a related point: self-service succeeds when it is connected to the operational reality behind the interface, not when it merely provides another front end.
Identification
This pattern is usually an information-access, service-design and operational-visibility problem. The customer sees a service issue. Internally, the real constraint may be fragmented status data, missing events, weak process visibility, or no mechanism for exposing appropriate information externally.
Diagnosis
Status chasing tends to emerge when the process was designed for internal execution but not for external transparency. Common causes include:
- status is stored in operational systems that customers cannot access;
- different teams own different stages without a shared status model;
- important events do not trigger notifications;
- service staff cannot see a complete end-to-end view;
- the business waits for the customer to ask instead of designing proactive communication.
Commercial impact
The Commercial Value Wrapper is primarily customer experience, service capacity, response speed and scalability. Repetitive status enquiries consume agent time without creating new information. They also make response quality dependent on how quickly the agent can reconstruct the current state.
As volume grows, the support workload can grow even when the underlying product or service has not become more complex. That is a scaling problem: each transaction can generate avoidable communication work.
Common misidentification
The obvious fix is often “we need a chatbot” or “we need more service agents.” Either may help in the right context, but neither solves a fragmented status model. A chatbot that cannot access trustworthy operational data simply becomes another place where the customer fails to get a definitive answer.
Possibility
A better state is one in which relevant operational events automatically update a trusted status and, where appropriate, trigger a notification or become visible through self-service. Customers can see what is happening without learning the company's internal org chart, and agents spend more time on exceptions that actually require human help.
Intervention
Map the most common “what is happening?” questions. Identify where the answer originates, how reliable it is, who is allowed to see it, and whether an event can update the customer automatically. The intervention may involve system integration, status models, event-driven workflows, customer portals, notification services or agent tooling.
The right sequence is operations first, interface second.
Practical diagnostic questions
- What percentage of inbound service contacts are status questions?
- Can an agent answer them from one trusted view?
- Which answers already exist in operational systems?
- Which status changes could safely trigger proactive communication?
- Would self-service resolve the question, or would fragmented back-office data still force escalation?
Bottom line
When customers repeatedly ask for information the business already has, the pattern is not merely “high support volume.” It is a sign that information is not flowing to the point where it creates value. Fixing that flow can improve service while simultaneously releasing support capacity.
Sources and further reading
- Salesforce — 5 Customer Service Trends You Need to Watch in 2026
- Zendesk — The quiet shift behind customer expectations
- Salesforce — Customer Self-Service: What It Is, Importance & Best Practices
Related Mellorca reading
- The Pain of Business Systems That Do Not Talk to Each Other
- Why Growth Breaks Systems That Worked When the Business Was Smaller