Free Google review reply generator

A reply to a Google review is public, it sits under the review for as long as the review stays up, and it is often the last thing someone reads before they call you. It is written for the next customer as much as for the reviewer.

An owner who answers a two-star review calmly reads better than one who has no two-star reviews at all. A page where the good reviews got a thank-you and the bad ones got silence tells a stranger which kind of feedback you listen to.

Most businesses we work with answer about a third of their reviews, and it's rarely for lack of caring. Each reply costs ten minutes of low-grade dread, so the queue grows. The generator takes the blank page away: you start from a draft and spend your minutes on the one detail that makes it yours.

It runs the rules from our use case, Answer every Google review without sounding like a template, as templates in your browser. No AI model sees the review. Each rule is there because the reply fails without it:

• Under 60 words. Replies are skimmed. A paragraph of gratitude under a one-line review reads as automated, which is the thing you're trying not to be.
• One specific thing the reviewer said. A name, a dish, a room, a date. It's the difference between a reply that could belong to any business on the street and one that proves somebody read the review. The generator suggests candidates from the text; you pick one.
• Thanks once, at most. Twice sounds like a script. A negative review gets no thank-you at all, because thanking someone for a bad night reads as not having listened.
• No exclamation marks, no "we appreciate your feedback", no "we strive to". Those phrases are the fingerprint of a template, and customers have learned to skim past them.
• Signed with a first name. A reply from "Sam, the owner" is from a person. A reply from "The Management" is from a policy.
• Two drafts in different tones. Choosing between two takes five seconds and gives a better result than editing one, and it stops your replies settling into one rhythm.

Where the generator can't know something, it leaves a gap in brackets rather than guessing: what went wrong, what you're changing, where the reviewer can reach you. A reply that invents a fix you haven't made is worse than no reply.

Some reviews shouldn't get a fast public reply, and the generator says so instead of writing one. It flags a review that:

• mentions a lawyer, a court, the police, a regulator or a chargeback;
• describes illness, an injury, an allergic reaction or a safety problem;
• describes how a named member of your team behaved, or anything like harassment or discrimination;
• claims you overcharged, never refunded, lied or stole.

Each of those is a fact you need to check before you say anything in public, and some of them are the opening of a legal problem. A reply written at speed can admit something that isn't true, or deny something that is. Find out what happened, talk to the person involved, and if there is any chance of a claim, ask a lawyer before you reply.

The check is a word list, so it errs toward flagging. A review that says the pasta made someone "sick with envy" will get flagged. That costs you one read; missing the real one costs a lot more.

A one- or two-star reply has three jobs, in this order:

• Name the failure in plain words. "The wait for a table was forty minutes, and that isn't good enough" beats "we're sorry your experience didn't meet expectations". The reviewer wants proof you understood; the next customer wants proof you won't argue.
• Say what changes. One concrete thing: a second person on the phones on Saturdays, a new booking system, the north wing next in the renovation queue. If nothing is changing, say you'll look into it, and then do.
• Move it off the platform. Give a direct email or phone number. The details of a refund or a complaint don't belong in public, and a reviewer who gets a real answer privately sometimes updates the review.

What not to do: apologise three times, explain your internal causes (the new hire, the supplier, the storm), or argue about facts in public. Each of those makes the reply about you. If the reviewer is wrong on a fact, fix it privately and keep the public reply to the three moves.

A three-star review is the easiest win on the page. The reviewer liked something and something let them down. Thank them once, agree about the part that fell short, say what changes, and invite them back.

A five-star reply should be the shortest thing on the page: thanks, the one detail, and a line about next time. If the review names a person on your team, pass it on, and say so in the reply. Staff read these too.

A review that is three words long ("Great, thanks guys") may not need a reply at all. A thumbs-up and no reply beats filler, and the generator will tell you when a review is that short.

Under the drafts is the prompt from our use case with this review filled in. Paste it into ChatGPT or Claude and you get two drafts written by a model instead of by templates, which reads more naturally on long or unusual reviews.

The prompt starts with a business profile, and the profile is the part people skip. Fill it in once: what you do, who replies, three things people praise you for, two things you know you're weak on and what you're doing about each, and what you'll never say in public. With it, the model writes replies specific enough that regulars notice. Without it, you get the generic replies you already have.

Paste one review at a time. Given ten, a model writes ten variations of the same reply, and the sameness is exactly what makes a review page look automated.

Read every reply before it goes up. Replies are public and permanent, and no tool, ours included, should post to your profile without a person reading it first. Kill the replies that are technically fine and say nothing. Answer the flagged ones yourself.

Clearing a year of backlog takes an afternoon: oldest negative reviews first, because those are the ones being read. The full use case has the profile template, the prompt and the variations we run for clients, including a monthly summary of reviews for your team.