Replying to reviews at a 25-location car wash chain: 300 a month, read by hand every morning

For the executive who decides

• The customer acts
• The machine acts
• A person decides
• Nothing runs

An illustration built from the chain's numbers: the times are examples, and the membership's value is an estimate.

1The job

Reading and replying to customer reviews on Google, Yelp and Facebook, for every location. A US car wash chain with 25 locations, about 300 reviews a month.

2The number today

I think we get about 300 reviews a month across Google, Yelp, and Facebook. Right now, one of our teammates checks each of our sites every morning. That is up to 75 pages a morning (25 locations on three sites). Checking them and writing the replies comes to about 290 hours a year: about $11,000 at US median pay for a marketing specialist, or about $3 a review. The poster adds that the replies are "just that slow, and half of them sound the same." Then the members. About 30 reviews a month are complaints. If one in three comes from a member worth about $200, about $2,000 a month is at risk: $24,000 a year.

Estimate. The 290 hours assume 20 seconds a page and 3 minutes a reply; the teammate's own count replaces them. The 30 complaints use the 10.2% of reviews at one to three stars on a typical local business's page (car washes rate lower, so it is likely more). One member in three is assumed. $200 is the cheapest public membership times the average stay. $2,000 a month is the most a fast, right reply could keep; it will keep less. The chain's own figures replace all of these.

3The verdict

Hand over the sorting and the first draft. Keep the damage claims.

• Hand to the machine: watching every location's Google and Facebook pages, sorting each review by location and type within the hour, drafting a reply that names one detail from the review, and posting the thank-you replies to four and five star reviews on Google once two weeks of drafts have passed a person's check.
• Keep with a person: anything about damage, refunds, injuries or a staff member by name; every reply to a one to three star review, approved before it posts; and every reply on Yelp and Facebook, posted by your own team. Yelp allows only the business itself to reply, and Facebook gives outside software no way to post one.
• Not yet: posting a complaint reply without a person's approval. Offering a free wash, a refund or a repair. Replying to a review you plan to report as fake. Watching the Yelp pages, until a way in is tested; the teammate checks those 25 each morning, down from 75.

What the teammate is for now: the complaints, the Yelp pages, the Yelp and Facebook replies, and spotting what keeps going wrong at one location. The GM sees only the damage claims, each one within the hour, with a draft.

4The bill

To run it: about $25 a month in parts, if you have it built. The scheduler that runs the steps is 20 euros, about $22 (n8n). The drafts cost about $0.41 a month for 300 (Claude Haiku 4.5). Google's reply connection is free. Add the build and its upkeep. It replies on Google. For Yelp and Facebook it writes the draft, and a person posts it.

The other routes, at 25 locations: one shared inbox with no drafts, $296 a month (BrightLocal Grow). Software that drafts with AI, about $1,500 to $2,000 (GatherUp at $60 a location, if that rate holds past 10 locations; Reputation at $80). Software that replies on all three sites, $3,625 to $4,500 (Marqii, $145 to $180 a location). A done-for-you service, about $350 for 300 reviews plus a fee it does not state (Marqii); Yelp's rules say only the business may reply there.

What that means: at this volume, every ready-made route that drafts costs more each month than the teammate's time today, about $915. Per-location prices suit chains with many more reviews per site; this chain has about 12.

Checking: every draft read before it posts for the first two weeks, about 30 seconds each, about 2.5 hours a month. After that, the check time is not known until it is counted.

Estimate. About $915 a month is the 290 hours above at the median wage, not the chain's payroll. The 2.5 hours assume 30 seconds a draft.

5Owner and off switch

The marketing teammate owns it: they know the locations, the tone, and what each site allows. The GM owns the damage-claim approvals. The off switch: pause the hourly run with one switch. Nothing new posts, and the teammate goes back to the morning check. They should be able to do it in under a minute, and try it once in week one.

6The brief to hand your builder

