A fast reply is part of the work.

There is a difference between waiting for an answer and wondering whether anybody has seen the question.

The first can be reasonable. The second gets tiring.

When someone sends a message about work, they may have another decision depending on the reply. A person to update. A deadline to plan around. A concern they do not yet know how to explain.

You do not always need to solve the whole issue immediately to help them.

You can acknowledge it. Say who is looking at it. Give them a realistic time for the next update.

That is work too.

Remove the guessing

Imagine you have asked a supplier whether an order can arrive before an event.

A complete answer might require checking stock, speaking to a courier and confirming the address. Fine. You would want those checks made.

But a short reply saying the request has been received and you will have an update tomorrow morning lets you organise your next step.

Silence makes you guess. Should you wait? Call someone else? Chase again? Has the person gone away? Did the message arrive?

The work may be happening perfectly well in the background. The customer has no access to that background.

It is easy to forget this when you are the person doing the work.

DO NOT MAKE PEOPLE CHASE YOU JUST TO FIND OUT WHAT HAPPENS NEXT.

Clear does not mean permanently available

I am not arguing that everybody should be reachable all day and all night.

That is a poor expectation to build a working relationship around. People need time to concentrate, rest and do things that have nothing to do with your message.

The useful commitment is one you can keep.

Agree on where project communication happens. Explain normal response times. Decide how something urgent should be raised and what actually qualifies as urgent.

Then work within that agreement.

If you promise an update on Thursday, give the update on Thursday, even when the answer is that a dependency is still unresolved. Explain the delay and the next realistic step.

A missed promise followed by silence creates a second problem on top of the original one.

Make it someone's responsibility

In a small business, several people can see the same message and each assume another person will answer it.

A shared inbox does not automatically create shared responsibility.

I would make the ownership clear. Who acknowledges the request? Who gets the answer? Who makes sure the customer hears back?

The customer should not need to understand your internal structure to receive a coherent response.

This is one of those details that can feel too ordinary to deserve attention. It does not look impressive in a presentation about customer experience. There is no dramatic campaign to show.

But it affects how working with you feels.

I can accept that a thoughtful answer takes time. I am much less comfortable with being left to figure out whether I am still part of the conversation.

Think about the last message waiting in your business. Does the person who sent it know what happens next?