Observable condition
The same questions arrive every day. Do you deliver to Polokwane? What does this line on my invoice mean? Which documents do I need to open an account? Can I change the size after ordering? Why is the price on the quote different from the website? They come by phone, WhatsApp, email and the website contact form, and they are answered politely and correctly by whoever is free.
Because each question is quick to answer, nobody counts them. Because they are answered well, nobody complains. The team simply feels busy, and when volumes rise the instinct is to add another person to the front desk or the support inbox.
An illustrative example: a Durban-based supplier of office furniture with a small sales and support team finds that a large share of incoming messages are about delivery lead times, assembly, and the deposit required on custom orders. The answers are stable and have not changed in two years. They are not written down anywhere a customer can find them, and the quote template does not mention them. Each new customer asks, and each answer is typed fresh.
Realisation
A repeated question is information about the business, not just a task to clear. If many customers ask the same thing, something upstream did not tell them, told them unclearly, or told them in a place they do not look. The question is the symptom. The quote, invoice, form, website page or policy that created it is the cause.
The service-design writer John Seddon gave this a name. He distinguished value demand, the requests a business exists to serve, from failure demand, the demand created by a failure to do something or to do it right for the customer. Many repetitive questions are failure demand in this sense. They exist because an earlier communication failed to answer them.
That changes how the work should be managed. Value demand should be served well. Failure demand should be removed at its source, because every answer given is effort spent on something the customer would rather not have needed to ask.
Realisation prompt: of the last fifty customer messages your team handled, how many asked something that a document you already sent could have answered?
Identification
This is a failure-demand and customer-communication design problem. The visible symptom is a high volume of simple questions. The common assumption is that customers do not read, or that the business needs more front-line staff. The structural cause is that customer-facing documents and channels do not contain, or do not clearly present, the information customers need at the moment they need it.
It is related to two existing Patterns but distinct from them. Why Customers Have to Ask What Is Happening concerns status questions about orders and cases in progress. Why Customer Service Becomes a Human Search Engine concerns staff hunting through internal systems to answer. This Pattern concerns stable, predictable questions about policies, products, documents and processes.
Diagnosis
- Documents written for the business, not the customer. Quotes and invoices use internal codes and abbreviations. Terms are in small print on page three. Customers ask what they mean.
- Information in the wrong place. The answer exists on a website page nobody visits, or in a PDF attached to an email sent weeks ago. It is not present at the point of decision.
- Inconsistent answers. Different staff explain the same policy differently, so customers ask again to confirm, or ask a second person.
- No feedback loop. Questions are answered and closed, but nobody records what was asked. The business never sees the pattern, so it never fixes the source.
- Unclear processes. Account opening, returns or custom orders have steps that are not explained up front, so customers discover them one question at a time.
Adding a frequently-asked-questions page is the common fix, and it can help. It is worth knowing that the format has critics: the UK Government Digital Service has argued that FAQs serve writers more than readers and that organising content clearly under logical headings serves users better. The lesson for a smaller business is that the answer should live where the question arises, in the quote, the order confirmation or the product page, not only in a separate list.
Commercial impact
The commercial value at stake is capacity, customer experience, revenue and scalability.
Capacity is consumed answering questions that need not exist, often by the same staff who should be quoting, following up and resolving genuine problems. Customer experience suffers because each question is a moment of uncertainty and a wait for a reply, usually before the customer has committed to buy. Revenue is affected because uncertainty before purchase delays decisions, and an unanswered question after hours may send a prospect to a competitor whose website answers it. Scalability suffers because question volume grows in line with customers, so support headcount grows with sales.
Routine questions handled through email chains also add coordination cost, as discussed in the pain of processing routine requests through email chains.
Common misidentification
A chatbot is now the most common proposal. A well-designed assistant can answer stable questions at any hour, but it can only give answers the business has already written down and agreed. If policies are inconsistent and the source documents are unclear, the chatbot reproduces the confusion at greater speed. It also does nothing to remove the upstream cause: the quote that confused the customer in the first place.
Blaming customers for not reading is the other misidentification. If many readers miss the same information, the problem is with the document.
Possibility
In a better state, the business knows its top recurring questions because they are tagged as they are answered. The most frequent ones are eliminated at source: quotes state lead times and deposit terms plainly; invoices explain their line items; order confirmations say what happens next. A single maintained set of approved answers exists for staff and, where appropriate, for customers through the website or an assistant. Front-line time shifts from repeating answers to handling genuine problems and selling.
For the furniture supplier, that might mean a revised quote template, a short delivery-and-assembly page linked from every quote, and a tag on each message so the team can see which questions remain after the changes.
Intervention
- Tag a sample. For two weeks, tag every incoming customer question by topic. A simple list of categories is enough.
- Separate value from failure demand. Mark each category as a request the business exists to serve, or a question caused by something unclear or missing upstream.
- Trace each failure category to its source. Identify the document, page, form or process step that should have answered it.
- Fix the source. Rewrite the template, move the information to the point of decision, or simplify the process.
- Create one set of approved answers. Keep it maintained and owned. Use it for staff, the website and, if adopted, any automated assistant.
- Re-measure. Repeat the tagging after a month to see which categories have fallen and which remain.
Where questions are mainly about progress rather than policy, the approach in Why Proactive Communication Can Remove Entire Support Workloads applies.
Diagnostic questions
- What are the five questions your customers ask most often, and could you list them without checking?
- Which of those could a document you already send have answered?
- Do all staff give the same answer to the same question?
- Is anyone responsible for reducing question volume, rather than only answering it?
- Does support headcount rise in step with customer numbers?
Bottom line
Repetitive customer questions are a signal that something upstream did not do its job. Answering them well is good service, but removing the reason they are asked is better business. Counting the questions, tracing them to the documents and processes that create them, and fixing those sources frees front-line capacity and gives customers the confidence to buy without having to ask.
Sources and further reading
- Failure demand - Wikipedia (last verified 10 October 2026)
- FAQ - Wikipedia (last verified 10 October 2026)
Related Mellorca reading
- When Service Quality Depends on Who Picks Up the Ticket
- The Hidden Cost of Re-entering the Same Information
- The Hidden Cost of Waiting for Management Information