A branch with no complaints might be well run, or its customers might have no easy way to tell you, or they might not think it worth the effort. Silence cannot tell these apart. So the right way to read a branch that sends nothing is as unknown, not as fine, and to check coverage, meaning whether customers at that branch had a route to reach head office and whether any messages arrived in the period, before drawing any conclusion.
This guide explains why silence misleads, how to check coverage, and what to do about branches you cannot hear from.
Why silence is ambiguous
There are at least four reasons a branch might be quiet, and only one of them is good news.
- The branch is doing well and customers have little to complain about.
- Customers have a route but do not use it, because it is hard to find, they do not think anything will happen or the problem seemed too small.
- Customers have no route at all, because nobody placed the code, the link was never sent or staff discourage it.
- Something is blocking the signal, such as a broken link, a misplaced code or a process that never reaches head office.
Looking at a dashboard where one branch shows zero complaints, all four look identical.
Why the mistake is common
Reporting tools are good at showing what is there and poor at showing what is missing. A table that lists complaints by branch ranks the branch with none at the top, which looks like a reward.
Branches also have reasons to like silence. A manager whose branch generates no complaints looks successful, and nobody is motivated to ask whether the channel works.
What coverage means
Coverage is a simple question: did this location produce any messages in the period? It is not a measure of quality. It is a measure of whether you can see the branch at all.
A useful view shows three groups.
- Locations that produced messages in the period.
- Locations that went quiet after producing messages before.
- Locations that have never produced a message.
The second group deserves attention first. A branch that used to send messages and has stopped may have lost its code, changed its process or had a change of manager. The third group needs a different question: was the channel ever properly set up there?
How to investigate a silent branch
You do not need to assume the worst. You need to find out what the silence means.
- Check the basics. Is the code displayed where customers can see it? Is the link being sent? Does it work from a phone?
- Ask the manager how the channel is used at the branch. Ask as a practical question, not a challenge.
- Compare with similar branches. If the other branches of a similar size and format produce messages and this one does not, the gap is informative.
- Look at other signals. Operational numbers, reviews, visits and checklist results may point either way.
- Visit and look. Stand at the counter and see whether a customer could find the code.
- Decide what you now know. If it is "working as designed and quiet", note it. If it is "no route in place", fix that.
What not to do
- Do not rank a silent branch as the best performer.
- Do not reward a manager on the absence of complaints alone.
- Do not assume that because customers have not complained they are satisfied.
- Do not blame the manager before you have checked that the channel works.
- Do not treat every quiet branch the same way. A new branch, a small branch and a branch that has recently gone quiet need different questions.
The same applies to the whole network
The same logic applies at the top. If only a small share of customers across the group ever send a message, the picture you have is a picture of those who did. That is useful, but it is not a census.
Whether enough customers send messages to make a branch view useful is something each business finds out by running it, and nobody can tell you in advance. Treat the first weeks as a test of the channel itself, not only of the branches.
Where Outhentik fits
Outhentik shows coverage on the daily brief: which locations sent messages in the period, which have gone quiet and which have never received one. A branch with no messages shows as unknown, not as fine. A location with too few mentions of a topic is marked as low evidence and is not ranked.
Outhentik cannot make customers send messages. Head office decides where the code goes, whether staff mention it and who owns the callbacks. It supplies the code, the link and the view that shows where the gaps are.
Frequently asked questions
Does a branch with no complaints mean it is doing well?
Not necessarily. It may be doing well, or customers may have no easy route to complain, or they may not bother. Silence on its own cannot tell you which.
What is coverage?
Coverage is whether a location produced any messages in the period. It shows whether you can see the branch, not how good the branch is.
How do I tell if a quiet branch has a broken channel?
Check that the code is displayed where customers can see it, that the link works from a phone and that it is being sent. Compare with similar branches and ask the manager how it is used.
Should I worry about a branch that used to send messages and stopped?
It deserves a look. Something may have changed: a lost code, a new manager or a different process. Find out before assuming anything.
How should I treat a new branch with no messages yet?
As unknown. Give it time and make sure the channel is in place from the start.
Can I use the absence of complaints as a performance measure?
It is risky. It rewards silence, which can come from a weak channel as easily as from good service. Use it only alongside other signals.
How do I get quiet branches to produce more messages?
Head office decides where the code goes, whether staff mention it, and how customers are asked after a visit. Fix the route first, then see what comes back.
Try Outhentik free for 7 days, no credit card required
Outhentik gives head office a direct line from customers at every branch: a case with an owner for each customer who asks to hear back, every message read the same way, and a daily view of which problems repeat and where. For a head office reading silent branches, a location with no messages shows as unknown, not as fine.