To track and compare customer complaints by location, you need three things: a way for complaints to reach head office from every branch, one scheme for sorting them so a complaint at branch 40 is counted like one at branch 3, and a way to mark branches with too little data as unknown instead of fine. Spreadsheets, helpdesks, survey tools, review tools and purpose-built feedback tools can each do part of this. The part most of them skip is the fair comparison.
This guide covers the five kinds of tool, what each can compare, and the checks that matter before you commit.
Why comparing branches is harder than counting complaints
Counting is easy. Fairness is the problem. A busy branch gets more complaints than a quiet one simply because more people go through it, and a branch where customers feel comfortable speaking up looks worse than one where they stay silent.
There are three traps in a raw count. Volume differs, so a bigger branch tops every list. Wording differs, so one team's "slow service" is another team's "wait time" and the totals never join up. Silence is ambiguous, because a branch with no complaints might be excellent or might be a branch whose customers have no route to you.
A comparison tool earns its place by dealing with these. A tool that only produces a bar chart of totals gives you the first trap in graphic form.
The five kinds of tool
Spreadsheets
A shared sheet with a row per complaint and a column for the branch is the cheapest way to start, and it teaches you what you want to track. It stops working when branches enter data differently, because you are the only one reading the free text, and there is no owner or clock unless you build them.
Use it for a first pass across a few branches. Move on when you spend more time cleaning rows than reading complaints.
Helpdesk and ticketing tools
A helpdesk gives every complaint a ticket with an owner and a status, and many can tag a branch. They are built for support teams answering inbound requests, so the branch comparison usually depends on whoever tags the ticket and how consistently they do it.
Use one if you already have a support team and a good tagging discipline. Ask who decides the category of each complaint, and whether it is the same person for every branch.
Survey tools
Survey tools collect scores and set answers across branches, which makes them good at comparing a number between locations. They are weaker at telling you what went wrong, because the customer picks from your list instead of using their own words.
Use one for a regular score. Ask how it handles the free-text answer, and whether a complaint becomes something anyone owns.
Review and reputation tools
These collect public reviews for each location and often show them side by side. Reviews are public and tend to come from people with strong feelings either way, and a single branch may have too few to compare with another. They are useful as one signal, not as the full account.
Use one to watch what is said publicly. Do not treat a review count as a complaint rate.
Purpose-built feedback and recovery tools
These collect messages from customers, sort them with one scheme and show them by branch, often with a way to follow up. Outhentik is one example. Customers reach head office directly by scanning a code or opening a link, and every message is read the same way at every branch, in Arabic or English. A problem raised at two or more branches becomes an issue on the daily brief, and a customer who asks to hear back becomes a case with an owner, a state and a clock.
Use this kind if the comparison is the point and you also want the follow-up in the same place. Ask any vendor in this group how the tool stops a branch with a handful of mentions from being ranked against a branch with many.
What a fair comparison needs
One scheme for every branch
Every message should be sorted the same way, whichever branch it came from and whichever language it was written in. If two people read two branches, you are comparing the readers.
The message behind every number
A figure on a dashboard should lead to the actual messages. Without that, you cannot tell a real pattern from a misread, and the branch manager will dispute it.
A rule for thin data
A branch with only a few mentions of a topic cannot carry a conclusion. Outhentik marks a location with fewer than five mentions of a topic as low evidence, shows it muted and does not rank it. Whatever tool you choose, ask what its rule is, because a ranking without one will put the wrong branch at the top.
Silent branches shown as unknown
A branch that sent nothing is not a branch with no problems. The view should show coverage: which locations produced messages in the period, which went quiet and which have never produced any.
A way to tell a pattern from a bad day
A problem at three branches is a different decision from a bad day at one. Look for a tool that shows how many branches an issue appears at and since when, not only how many times it was mentioned in total.
What not to do
- Do not rank branches on raw complaint counts.
- Do not let each branch enter and categorise its own complaints, because then you are comparing branches by how they report.
- Do not read a quiet branch as a good one.
- Do not make decisions on a handful of mentions.
- Do not expect any tool to make customers send messages. Where the code goes and whether staff mention it are your decisions, and whether customers send enough to make the comparison useful is the first thing every rollout finds out.
Checklist before you choose
- Who reads and categorises each complaint, and is it the same reader for every branch?
- Can I click from any figure to the original message?
- What happens to a branch with very little data?
- How does a silent branch appear?
- Does a complaint ever get an owner and a clock, or is it only counted?
- What can a branch manager see, and is that limit enforced in the database or only on the screen?
- What does it cost per location and per seat?
Frequently asked questions
What is the best tool to track customer complaints by location?
It depends on what you need. A spreadsheet works for a first pass, a helpdesk suits an existing support team, and a purpose-built feedback tool suits a head office that wants one scheme across branches and a follow-up process in the same place.
How do I compare complaints fairly between a big branch and a small one?
Compare shares and patterns instead of totals, and do not rank branches with very little data. Look at how many branches an issue appears at, not only how many times it was mentioned.
Can I do this in a spreadsheet?
Yes, for a few branches and a short period. It becomes hard once several people categorise complaints differently or once you need an owner and a clock on each one.
Why not rely on online reviews?
Reviews are public, tend to come from people with strong feelings and are often too few per branch to compare. They are a useful signal alongside what customers tell you directly.
How do I know if a branch with no complaints is doing well?
You cannot tell from silence alone. Look at coverage, meaning whether customers at that branch had a route to reach you and whether any messages came in during the period.
Should branch managers see other branches' complaints?
That is a policy choice. In Outhentik, branch managers see their own locations only and get no network comparison, which is enforced in the database.
How many complaints do I need before the comparison is useful?
There is no fixed number that fits every business, and no vendor can know yours in advance. Run it across a set of branches for a few weeks and see which locations produce enough to read.
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 business comparing complaints by location, that means one scheme for every branch and a view that shows silent branches as unknown.