How to reply to a 2-star review (with examples)

A 2-star review is the hardest one to answer. It is not angry enough to dismiss and not warm enough to thank. Something genuinely went wrong for that customer, and the people reading your reply are not the reviewer — they are future customers deciding whether a business that falls short handles it well.

Below is a structure you can reuse, two worked examples (one service delay, one product quality complaint) and the lines that make a reply worse. The example reviews and replies are written for illustration, not taken from a real customer.

What a 2-star review is actually telling you

A 2-star review is usually a mixed experience, not a disaster. The reviewer often says part of the visit was fine and part was not. That matters, because the reply should not read like a blanket apology for everything — it should be precise about the part that failed.

Two failure modes are common. The first is arguing the facts in public: quoting timestamps, camera footage, order numbers and staff rotas until the reply reads like a legal defence. The second is the opposite — a paragraph that could be pasted under any review in your category, which tells the reader you are replying for appearance's sake.

There is also a policy floor. A reply from the owner is content on your Google Business Profile, and Google's Prohibited and restricted content policy applies to it. That policy says plainly: do not share private or confidential personal or business-related information in this public forum. So no customer details, no booking references, no employee disciplinary matters, no medical or financial specifics. The policy is at https://support.google.com/business/answer/7400114.

The four-part structure

Write the reply in four moves, in this order:

• Name the specific thing that went wrong, in the customer's own terms. Not 'your feedback' — the 25-minute wait, the peeling finish, the missed callback.
• Say what should have happened instead, in one sentence. This sets your standard without accusing anyone.
• State one thing you have actually done or are doing. Only what is true today. If you do not know yet, say you are checking and come back to it.
• Move the next step to a private channel, and sign it with a name and a role.

Aim for 60 to 120 words. Long replies read as defensive; replies under 40 words read as dismissive. Keep anything of value — a refund, a credit, a free redo — out of the public reply. Negotiating money in public turns every reader into a potential complainant, and making help conditional on the review being edited or removed is a line you should not cross.

Worked example 1: a service delay

The review, as a customer might write it: "Booked a table for 7pm on Saturday. Waited 25 minutes for drinks and nobody seemed to know whose section we were in. Food was good when it arrived."

The reply: "Thank you for writing this, and for being specific. A 25-minute wait for drinks after a 7pm booking is not the start to an evening we want anyone to have. A full Saturday should still mean drinks on the table within ten minutes of sitting down, and on your visit it did not. I have shared the timing with our floor and bar leads and we are reviewing how orders are taken at the start of a sitting. If you would like to tell me more, call the number on our profile and ask for me. — Alex, front of house manager"

Why it works:

• It repeats the specific failure — 25 minutes, drinks, a 7pm booking — so the reply could not have been written for anyone else.
• It sets a standard (ten minutes, even on a full Saturday) instead of apologising vaguely.
• It promises one internal action you can actually verify, not 'we have retrained all staff'.
• It offers a real next step without publishing a personal email address or direct phone number, which is also the safer reading of Google's rule on private information in public threads.
• It is signed. Unsigned replies read as automated.

Worked example 2: a product quality complaint

The review: "Water pump replaced in March, leaking again two weeks later. Was told at the desk it was not your problem. Will not be using you again."

The reply: "A pump we fitted leaking two weeks later is something we should have looked at that week, and being told it was not our problem is not how we want that conversation to go. Parts we supply carry a 12-month warranty, and a leak inside that window is a fault we investigate rather than a judgement call at the desk. I have asked our workshop manager to pull your job sheet and the supplier record. Please call the number on our profile and ask for him, and we will get the car back in to check it properly. — Sam, service manager"

Why it works:

• It neither admits nor denies liability for a fault that has not been diagnosed. It accepts responsibility for the process, which is the part you can be certain about.
• It quotes a warranty term only because that term exists and is checkable. Never cite a policy you have not confirmed.
• One action, one named internal owner, one private channel.
• No public offer of a refund. If a refund is the right answer, it is a private conversation, and it is not a price on the review.

Lines that make a reply worse

Swap these on sight:

• "We are sorry you feel that way." becomes "We are sorry the fitting ran 40 minutes late."
• "Our records show..." becomes "I have checked the timeline and would like to take you through it directly."
• "This is the first we have heard of it." becomes "Thank you for telling us — I have asked for the job record today."
• Naming the member of staff who served them, or discussing any action taken against them. Personnel issues are handled internally; in public you say you are looking into it.
• Repeating the customer's details beyond the first name they already used, or anything medical, financial or tenancy-related. Google's policy is explicit about private information in public threads.
• Arguing in the reply about whether the review is fake. If you believe it breaches policy, report it through the process on Google's 'Report inappropriate reviews' page (https://support.google.com/business/answer/4596773) and keep the public reply short and neutral while you wait.

A five-minute process you can run every time

1. Pull the record first: booking, job sheet, ticket, order. Reply from facts, not from memory.

2. Draft outside the reply box. Write the four parts, then cut to under 120 words.

3. Strip anything that identifies the customer beyond the name they already published, and anything about money.

4. Check that every promise in the reply is already true.

5. Publish, then log the complaint where your team will see it, with one owner and a date to close it.

6. If you do not have the facts yet, publish a short holding reply and edit it once you do. "I have asked our manager to check what happened on your visit and I will come back to you here" is a legitimate reply; silence is not.

If you are replying on behalf of a client rather than your own business, Google's Business Profile API policies require the business's authorization before you respond for them: https://developers.google.com/my-business/content/policies.

Where Ratingly fits

Ratingly drafts replies like the two above from the review text plus your own policies and facts. You approve or edit before anything is published — nothing goes out without your sign-off, and we do not ask customers to change or remove reviews.

Start with a free audit of your last 90 days of reviews at audit, see how drafting and approval work at how it works, and check pricing when you are ready. If you manage reviews for several clients, the agency setup covers multi-location routing and reporting.