Responding to Reviews and Flagging the Ones Google Might Remove

A bad review is not written for you. It is written for the next person standing in their driveway on a Saturday morning, staring at a bent track or a spring that let go, trying to decide which of the four garage door companies in their search results to call. That person will read your one-star reviews before your five-star ones, and they will read your response to each one just as closely. This guide is about writing that response well, and about the much smaller category of reviews that Google will actually take down, which is not the same category as reviews you simply do not like.

Review requests are one of the things our own lead-handling platform automates, so this is not neutral outside commentary on the review category. What follows is the same distinction we make with our own customers: a response is something you control completely, a removal is something Google controls entirely, and confusing the two wastes time you could spend on the response.

Which one you should probably pick

Every reply you write, no matter what other software touches your reviews, ends up posted through Google Business Profile itself. That makes the free, native reply tool inside your Business Profile the one piece nobody should skip, regardless of budget. Start there.

Layer in GatherUp if you want help with volume: it drafts a first-pass reply using AI, which is useful when a shop is catching up on a backlog of unanswered reviews, and it monitors your listing across more than a hundred review sites so you are not manually checking Google, Facebook, and Yelp on three separate days. It is worth a look especially if you are already using it, or considering it, to automate review requests, since response monitoring and request automation live in the same product.

Skip Broadly unless you actually want the full bundle. It handles review responses well enough, but it sells that ability inside a $799-a-month package that also includes a company website, an AI receptionist for phone and web chat, weekly social posting, and directory-listing sync. If review response is the specific problem in front of you, Broadly is five products to get one.

What each one actually costs

Neither GatherUp nor Broadly can make Google remove anything faster or more often than the free path does. Removal runs through Google’s own review of a flagged item against its own policy, and no vendor has a side channel into that process.

Before you start

• Confirm which specific person has owner or manager access to the Google Business Profile. “Someone at the shop has the login” is how a review sits unanswered for three weeks.
• Read Google’s own policy on prohibited and restricted content once, before your first flag, not while you are angry about a specific review. It is short, and it is the actual bar a flag has to clear.
• Decide your internal response-time rule now. Waiting until a bad review shows up to figure out how fast you will answer it means you decide under the worst possible conditions.
• If you have not generated your own Google review link or QR code yet, that setup happens first; this guide assumes reviews are already coming in and focuses only on what to do once they land.
• If you are weighing GatherUp, read it as a review-request and monitoring tool that happens to include AI drafts, and check it against your automated review request needs at the same time, not in a separate evaluation.

Writing a response that actually helps the next reader

A response that works on a trade review does four things, in this order, and then it stops: it acknowledges the specific job, it states the fact that was missing from the review, it offers a direct line to resolve it, and it ends. It does not re-litigate the review, defend every decision made on site, or match the reviewer’s tone.

Example 1: a legitimate complaint about a callback. “We did not get back to you the same day, and that is on us. We had a torsion spring emergency ahead of your call that ran long, and the callback should have gone out regardless. If the door is still an issue, call the shop directly at [number] and ask for [name], and we will get someone out this week.”

Example 2: a price complaint on a spring job. “Torsion springs are rated by cycle count and door weight, which is why two shops can quote different numbers for what looks like the same repair on the phone. We priced yours for a [specific detail, like a two-spring system rated to your door’s weight]. Happy to walk through the invoice line by line if that would help, call the shop and ask for [name].”

Example 3: a review that is clearly about a different company. “We could not find a job on our schedule matching this description, and we do not have a technician by that name. If you can confirm the company name and the approximate date, we are glad to help point you to the right business, or if this was about us, call the shop directly so we can sort it out.”

Notice what none of these do: apologize for something that was not wrong, promise a discount or a redo in the public reply, or include the customer’s address, price, or personal details beyond what they already put in the review themselves. A response is public. Treat it that way.

What Google will actually remove, and what it will not

Google’s own policy describes prohibited and restricted content in specific categories: fake or paid reviews, content posted by someone with a conflict of interest such as a current or former employee or a competitor, reviews that are off-topic or unrelated to an actual experience with the business, and reviews that contain hate speech, threats, or other content that breaks Google’s broader content policies.

What that list does not include is a review that is simply negative and true. A customer who accurately describes a longer-than-promised wait, a price they were not happy with, or a technician they did not like is inside the policy, however much it stings to read. Flagging a review like that does not get it removed, and Google’s own guidance on reading and replying to reviews is built around the assumption that most negative reviews stay up and get answered, not disputed.

