Reply within a day or two, thank the reviewer, apologise for how the experience felt without arguing the facts, say nothing about their claim, and move the conversation offline with a named contact. Write the reply for the next customer reading it, not for the angry reviewer. AI can draft it, but only from facts you supply.
Claim and delay reviews are different from "the crew was rude" reviews. They involve money, an insurer, the weather and a paper trail that belongs to the customer. Google's own advice for negative reviews is to avoid sharing a reviewer's private information and to invite them to continue by phone or email. For a roofer that applies twice over, because claim details are private and the dispute is rarely settled in a reply box.
What a claim or delay review changes about the reply
Three audiences read your reply. The reviewer, who wants to be heard. The next customer, who wants to know what happens when something goes wrong. And, in a claim dispute, anyone who might later read the page alongside a file. Only the first can be satisfied in public, and only partly. The reply's real job is to show the second audience a firm that stays calm and moves things forward.
That gives a simple split between what is safe to write and what never goes on a public page.
| Fine to say in public | Never say in public |
|---|---|
| Thanks, and an apology for the experience or the wait | Claim numbers, amounts, supplements or what the insurer paid |
| A general sentence about how delays arise: weather, deliveries, scheduling | Why a claim was reduced or refused, or what an adjuster said |
| That coverage decisions are made by the insurer, not by you | Whether an excess or deductible was discussed, waived or paid |
| A named person, a direct line and when they will call | Anything from your records: the customer's full name, address, phone or job details |
| That you will review what was agreed and what happened | Quotes from the contract or the estimate to prove them wrong |
| A plain offer to talk it through | Any claim that they are lying, late paying or acting in bad faith |
The right-hand column is longer than it looks, and it is where AI drafts go wrong, because a model told to "address the complaint" will try to. Everything in that column belongs in a phone call, a letter or a conversation with your own adviser. If a review raises something that sounds like a legal threat or a safety problem, stop drafting and take advice before you reply at all.
The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowThe five-part frame behind every reply
- Thank them. One short sentence, no "valued customer". Google's review tips suggest addressing the reviewer by name; use the name they posted under, never one from your own files.
- Apologise for the experience. Say you are sorry it felt like that. Do not say "sorry you feel that way", which reads as a dismissal, and do not admit fault for facts you have not checked.
- Add one neutral fact. A general line about delays or claims that reveals nothing about this customer.
- Move it offline. A named person, a direct line or email, and when they will call. Offer something specific you can do: review the file, call back today.
- Stop. No defence, no summary of why you were right, no sales line.
Here is the difference as a before and after (illustrative). The angry draft the owner types first: "This customer is being unfair. We sent the paperwork to their insurer on time, and the insurer only approved half of the supplement because the customer never sent the photos. We did our job." It reveals claim details, blames the customer and the insurer, and will be read by strangers as a firm that argues. The version that goes out: "Thank you for telling us. I'm sorry this has been such a stressful process. We can't discuss claim details in a public reply, and coverage decisions are the insurer's, but I'd like to go through what happened with you. Please call [name] on [direct line] and we will make time today." It is shorter, safer and answers the person reading, not the person who wrote the review.
A facts sheet and a prompt that cannot leak claim details
Most bad AI replies come from the AI being given too much. If you paste the claim file, it will use it. So give it two things only: the public review text, and a short facts sheet you wrote once, when you were calm. Keep the sheet in a ChatGPT Project or a Claude Project, and update it yourself.
FACTS SHEET (written by the owner, reviewed every quarter)
Reply is signed by: [name, role, company]
Direct line for reviews: [number], answered [hours]. Email: [address]
Commitments we can keep: a call back within one working day; a written update within 48 hours of that call
True and safe to say about delays: weather, deliveries and inspection dates can move a start date
What we may honestly admit (only where our records show it): we did not update the customer as often as we should
Never mention in public: claim numbers, amounts, supplements, excess or deductible, insurer or adjuster names, what any insurer said, the reviewer's full name or anything else from our records, their address or photosDraft a public reply to the Google review below for a roofing company. Use ONLY the facts sheet. 60 to 100 words.
Structure: thank them; apologise for how the experience felt (never "sorry you feel that way"); one neutral sentence about delays or claims in general; move offline with the named contact and one commitment from the facts sheet; sign off.
Rules: no claim, payment, excess or deductible details. Do not repeat any figure, date or address from the review. Do not say whether the reviewer was a customer. Do not argue, say who was at fault, or blame the insurer, the weather or the customer. No promises beyond the facts sheet. No offer of money, discounts or free work, and no mention of removing or changing the review. If the review mentions an injury, damage to someone else's property, a legal threat or a regulator, write "STOP: take advice before replying" instead of a reply.
Review text: [paste the review only]The last rule is the one that earns its place. A reviewer who writes "my solicitor will be in touch" or "someone could have been hurt" has changed the situation, and a public reply written in a hurry can become evidence. Let the AI flag those and stop.
Keep the AI's work to drafting. Google checks replies against its content policies before they show, and says a reply usually takes up to 10 minutes to appear, occasionally much longer. That gap is another reason to avoid auto-posting: you cannot unsay a reply that has gone live. Whether to let AI auto-post replies to Google reviews weighs the idea fairly; for claim and delay reviews my answer is no, and the general routine is in how to use AI to respond to Google reviews.
One firm, nine reviews and a Friday afternoon
Here is a worked example with illustrative numbers. Take a twelve-person roofing firm in the six weeks after a hailstorm. It completes about 70 jobs and receives nine reviews of two stars or fewer: five about insurance claims (an insurer paying less than the estimate, a denial the customer blames on the roofer, a supplement the customer says was never filed, a payment dispute) and four about delays (weather, materials, cancelled visits, late paperwork).
The owner sets aside one 40-minute block each Friday, plus a call slot between 8 and 9 each morning. The routine for each review runs as follows.
- Check the facts in your own records first (3 minutes). What does the schedule show? Do not use the review as your source of truth, and do not paste the records into the AI.
- Draft with the prompt (1 minute). Paste the review text, read the draft.
- Edit and approve (3 minutes). Cut anything the facts sheet does not support, then read it once out loud.
- Post by hand (1 minute). Under the owner's login, never from a tool.
- Call the next morning (10 minutes including notes). The call matters more than the reply.
That is 8 minutes of desk time per review and 10 for the call. Across nine reviews it is 72 minutes of drafting and checking and 90 minutes of calls, 162 in all. If writing each reply cold, while angry, takes 25 minutes (an assumption; time your own), the drafting alone would be 225. The saving is real, but it is the calm that matters more: the reply is the same five parts every time, so no reply is ever written in a temper.
Four replies to claim reviews
In each case the review is illustrative, the trap is what the owner is tempted to write, and the reply is the version to post once the placeholders are filled. Brackets are facts only you can supply.
Review 1: the insurer paid less than the estimate
The review: "Roofer's estimate was far higher than what the insurance paid. Nobody warned me. Felt let down." The trap is repeating the amounts, even though the reviewer posted them, and explaining the insurer's reasoning. Your reply never echoes a figure.
Thank you for writing this, and I'm sorry the process has left you feeling let down. We can't discuss any claim in a public reply, and decisions about what is covered are made by the insurer, not by us. I would like to go through what you were told and what has happened. Please call [name] on [direct line] or email [address] and we'll make time to talk it through.
[Name], [role], [company]
Offline, ask what they were told and when, and look at your own estimate and emails before the call. If an estimate was written to be sent to an insurer, say plainly that you can describe the work, not predict the payment.
Review 2: "You told me it would be covered"
The review: "Your salesman said my claim would be approved. It wasn't, and now I'm stuck. Avoid." The traps are "we never said that", which turns a customer into a liar in public, and any statement about what your salespeople are trained to say, unless it is true and you can show it.
Thank you for telling us, and I'm sorry you're dealing with this. I'd like to hear what you were told, directly from you. Coverage is decided by the insurer, so I can't comment on any claim here, but I can look into our conversations and talk about what we can still do. Please call me on [direct line] today or tomorrow. [Only if you will do it: if water is coming in now, call [emergency number] and we will send someone to make it safe.]
[Name], [role], [company]
Offline, listen first. Check your notes and any message that mentions coverage. If a salesperson did overstep, say sorry and describe what changes in how you talk about claims; you can say that publicly later in a general way, never about this customer.
Review 3: the supplement the customer says was never filed
The review: "They said they'd file a supplement for extra items and nothing happened. I had to chase everyone." A supplement is a request to the insurer for items the first estimate missed. The trap is to prove you filed it, with dates and reference numbers, in public.
Thank you for the review, and I'm sorry you felt you had to chase us. We don't go into job or claim details in public replies, but I'd like to check our records against what you remember. Please call [name] on [direct line] or email [address], and we'll come back to you within one working day with a plain account of where things stand.
[Name], [role], [company]
Offline, open the file before you ring. If it was filed, send the customer the dates in writing, privately. If it was not, say so and fix it that day; your honesty on the phone is worth more than any public defence.
Review 4: asked to pay before the insurer had
The review: "Roofer wanted payment before the insurance company paid out. Pushy, no flexibility." The traps are quoting the payment terms, mentioning the excess or deductible (the part of the claim the customer pays), and anything that sounds like a threat of collections.
Thank you for raising this, and I'm sorry the payment conversation felt pushy. That isn't how we want anyone to feel dealing with us, and I'd like to understand what was said to you. Payment and claims are private matters, so I won't go into them here, but I'd like to talk about your situation personally. Please call me on [direct line]; I'm available [hours].
[Name], [role], [company]
Offline, read the contract's payment clause and any message from your office first, since the review may describe a clerk's phone call and not your policy. Ask an adviser before you change how you handle the excess or deductible: how it may be treated depends on where you work and on your insurers' rules, and the reply should neither confirm nor deny any conversation about it.
Four replies to delay reviews
Delay reviews are easier than claim reviews, because you may say more in public: that weather, deliveries and inspection dates move start dates is general knowledge. What you may not do is argue about the dates in this particular job. And before you admit anything, check your own schedule.
Review 5: weather pushed the start back three weeks
The review: "Quoted two weeks, took five. The roof was half open through all that rain." The trap is the weather defence, "we can't control the rain", which is true and sounds like an excuse.
Thank you for the feedback. I'm sorry the job ran longer than we told you, and that your roof was open for longer than anyone would want. Weather decides when we can safely work, and we should have updated you more often than we did. I'd like to hear what happened on your job and make sure everything is right now. Please ring [name] on [direct line] or email [address].
[Name], [role], [company]
The admission "we should have updated you more often" belongs in the reply only if your records show it. Decide that once, in the facts sheet, and the AI will use it consistently.
Review 6: the materials were late and nobody called
The review: "Materials were delayed and nobody told me for two weeks. I only found out by ringing the office three times." The trap is to defend the supplier. Customers do not care whose fault the delay was; they care that they were not told.
Thank you for telling us. I'm sorry you had to ring several times to find out what was happening; you should have heard from us first. Delivery delays are a normal risk in this trade, but not keeping you informed is something we can fix. Please call [name] on [direct line] and I'll make sure you have a clear update that day.
[Name], [role], [company]
Offline, send the update you would have sent two weeks ago and tell them what will change. The rule worth adopting afterwards: a customer hears about any slip of more than two working days the day you learn of it, by the channel they prefer.
Review 7: the crew cancelled twice
The review: "Crew cancelled twice with no notice. Took time off work for nothing." Check the schedule before replying. If the crew did cancel twice, say sorry plainly, as below. If the record shows one cancellation and one date the customer moved, do not correct them in public: use the same reply but drop the first admission, and put the dates on the table in the call.
Thank you for the review, and I'm sorry for the wasted time, especially if you took time off work for it. Cancelling twice isn't the standard we aim for, and I'd like to find out what went wrong on your job and what we can do now. Please call [name] on [direct line] or email [address] and I'll make time today. If it's easier, tell us when suits you and we will ring you.
[Name], [role], [company]
Review 8: the job is finished and the paperwork is not
The review: "Roof done in October. Still waiting for the warranty paperwork and the final photos my insurer asked for. Can't get anyone on the phone." The trap is replying with the customer's address or job number to help find the file, which puts both on a public page.
Thank you for the review, and I'm sorry the paperwork has taken this long. Completion documents shouldn't be left waiting, and I want to get yours to you. Please email [address] with your job address (please don't post it here) or call [direct line], and I will check on it myself and come back to you by [day].
[Name], [role], [company]
Offline, produce the documents the same day if you can; storm-season paperwork piles up, and the photos for a customer's insurer are often the item that turns a quiet customer into a reviewer. The tutorial on roof damage reports for insurance claims shows how to produce those photo reports properly, so none of them is late.
All eight replies run between 60 and 100 words, and none contains an amount, a date from the review, a claim detail or an offer of money or free work. That is the test to run on every draft: if you can lift a sentence out and it gives a stranger one fact about this customer's job, cut it.
What the AI writes first, and what you cut
Even with the prompt above, first drafts drift in the same few directions. Here are the commonest, from a run on the Review 2 text (illustrative), with the fix for each.
| Line the AI produced | Why it goes | What replaces it |
|---|---|---|
| "We're sorry the insurer declined your claim." | Confirms the claim outcome publicly | "I'm sorry you're dealing with this." |
| "We never promise coverage, as our contract states." | Calls the customer a liar and quotes the contract | "Coverage is decided by the insurer." |
| "We take customer satisfaction extremely seriously." | Boilerplate the next reader skips | One concrete commitment: a call by [day] |
| "If you update your review, we'll waive the call-out fee." | An incentive to change a review, which Google prohibits | Nothing. Offers are never tied to the review |
| "We have already contacted you privately." | Claims a step you may not have taken | "Please call [name] on [direct line]." |
| "Your roof was completed on 12 October to the manufacturer's specification." | Argues the facts and discloses a job detail | Cut. Raise it on the call, if at all |
| A phone number that is not yours | The model invented one to fill a gap | Your real direct line from the facts sheet |
Then run a second pass. Paste the draft back with one instruction: "List every fact in this reply about the reviewer's job, claim, payment or dates. If there are none, say NONE." A clean draft returns NONE. If it returns a line, cut the line. The same check catches an accidentally helpful sentence such as "we know the extra decking was a surprise", which is a job detail in disguise.
Reply, report, or both: when the review is not genuine
Not every 1-star review is from a customer, and not every one that annoys you can be removed. Google's help pages are clear on the limits. You can report any review, but only those that break its policies are eligible for removal, and you are told not to report a review just because you disagree with it or dislike it. You flag a review from the Reviews section of your profile or through the Reviews Management Tool, and evaluation typically takes several days. The tool shows the status: decision pending, or reviewed with no policy violation found; a review that breaks the rules is removed. If you disagree with a no-violation decision, Google allows a one-time appeal from the same tool, and the result arrives by email. Google's pages also say it does not get involved in conflict between businesses and customers, so a claim dispute on its own is never grounds for removal.
That leaves a short decision rule, shown in the table.
| What the review is | What to do |
|---|---|
| A real customer, angry, with a fair point | Reply as above and call |
| A real customer, angry, partly wrong on the facts | Reply as above. Do not correct the facts publicly; do it on the call |
| Someone who was never a customer, or a competitor | Report it for the policy it breaks; reply only if it stays up |
| Spam, profanity or off-topic content | Report it; Google's tool offers reasons such as these |
| Someone demanding money to remove or change a review | Do not engage or pay; Google has a separate reporting route for extortion |
| A false statement of fact that harms you | Take legal advice; Google handles legal removals through a different channel |
Two traps sit beside that table. Never offer a customer anything on condition that they change or delete a review: Google's review policy treats incentives for posting, revising or removing reviews as prohibited, and the same page covers asking only happy customers for reviews. And do not assume a flag will work. If the review stays up after a report, the public reply is your remaining tool, and Google's own advice is that constructive replies and follow-up can show you care and sometimes lead the customer to update their review on their own. Its Manage customer reviews help page and the page on reporting reviews describe the current steps.
The call the next morning: the first ten minutes
The reply earns you the call. The call is where the review is actually resolved, or at least where the reviewer stops feeling ignored. A short structure keeps it from turning into an argument.
- Open with your name and the reason. "It's [name] from [company]. I read your review and wanted to hear it from you." Do not say you have already looked at the file unless you have.
- Listen for two minutes without correcting anything. Take notes of dates, who said what, and what they want to happen.
- Say back what you heard. "So the main problem is that you weren't told the materials were late, and you had to chase us." It shows you listened and it fixes the issue you will work on.
- Say what you will check and by when. "I'll look at the schedule and the messages and call you back by Thursday at 4."
- Offer only what you can do. Send the missing document, send someone to look at the roof, explain the next step in the claim. Never promise a payout, never promise the insurer's decision and never offer money on condition that the review changes.
- End with the follow-up in writing. A two-line email the same day: what you heard, what you will do, when. Keep the email private and factual.
Afterwards, you may add a short public follow-up under your reply, something like "We spoke with the reviewer and are looking into what went wrong." Add it only if the customer would not mind, and it is true. Never put the outcome of the claim, or anything the customer said on the call, on the page.
A reply log that keeps nine reviews from becoming ninety loose ends
A spreadsheet with one row per negative review is enough. Its job is to show, at a glance, what was promised, to whom and by when. This is what two filled-in rows might look like (illustrative; leave out names, addresses and claim details, and never paste the review text into a sheet other staff can open if it includes either).
| Seen | Stars | Topic | Reply posted | Call made | Promised | Due | Done |
|---|---|---|---|---|---|---|---|
| Fri | 1 | Claim paid less than estimate | Fri, owner | Mon | Send our estimate wording privately | Wed | Yes, Tue |
| Fri | 2 | Delay: materials, no updates | Fri, owner | Mon | Written update plus date | Tue | Yes, Mon |
Once a month, read the topic column. If four of nine reviews are about not hearing from you, the fix is a process, not nine replies. If three concern what salespeople said about claims, the fix is a script. The review log is the cheapest market research a roofing firm has, and nobody reads it unless somebody wrote it down.
Two messages that stop the next claim and delay reviews
Replies are the clean-up; these two messages are the prevention. AI is good at drafting both from your facts, and both are short enough to read.
The first goes into your estimate or contract cover note, written by you and checked by whoever advises you on contracts. An illustrative version:
About insurance. If your repair is part of an insurance claim, the insurer decides what is covered and how much it pays. We can provide photos of the damage and an estimate of the work. We can't promise the insurer's decision or when it will be made. If you are unsure about a document from your insurer, ask the insurer or an adviser of your own.
The second is a slip message, sent the day you learn of a delay. Weather, deliveries and inspections are the usual causes, and a customer who hears about each within a day rarely writes the review. For wording on rain days and rescheduling, the weather-delay messages and rescheduling checklist for roofers goes through them in detail. A short version:
Hi [first name], [company] here. [Cause, in a few words] has moved your start. The earliest safe date is now [date], and I'll confirm by [time] the day before. If you'd rather talk, call [name] on [number].
Neither message takes more than a few minutes to produce with the prompt style above, and both save more reviews than any reply ever will. A sister trade's version of the same reply discipline is in replying to a negative Google review as a vet, where the private information is health, not a claim. The principle is the same: acknowledge, apologise for the experience, say nothing private, go offline.
Questions roofers ask about review replies
Should I reply to every 1-star review?
Reply to every review from a real or possible customer, because the next customer reads the reply as much as the review. For a review that clearly breaks Google's content rules, report it first and reply only if it stays up after the decision. Keep each reply short and calm, whatever the review says.
How long should a reply be?
Roughly 60 to 100 words. A long reply reads as defensive, and it tempts you to explain details that belong in a private conversation. Aim for an apology, one neutral sentence, a named contact with a route to reach them, and a close. If you need more room than that, the issue should be handled by phone.
Can I let AI post the replies automatically?
It is safer not to. An automatic reply cannot tell when a review hides a claim dispute, a safety complaint or a legal threat, and Google also checks replies against its content policies before they appear. Let AI draft, let a named person read, and post by hand.
Further reads
- Roofing Change Orders for Rotten Decking: A Worked Example, AI-Drafted — Explain scope changes before they become a delay complaint.
- AI Receptionist for Roofing Companies: Storm-Day Calls and Claim Questions — Answer storm-day calls so fewer customers feel ignored.
- Roofing Storm Leads: Triage and Follow Up After Hail With AI — Triage and follow up after hail to cut waiting.
- Roofing Contract Template: Can AI Tighten the Wording? What a Lawyer Checks — What a lawyer checks in the contract behind the dispute.
- HVAC Google Business Profile: Service Areas, Q&A and Review Replies With AI — A sister trade's review-reply routine.
- How to Get More Google Reviews With Automated Review Requests — Collect more reviews so one bad one weighs less.
- AI SEO for Roofers: Hire an Agency or Do It Yourself? — Agency or DIY for a roofer's search and AI visibility: pitch claims to check, break-even sums, a weekly rota, a ChatGPT test sheet and contract clauses.
- Roofr's AI Receptionist: Is the Add-On Worth It for a Small Roofer? — What Roofr's AI Receptionist does, how its two pricing pages differ, a missed-storm-call payback sum and five test calls before you pay.
- AI Marketing for Roofing Companies: A Worked Storm-Season Content Plan — How a twelve-person roofing firm prepares storm content in advance: trigger levels, an approved pack, local pages, claims rules and financing wording.
- ChatGPT for Roofing: 10 Prompts for Estimates, Inspections and Warranty — Ten ChatGPT prompts for a roofing company's inspections, estimates and warranty replies, each with a filled example and a check before it is sent.
- Door-to-Door Roofing Sales: Scripts and Follow-Up Texts Written With AI — A 20-second doorstep script, honest objection replies and a three-text follow-up, with the permit and consent checks to make before anyone knocks.
- Roofing Social Media: Turn Finished Roofs Into a Month of Posts With AI — A consent step, a one-line job note and a four-week calendar that turn finished-roof photos into sixteen honest posts.
- How to Use AI for a Roofing Business: Where to Start, and What Waits — Five AI jobs for a roofing company ranked by effort and risk, the one to avoid, and a 30-day order of work.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Google Business Profile Help pages on managing customer reviews, reporting inappropriate reviews and tips for getting reviews, and Google's review content policy (read November 2026). Every review, reply and figure in the examples is illustrative.