Who Should Reply to a Bad Review — HQ or the Branch? You’re Asking the Wrong Question

A one-star review comes in for a location inside a 40-store chain. Headquarters wants to review it before anything posts — brand risk is real, and a bad reply becomes a screenshot fast. The location manager wants to answer today, in their own words, because they were actually there, and a customer can tell a real answer from a corporate one on sight. Neither side thinks they're being unreasonable. Neither one is, entirely — which is exactly why this argument keeps recurring at almost every multi-location business past a handful of locations, instead of getting settled once and staying settled.

The debate everyone's already had, and lost

Centralize approval, and the organization rediscovers the exact problem full centralization always causes: a small team, physically and experientially removed from the location, approving or rewriting a reply about something it wasn't part of. The reply reads generic because it is — whoever wrote it wasn't in the room. Delegate fully, and the opposite failure shows up almost as fast: one manager's bad day, or one badly chosen sentence, becomes a permanent public artifact standing in for the entire company, with nothing between 'send' and public visibility to catch it. Most multi-location businesses have already tried both extremes. Neither one holds — not because anyone picked the wrong policy, but because the policy was answering a question the reply itself doesn't actually ask.

The org chart is answering the wrong question

The instinct is to assign reply ownership the way most internal decisions get assigned: by who's responsible for the thing on paper. Marketing or brand technically owns reputation, so replies default to marketing. Operations technically owns the location, so replies default to the location. Both are defensible readings of an org chart. Both miss what actually determines whether a reply is good, which has nothing to do with who's accountable for optics and everything to do with two much narrower, more specific things: knowing what actually happened, and having the standing to promise something will change because of it.

Context and authority almost never live in the same person

The location has the first one. A manager, or whoever was on shift, knows within minutes whether the wait really was forty minutes, whether the order really did go out wrong, whether the complaint is fair, exaggerated, or fabricated entirely. What that person usually doesn't have is the second: the authority to approve a refund past some threshold, grant a policy exception, or commit to a fix that reaches beyond their own four walls. That sits with someone above them — who, in turn, almost never has the first thing. They're reading the review cold, with no more first-hand knowledge of what happened than the customer who wrote it.

Put those two people in the same reply and you get exactly the failure each side already recognizes on sight. Context without authority reads sincere but powerless: 'I'll pass this along to the right person.' Authority without context reads sincere-sounding and interchangeable: 'We take this seriously and are looking into it' — words that would fit any complaint, at any location, on any day, because that's genuinely all the writer has to work with. Neither failure is a writing problem. Both are a structural one — the reply needed both ingredients, and whoever wrote it only had access to one.

Fixing the structure, not picking a side

The fix isn't finding someone who holds both — at real scale, across dozens or hundreds of locations, that person doesn't exist. It's making sure whoever's actually writing the reply can reach whichever ingredient they're missing, fast enough that the reply doesn't sit for three or four days while someone tracks it down. Concretely: the person with context should default to drafting, because only they can make the reply specific instead of generic. The person with authority shouldn't be a gate every reply passes through — they should be a fast, narrowly defined escalation path for the small set of things that genuinely need it: a refund above a set amount, anything alleging discrimination or a safety issue, anything that reads like it could become legal. Everything else moves at the speed of whoever actually knows what happened, not the speed of whoever has to sign off on it.

Why this is a permissions problem before it's a policy one

A written policy describing this split survives about as long as it takes for the first edge case to show up, unless the software backing it actually enforces who can do what. A location manager needs to be able to draft and post the routine and moderate cases without waiting on anyone — and headquarters needs real visibility into what's going out, plus a genuine, fast way to step in on the narrow set of cases that warrant it, without that visibility turning into an approval bottleneck by default. That's a role-permissions problem, not a values one: give context-holders drafting authority and give authority-holders a real-time view plus a narrow override, and most of the debate about who 'should' reply quietly stops being a debate at all.

The debate ends when the two questions stop getting confused

'Who should reply to this review' and 'who's responsible for our reputation' feel like the same question, and answering the second one is what keeps producing the wrong answer to the first. Reputation is a company-wide concern; a specific one-star review is not — it's a specific, local, factual thing that happened to one customer, and the reply is only as good as how close it comes from that fact. The businesses that stop fighting about this aren't the ones that finally picked a side. They're the ones that stopped asking who owns the reply, and started asking, for each one: who actually knows what happened, and does anyone need to sign off — then built a process, and picked software, around that question instead of the org chart.

FAQ

None of this is a call to abandon oversight, or to let every location say whatever it wants. It's a call to stop routing every reply through the same gate regardless of what it actually needs. Most reviews need someone who was there. A few need someone who can promise a fix beyond that one location. Very few need both. Confusing those three categories — treating every reply as if it needs the same level of sign-off — is the actual reason this keeps being a fight, long after everyone involved is tired of having it.