Your customer shouldn't have to ask if it worked.

There is a particular kind of uncertainty that appears in otherwise perfectly functional businesses.

You make a booking. Submit an enquiry. Request an appointment. Send a document. Make a payment.

And then — nothing.

No clear confirmation. No useful indication of what happens next. Perhaps an automated email arrives, but it says little more than we have received your request.

So you wait.

Eventually, you do the rational thing. You call.

The person answering checks the system and tells you everything is fine.

From the business's perspective, nothing went wrong. The booking was there. The payment went through. The request had been received. The system worked.

Except it didn't.

This distinction matters. A surprising amount of customer effort isn't caused by businesses lacking information. It's caused by businesses failing to move information to the person who needs it.

The receptionist can see the appointment. Operations can see the booking. Finance can see the payment. The system knows the request has been received. But the customer can't.

So the customer creates a new piece of work simply to retrieve information the business already has. They call. Someone answers. They explain why they're calling. An employee searches for the record. They confirm what the system already knew. The customer hangs up.

Nothing has been created by this interaction. No new decision was made. No genuinely new information was exchanged. The business has simply used two people's time to move an existing piece of information from one side of the organisation to the other.

A customer chasing for an answer is often creating work for both sides.

And this is where something that looks like a customer-experience problem becomes an operational one.

Imagine it happens once. It's irrelevant. Imagine it happens twenty times every day.

Now employees are repeatedly interrupted by calls and emails that should never have been necessary. Those interruptions create their own consequences. Other work gets delayed. Customers who genuinely need help wait longer. Employees switch constantly between tasks.

And eventually someone concludes: we're getting too many calls.

The instinctive response might be to add another phone line. Or hire someone. Or build a better call queue. But that treats the demand as inevitable. The more interesting question is why people are calling in the first place.

Not every contact is valuable demand.

Some customer contact exists only because something upstream failed to provide enough clarity:

• Did you receive my form?
• Is my booking confirmed?
• When will someone contact me?
• Has my payment gone through?
• Do I need to bring anything?
• What's happening with my order?

Individually, these questions seem harmless. Collectively, they reveal something important about how the business communicates.

And often the solution isn't particularly sophisticated. It may simply be:

• A better confirmation.
• A clearer next step.
• An accurate timeframe.
• A reminder.
• A link containing the information customers repeatedly ask for.
• Clear ownership of who communicates what.

Sometimes technology can help. Sometimes the technology already exists and simply isn't being used properly. Sometimes the answer is just one well-written sentence.

There is a significant difference between:

Your request has been received.

and:

Your appointment is confirmed for Tuesday at 10:30. You don't need to call us — we'll send a reminder the day before, with everything you need to bring.

Both are confirmations. Only one anticipates what the customer is likely to wonder next.

Good communication isn't measured by whether information was technically provided. It's measured by whether the recipient knows what they need to know.

Look at the questions your business keeps answering.

Repeated questions are useful. They are evidence.

If customers repeatedly ask the same thing, resist the temptation to conclude that they simply don't read. Sometimes they don't. But before blaming them, look at what you're giving them. Is the answer easy to find? Is it provided at the right moment? Is it written in language they understand? Does it answer the question they are actually asking?

And, perhaps most importantly: could the business have answered the question before the customer needed to ask it? Every repeated question is an opportunity to examine the system that produced it.

That doesn't mean removing human contact. Some conversations matter enormously. A customer dealing with something unusual, emotional or genuinely complicated may need a person — and should be able to reach one easily.

The objective isn't to automate customers away. It is almost the opposite. Remove the unnecessary interactions so people have more capacity for the ones where being human actually matters.

A customer shouldn't spend five minutes on hold to ask whether their booking exists. And an employee shouldn't spend five minutes proving that it does. If the business already knows the answer, the system should make that answer clear — before anyone has to ask.