A review-response procedure a crew can run at nine at night without calling the agency

A one-star review lands on a Saturday. The owner sees it on a phone, in a truck, ten minutes after finishing a job that went badly. Whatever gets typed in the next thirty seconds is permanent and is written in front of every future customer. The procedure exists for that moment, not for the calm Tuesday when a marketer has time to draft something. It also has to survive being run by three different people who will never all be in the same room.

The riskiest thirty seconds in a trade business is an owner replying to a one-star review from a phone, in a truck, ten minutes after the job that caused it.

1. 01

   The response is written for the next reader, not for the reviewer

   The reviewer has already decided. The audience is the person reading three months later deciding whether to call. That single reframe changes almost every sentence a business would otherwise write, and it is the first line of the procedure for that reason.

2. 02

   The dispute test is deliberately narrow

   Contest a review only where there is a clear factual error or a clear breach of the platform's own content policy. Never publish private personal details about a reviewer, and never make an accusation. A business that argues in public has lost regardless of how the platform rules.

3. 03

   Five templates is four too many

   The first version carried a template per scenario and none of them were used, because choosing between five options under pressure is harder than writing from scratch. Three shapes covered everything that actually arrived.

4. 04

   Unanswered five-star reviews are the bigger miss

   Almost every procedure is built around bad reviews. The positive ones are the ones the business has earned and left sitting, and they are the cheapest place to demonstrate that someone is home.

**88% of consumers are more likely to use a business that responds to reviews**, and **57% only use businesses rated 4★+** (BrightLocal), while in home services only **52% of calls are answered** in the first place (Invoca 2026). Reviews are the cheapest media a trade business owns; the response procedure is what keeps that media working after hours.

The procedure is one page. It sorts every review into three shapes: acknowledge and thank, acknowledge and take it offline, or acknowledge and correct a fact. Each shape carries an opening, a middle and a close, with the specifics left blank because the specifics are the only part that reads as human. It names one owner and one backup, sets a response window measured in working hours rather than days, and carries two prohibitions in bold: no private details, no accusations. The dispute checklist sits underneath as four yes-or-no questions, and anything failing one of them is answered rather than contested. Every review and response is logged with a date.

1. 1

   Week 1

   Response shapes drafted

   Three shapes with openings, middles and closes, specifics left blank

   Owner: OmniFlow

2. 2

   Week 1

   Ownership and window set

   One owner, one backup, response window in working hours

   Owner: OmniFlow + client

3. 3

   Week 2

   Dispute checklist

   Four-question test, plus the two standing prohibitions

   Owner: OmniFlow

4. 4

   Week 2 onward

   Log and latency

   Every review and response dated, latency reported monthly

   Owner: Client + OmniFlow

This entry makes no performance claim. It shows a written operating procedure for handling reviews under pressure, the three shapes it sorts every review into, the four-question test it applies before contesting one, and the two things it refuses to do in public under any circumstances. The only figure the procedure generates is response latency, which is a count of working hours rather than an outcome, and it exists so that the procedure can be corrected when it slips rather than to demonstrate that it worked.

These are the surfaces this engagement is run and measured from, shown with representative figures built around the benchmarks cited on this page. Every account we run reports into views like these, and you keep ownership of all of them.

The first version had five response templates and a decision tree to choose between them. Nobody used it once, because the cost of navigating the tree was higher than the cost of typing something. Collapsing to three shapes with blanks in the middle was the change that made it get used, and it should have been the starting point.

Real client work that shipped. No performance figures are published, because none have been verified and approved for release. See all our work