Reputation Management Case Study: A Step-by-Step Walkthrough
The fastest way to understand reputation management isn’t a checklist — it’s watching one engagement unfold from first phone call to steady state. What follows is an illustrative walkthrough, a composite built from the pattern we see over and over at Salterra: a good business with an invisible reputation problem, a system installed to fix it, and a crisis along the way that tests whether the system actually holds.
- The Starting Point: A Business That "Seemed Fine"
- Phase One: The Diagnostic Audit
- Phase Two: Fixing the Root Cause Before Chasing Reviews
- Phase Three: Building the Review Acquisition System
- Phase Four: The Response Protocol
- Phase Five: The Crisis — A Review-Bombing Incident
- Phase Six: Where It Landed
- What This Walkthrough Illustrates
We’re not naming a client or citing invented numbers here — the goal is to show the sequence of decisions and the reasoning behind each one, so you can run the same playbook on your own business or your own client’s.
The Starting Point: A Business That "Seemed Fine"
Call it a mid-sized HVAC company, three trucks, family-owned since the late 1990s. The owner didn’t think he had a reputation problem. Revenue was steady, referrals still came in, and nobody had mentioned reviews in a sales call. That’s usually the first sign an audit is overdue — reputation problems rarely announce themselves until they’ve already cost you a deal.
On the surface: a 3.9-star average on Google, 26 reviews, last one posted eight months prior. That’s not a five-alarm fire. It’s a slow leak. In a category where competitors were sitting at 4.6+ with 150+ reviews and posting weekly, 3.9 and stale wasn’t a red flag to the owner — it was a red flag to anyone comparing him against the next listing down.
Phase One: The Diagnostic Audit
Every engagement starts the same way: before touching anything, map the current state completely. That means pulling every review across every platform the business appears on — not just Google, but Yelp, Facebook, Better Business Bureau, Angi, and any industry-specific directory — and reading each one, not just skimming star counts.
The read-through matters more than the aggregate score. In this case, the negative reviews clustered around two specific complaints: missed appointment windows and unclear pricing on service calls. That’s a gift, not a problem — a scattered mix of unrelated complaints is hard to fix, but a repeated pattern points straight at an operational fix that will also solve the reputation issue at the root.
What the audit produced
- A platform inventory — where the business had a presence, where profiles were unclaimed or outdated, and where NAP (name, address, phone) data was inconsistent.
- A sentiment breakdown of existing reviews, sorted by theme rather than star rating alone.
- A gap analysis against three local competitors — review velocity, average rating, and response behavior.
- An owner interview, because the paper trail never tells you the whole story. In this case, the missed-window complaints traced back to a scheduling software that didn’t send confirmation texts — a two-week fix, not a two-year one.
Phase Two: Fixing the Root Cause Before Chasing Reviews
This is the step that gets skipped constantly, usually by agencies that treat reputation management as a review-generation service rather than a business function. You do not launch a review request campaign on top of an unresolved operational problem. Every new review you generate before fixing the underlying issue is a new chance for someone to write publicly about the thing that’s actually broken.
So the scheduling software got a confirmation-text feature turned on, and the pricing conversation got scripted — technicians were given a simple, consistent way to explain diagnostic fees and estimate ranges before starting any work. Small operational changes. Neither one glamorous. Both directly targeted at the two complaint themes the audit surfaced.
Phase Three: Building the Review Acquisition System
With the leak patched, it was time to open the tap. The system had three parts, and the order mattered:
Step 1 — Identify the ask moment
Not every customer interaction is a good moment to request a review. The team mapped the customer journey and picked the single highest-satisfaction touchpoint: the moment the technician closed out a job and the customer signed off on the invoice, in person, visibly satisfied. That’s a very different moment than “three days after the invoice, via automated email,” which is where most businesses default to and where most requests die unread.
Step 2 — Make the ask low-friction
A short, direct text message sent within the hour, with a single tap-through link straight to the Google review form — no login wall, no extra steps. We avoided review-gating (routing unhappy customers away from public platforms and happy ones toward them), which violates Google’s policies and creates exactly the kind of artificially clean review profile that erodes trust the moment someone leaves an honest negative one.
Step 3 — Track and adjust
Every technician’s request-to-review conversion got tracked individually. It turned out one technician had a 40% higher conversion rate than the others simply because of how he phrased the ask verbally before the text went out. That phrasing became the new script for the whole team.
Phase Four: The Response Protocol
Volume alone doesn’t fix a reputation — how the business shows up in the reviews it already has matters just as much. We built a response protocol before the review volume increased, not after, because once volume climbs, an ad hoc response habit turns into an ad hoc response mess.
The rules were simple: every review, positive or negative, gets a response within 48 hours. Positive reviews get a genuine, specific reply — never a copy-pasted “Thanks for the kind words!” Negative reviews get acknowledged publicly, briefly, without defensiveness, and moved to a private channel (phone call, direct message) to resolve the actual complaint. The public reply exists for the next hundred people reading that review, not to win an argument with the reviewer.
Phase Five: The Crisis — A Review-Bombing Incident
Four months in, the system got tested. A disgruntled former employee, terminated for cause, encouraged friends and family to post one-star reviews over a 48-hour window — eleven reviews, none from actual customers, all referencing vague, unverifiable claims about the business.
This is where a lot of businesses panic and either go silent or fire off angry replies. Neither works. The protocol here was methodical:
- Document everything — screenshots, timestamps, and any identifying pattern connecting the accounts (posting within the same hour, similar phrasing, no verified purchase history).
- Report through the platform’s formal process — Google has a mechanism for reviews that violate its policies (not affiliated with a genuine customer experience), and it takes a documented pattern seriously. Vague “this is unfair” reports get ignored; specific, evidenced reports get action.
- Respond calmly to any review that stayed up during the review period — a short, factual, non-defensive note that didn’t confirm or deny specifics, just signaled to future readers that something was off.
- Keep the review request system running — this is the part people get backwards. The instinct is to pause everything during a crisis. The better move is to keep generating legitimate reviews from real customers, because volume and recency are the fastest way to dilute a temporary spike of bad-faith reviews.
Seven of the eleven reviews came down within three weeks through the platform’s removal process. The remaining four stayed, diluted into a review profile that had grown by dozens of genuine reviews in the meantime.
Phase Six: Where It Landed
Reputation work doesn’t have a finish line, but there’s a point where the system becomes self-sustaining rather than something the business has to think about daily. Within roughly a year, the review count had grown several times over, the average rating climbed solidly into the range that competitors occupied, and — more importantly to the owner — sales conversations stopped starting with a customer’s guarded tone about “some of the reviews I saw.”
The operational fixes (confirmation texts, pricing scripts) also reduced the two original complaint themes to near zero in new reviews. That’s the real marker of success: not a star rating in isolation, but the disappearance of the pattern that caused the problem in the first place.
What This Walkthrough Illustrates
Reputation management done properly is never just “get more good reviews.” It’s diagnostic first, operational second, systematic third, and only then promotional. Skip the first two steps and you’re building a review-generation engine on top of an unfixed problem — which just means more people find out about it faster.
The crisis phase matters too, because every business with a real online presence will eventually face some version of a coordinated or bad-faith attack. The businesses that weather it aren’t the ones with zero negative reviews — they’re the ones with a documented process and a review base deep enough that eleven bad-faith posts don’t define the profile.
Frequently Asked Questions
Is this case study based on a real client?
It's an illustrative composite built from patterns we see repeatedly across engagements, not a single real business with verified figures. The sequence of phases and the reasoning behind each step reflect our actual process.
How long does a reputation management engagement typically take to show results?
Operational fixes can show up in new reviews within weeks. Meaningfully shifting an aggregate rating and review volume usually takes several months to a year, depending on starting point and customer volume.
What should come first: fixing the business problem or launching a review campaign?
Always fix the root cause first. Generating review volume on top of an unresolved operational issue amplifies the exposure of that issue rather than solving it.
Is it ever okay to selectively ask only happy customers for reviews?
No — selectively routing dissatisfied customers away from public review platforms (review-gating) violates most platforms' policies and produces a review profile that reads as inauthentic. Ask everyone at the same consistent moment in the journey.
What's the right way to handle a sudden batch of suspicious negative reviews?
Document the pattern, report through the platform's formal policy-violation process with evidence, respond calmly to anything that stays visible, and keep your legitimate review acquisition running rather than pausing it.
Do negative reviews ever get removed by the platform?
Platforms will remove reviews that violate their policies (fake accounts, no verifiable relationship to the business, harassment) when given clear, documented evidence — but they won't remove reviews simply because they're negative or unfair-feeling.
Terry has 30+ years in software and SEO. He’s the founder of Salterra Digital Services and SEO Spring Training, host of the Roundtable SEO Mastermind, and lead instructor at SEO University — teaching the exact tactics his team uses on client work.
Continue learning
Ready to master this?
This guide is one lesson from the Reputation & Review Management course. Get every lesson, framework and checklist — plus the full 38-course catalog — inside SEO University.
Practitioner-focused training across the full digital marketing stack — from technical SEO to conversion optimization and the AI search era. By Salterra Digital Services, since 2011.