The Time Tax of Re-Explaining the Same Thing

There is a particular kind of tiredness that comes from saying the same thing for the fifth time in a day. Not because the question is unreasonable. The customer asking how the delivery schedule works, or why the quote changed, or what happens after they sign, has every right to ask. The tiredness comes from the fact that the answer already exists, somewhere, in someone's head or an old email, and has to be rebuilt from scratch each time.

In many smaller businesses, one or two people become the explainers. They know how things work, so the questions find them. Customers ring them. Colleagues forward follow-ups to them. New staff ask them. Each explanation is short. Together they can fill a day.

This piece looks at the person doing the explaining, rather than the customer receiving it.

Two kinds of repetition

It helps to separate two patterns that often get blurred together.

The first is repeated questions: many different customers asking the same thing because the information they need is not available to them in advance. How long does installation take? What documents do I need? Why was I charged this amount? Mellorca has looked at the operational cost of this in the hidden cost of repetitive customer questions.

The second is repeated context: the same customer's situation being explained again and again inside the business, because the history of the conversation is not where the next person can see it. A follow-up call is picked up by someone who was not on the first call, so the customer explains again, and then a colleague asks the original contact to explain it to them as well.

Both produce the same experience for the explainer: the same words, said again, to someone who would not need them if the information travelled on its own.

What the wider guidance says

The idea that people should not have to provide or receive the same information repeatedly is well established in service design. The UK government's Service Standard, in its guidance on solving a whole problem for users, asks teams to work towards minimising the number of times users have to give the same information. That guidance is written for public services and for the user's benefit, but the mechanism it targets, information that does not travel between steps, is the same one that makes staff repeat themselves.

Customer service software reflects the same thinking from the staff side. Microsoft's documentation for Dynamics 365 Customer Service describes knowledge articles as a way to turn customer questions, issues and feedback into reusable content for service representatives, with an assigned author responsible for maintaining each article. Zendesk describes macros as prepared responses that agents can apply when handling tickets, so routine replies do not need retyping.

These tools are evidence of a widely recognised pattern. They are not evidence that any particular business has the problem, or that installing them solves it. What they show is that "write the answer once and reuse it" is a mainstream operational idea, not a novel one.

An illustrative case

Consider an illustrative example, not a real business: a Gqeberha solar installation company with about fifteen staff. Sales are handled by two consultants; installations by three teams; after-sales by a single coordinator.

In this scenario, every new customer asks broadly the same questions after signing: when the site assessment happens, what the municipality requires, how long until the system is commissioned, and what to do if the inverter shows an error. The answers depend on details that the sales consultant knows but has not written anywhere the coordinator can see.

So the coordinator explains the process to each customer by phone, then calls the consultant to check the details for that particular job, then explains again when the customer rings back a week later because nothing seems to have happened. When the coordinator is on leave, the consultants take the calls and each explains it slightly differently.

The coordinator is good at this. Customers like them. And a large share of their day is spent saying things that have been said before.

The human tax

The first tax is time, in the obvious sense: minutes spent rebuilding an explanation that could have been read.

The second is attention, and it is probably the larger one. Repeating an explanation is not mindless. The explainer has to remember which version applies to this customer, check whether anything has changed, and adjust for what the person already knows. That is a small cognitive load each time, carried many times a day, and it competes with the work that would actually move things forward.

It would go beyond the evidence to say that every explainer finds this draining; some people enjoy being the person who knows. But the structure of the situation is clear enough: when information does not travel, a person has to carry it, and carrying it repeatedly uses up time and attention that cannot be spent elsewhere.

What could realistically change

Most of the useful changes are about writing things down in the right place and making history visible. Some need software; many do not.

Find the top questions. For a fortnight, keep a simple tally of what customers and colleagues ask. The list is usually shorter than expected, and the top few account for much of the repetition.
Answer them once, properly. A short written explanation of each, owned by someone who keeps it current. It can live in a help-desk tool, a shared document or a page on the website.
Send the explanation before the question. A welcome message after signing that sets out the steps and timelines removes many calls that would otherwise happen. Mellorca has explored this in how proactive communication can remove whole support workloads.
Keep the conversation history with the customer record. Notes from each call and email in one place, so the next person can read the context instead of asking for it.
Use templates without becoming robotic. Prepared replies save typing, but they work best as a starting point the person adapts, not as a script.

What changes first, and for the business

The first change is that a portion of questions stop arriving, because the answer reached the customer before they needed to ask. Of those that still arrive, more can be answered by whoever picks them up, because the explanation and the history are both visible.

For the business, that means more consistent answers, less dependence on one person's memory, and capacity freed up for the work that actually needs a conversation. The related customer-side cost is covered in what it costs when customers repeat information across disconnected records.

The human dividend

The dividend is time and attention returned to the explainer. Not all of it: some explanations genuinely need a person, and a good conversation is not waste. But the share of the day spent reconstructing the same answers shrinks, and the attention that went into remembering which version applies can go to the conversations that are new, difficult or worth having.

There may be a further dividend in how the role is experienced. Being the person who knows can shift from being the person everything depends on to being the person who wrote the guide everyone uses. Whether that feels like a gain depends on the individual.

The trade-offs

Written answers age. An explanation that is out of date is worse than none, because it is repeated with confidence. Someone has to own each one.
Some customers want a person. A written guide can feel impersonal, and for some customers the call is part of the service. Removing it entirely would be a loss.
Recording history takes effort. Notes on every call add a small task to each conversation. Without that habit, the history is not there to read.
Templates can flatten judgement. If prepared replies are used rigidly, the explainer's skill in reading a situation is lost.

Why it matters

Explaining things well is a real skill and often an undervalued one. The people who do it are frequently the ones customers trust most. That is exactly why their time and attention deserve protecting from repetition that the business could absorb in other ways.

Mellorca's reading is that re-explaining is rarely a people problem. It is a sign that information is stored in people rather than in the business. Moving it, carefully, gives the explainer back the room to do what they are best at. A related Moment looks at a different version of the same drain: the skilled professional reduced to copy and paste.

Sources and further reading

2. Solve a whole problem for users (last verified 10 October 2026)
Create and manage knowledge articles (last verified 10 October 2026)
Using macros to update tickets (last verified 10 October 2026)