Skip to content

    Customers forgive the delay. They do not forgive the silence.

    Most operators think they lose customers over things going wrong. Usually they lose them over not being told.

    Customers forgive the delay. They do not forgive the silence.

    Ask an operator why a customer left and you will usually hear about the incident. The consignment that missed its window. The engineer who did not turn up. The order that went out short.

    Then go and read the review they left. It almost never describes the incident. It describes the hour spent trying to find out what had happened.

    The incident is not the damage

    Things go wrong in every operation. Customers know this. They run businesses too. What they cannot absorb is the period between something going wrong and somebody telling them, because that is the period in which they have to make decisions without information.

    A customer told about a delay at nine in the morning reschedules their day. The same customer told at four in the afternoon has already lost it. The delay was identical. The cost to them was not.

    Why it keeps happening

    Nobody decides to withhold information. The gap opens because telling the customer is manual work sitting at the end of a queue of more urgent manual work.

    The person who knows about the delay is busy dealing with the delay. Updating the customer is the task that gets done once the fire is out, which is to say after it stopped being useful. This is not a discipline problem. It is a design problem, and it gets worse exactly when volume rises and you can least afford it.

    What actually fixes it

    The fix is not a policy telling staff to communicate more. It is removing the human step from the communication entirely, so that the update leaves when the status changes rather than when somebody remembers.

    • The update fires off the status change, not off a person.
    • It goes out on the channel the customer already uses, not the one that suits your systems.
    • Routine questions get answered without reaching a human at all, so your team keeps the conversations that need judgement.
    • Nobody has to be free for any of this to happen.

    What changes

    Support volume falls, because most inbound contact was people asking a question you could have answered before they asked it. Reviews improve without anything operational getting better, because the thing customers were angry about was never the delay.

    And your team stops spending its day relaying information that a system should have relayed for it.

    This shows up hardest in transport and logistics, where the delay is rarely avoidable and the silence is the one part still in your control.

    Does this look like your operation?

    Tell us the problem