The practical filter: before flagging anything, ask whether the review describes a real interaction with your business, even an unflattering one. If yes, it stays, and your job is the response. If the review is about a company you have never heard of, mentions an employee you have never employed, or reads like it was generated to pad a competitor’s complaint pattern, it is a flag candidate.

Flagging a review the right way

1. Sign in to the Google account connected to your Business Profile and open the reviews section, either through Google Business Profile directly or by searching your business name on Google and opening the reviews tab from there.
2. Find the specific review. Google’s interface places a flag or a three-dot menu near each review; the exact icon and its position has changed across updates, so look for an option labeled something like “Flag as inappropriate” or “Report review” rather than a fixed click path.
3. Choose the reason that matches the actual violation, not the closest one available. Picking “spam” for a review that is really just a bad price complaint does not help your case and does not change the outcome.
4. Submit and move on. Do not wait to respond publicly until the flag resolves. Respond to the review the same way you would any other, on your normal timeline, regardless of whether Google eventually acts on the flag.

Where AI drafting helps, and where it embarrasses you

GatherUp’s included AI reply drafts are genuinely useful for the mechanical part of the job: clearing a backlog of twenty unanswered five-star reviews with a thank-you that varies its wording instead of one copy-pasted line twenty times. That is a real time save, and it is the kind of task AI drafting is well suited to.

Where it gets worse is anything with actual content in it, a specific complaint, a price question, a scheduling failure. A draft written from the review text alone has no idea what actually happened on your specific job, so it tends to default to something generic, a version of “we’re sorry to hear this and value your feedback” that reads as exactly what it is to anyone who scrolls past three other reviews with the same shape. Read every draft before it posts. If it does not mention the actual job, rewrite it so it does.

Setting up Broadly, the bundle option

Broadly is the challenging pick in this guide, and the reason is not that it works poorly. It is that buying it to solve review responses means buying four other things you may not have asked for.

1. Sign up directly through Broadly’s own site; billing is self-serve and month-to-month, with no long-term contract stated on the vendor’s own pricing page.
2. Broadly’s team builds and launches a company website as part of onboarding, stated as live within about a week.
3. Connect a phone and text number for the included AI receptionist and missed-call text-back.
4. Connect your Google Business Profile and other listing sources so the reputation module can monitor and draft responses.
5. Set a social posting cadence if you intend to use that piece.
6. Review every AI-drafted response before or immediately after it posts, the same rule that applies to any AI drafting tool.

The part worth sitting with before you sign: Broadly’s AI receptionist is answering live calls, which for a garage door shop can mean triaging an emergency, a trapped vehicle, a door that will not close and secure a home. That is a materially different risk than an AI tool drafting a review reply you read before it posts. If the review-response piece is what you actually need, check what the quote-gated players like Podium and Birdeye actually require in their contracts before you assume a flat $799 bundle is automatically the simpler path; sometimes the sales-call option is not simpler, just harder to compare.

What usually goes wrong

Responding within the hour, angry. The reviews that do the most damage are not the negative ones. They are the negative ones a shop owner replied to at 11 p.m. the night they were posted, defensive and specific in a way that reads worse than the original complaint. Sleep on anything that stings before you answer it publicly.

A boilerplate reply on a specific complaint. “We strive for excellent service and are sorry to hear about your experience” answers nothing and signals that nobody actually read the review. If the complaint names a real detail, your reply should too.

Flagging every negative review, hoping. Time spent flagging reviews that are negative but true is time not spent writing the response that actually helps the next reader. Reserve flagging for reviews that meet Google’s actual criteria.

Putting private details in a public reply. An address, a specific dollar amount tied to a name, or details about a dispute in progress do not belong in a public response, even when the customer already shared some of it. What you post is permanent and searchable.

Only answering the negative ones. A profile where every five-star review sits unanswered and every one-star review gets a defensive reply reads as a business that only engages when it is under attack. Answer both, briefly, on the same schedule.

How to tell it is working

Track two things monthly, not weekly: how many days it typically takes from a review posting to a response going up, and whether a stranger reading your ten most recent reviews in a row would come away thinking the responses sound like the same business, consistent in tone, specific about the actual job each time. If your review count itself is thin enough that ten recent reviews spans a year instead of a month, the more useful fix is upstream of this guide, in how you are asking for reviews in the first place. If review responses are trailing more than a few days behind, or if a customer service issue named in a review keeps recurring across multiple months of reviews, that second pattern matters more than the star rating itself. A response can defuse one bad review. A repeated complaint across several reviews is telling you something about the job, not the review.