The job: read every new review at all 25 locations, sort it, draft a reply, post thank-you replies on Google, and send the rest to the right person.

Today: about 300 reviews a month on Google, Yelp and Facebook; one teammate checks every page each morning; the GM approves anything about damage.

Done when: for two weeks, every review is sorted within an hour of posting; every one to three star review is answered within one business day; no reply about damage posts without the GM's approval; no two replies in a week use the same wording; and the share of replies a person had to change falls week on week.

It may never, on its own: reply to a review about damage, a refund, an injury or a named staff member; offer a free wash, a refund or a repair; say the wash was or was not at fault; post on Yelp; or reply to a review marked to report as fake.

You get from us: 50 past reviews with the replies we liked; the 25 locations and who runs each; the GM's rules for damage claims; the words we never use.

We own: the logins for every review site, the workflow account, and the billing.

We get back: a morning list of every review: location, stars, type, what was posted, and what is waiting for whom.

Ask whoever sets it up	A good answer	A bad answer
What happens to a review about damage?	No public reply goes up. The GM gets it within the hour with a draft, and nothing posts until the GM approves.	"It handles negative reviews with empathy."
How do Yelp and Facebook replies get posted?	Drafted in the same list, then posted by your own team on each site, because Yelp lets only the business reply and Facebook has no way in for outside software.	"We post everywhere automatically."
How will we know the replies sound the same, or say something wrong?	A weekly count of replies a person changed, a check that no two replies in a week match, and a person reading every draft for the first two weeks.	"It's trained on your brand voice."

For the operator who builds and runs it Paid layer

7The working set

• Trigger: every hour, read new reviews: Google through the Business Profile interface (read many locations at once, reply per review; free, needs Google's approval and profiles 60+ days old); Facebook recommendations through the Graph interface (read only). Yelp: its public interface gives only three excerpts per business, so the teammate checks the 25 Yelp pages each morning until Yelp's new-review emails are tested as a feed (not yet verified).
• Steps: sort each review into five types: praise (four or five stars, no complaint), complaint (one to three stars), damage claim (words such as scratch, cracked, mirror, dent, broke, wiper, antenna, claim), billing (charge, cancel, refund, membership), suspected fake (no visit on record, or the teammate's call). Draft a reply under 60 words that names one detail from the review, wording varied. Post praise replies on Google after the two-week check. Queue complaints for the teammate. Send damage claims to the GM with the draft and no public reply. Send billing to the teammate. Suspected fakes get no reply until the teammate decides whether to report them.
• Data: one record per review: site, location, review ID, stars, text, posted at, type, draft, approved by, posted at, hours to reply, changed by a person or not, claim opened or not.
• Review step: the teammate clears the complaint queue each morning; the GM clears damage claims each day; for the first two weeks the teammate reads every draft before it posts, praise included.
• Alerts: a damage claim waiting more than 24 hours (car wash incident guidance: customer contact within 24 hours); a one to three star review unanswered after one business day; a Google reply still not showing after 24 hours (Google checks every reply, usually within 10 minutes); two replies with the same wording in a week; and the wrong-but-green count, replies a person changed or deleted after they posted.
• If it breaks: what you see: reviews with no reply in the list, or no morning list. Check first: Google access for the account (most silently rejected replies trace to account restrictions, not wording) and the workflow's last run. Safe fix: pause the hourly run; the teammate goes back to the morning check.
• Cost per review: about $0.08: the workflow runner at about $22 a month over 300 reviews ($0.07) and the draft at about $0.0014 (Claude Haiku 4.5). Ready-made software with drafts is about $5 to $15 a review at this volume ($1,500 to $4,500 over 300).
• Baseline, before switch-on: two weeks of counts: reviews in by site and location, hours from review to reply, the share of one to three star reviews answered within a day, and the teammate's minutes each morning.

Estimate. The money uses about $200 a member and one complaining member in three until the chain gives its own members, prices and complaint count; the time uses 20 seconds a page and 3 minutes a reply until the teammate counts.