How to Respond to a Review Claiming You Damaged a Customer's Home

To respond to a property damage review, acknowledge the customer's concern specifically and without defensiveness, state only the facts your crew actually documented (photos, timestamps, notes from the visit), avoid disclosing the customer's address or personal details, and invite them to a private conversation — reserve a direct denial for cases where your documentation clearly contradicts the claim. A review claiming your crew damaged a customer's home is one of the highest-stakes situations in home services reputation management, both because it's genuinely upsetting to be accused of something you believe you didn't do, and because the instinct to argue it out point-by-point in public almost always makes the business look worse, not better, to everyone else reading. Being able to draft calm replies to contractor complaints from your phone matters here more than in almost any other review scenario, since this is the kind of complaint most likely to eventually escalate to the BBB or legal action if it's handled badly in public first. Template: when the damage was caused by your crew If your own records confirm the crew caused the damage, the review response should own it plainly and move to resolution fast — a defensive or hedging reply after your own documentation confirms fault reads as dishonest to anyone watching. A workable structure: Acknowledge specifically: "We've reviewed this with our crew and confirmed the damage you're describing happened during our visit." State what happens next without over-promising specifics in public: "We've reached out directly to make this right." Avoid restating the customer's address, the exact damage, or a dollar figure in the public reply — handle those specifics in the private conversation. Customers reading this exchange later tend to trust a contractor who owns a mistake quickly far more than one with a flawless record and no visible evidence of ever having to handle a problem. A calm, fast acknowledgment here often does more for your reputation than the incident itself does damage. Template: when the damage was not caused by your crew This is the harder, more common case — you believe the damage was pre-existing or unrelated to your visit, and you have some documentation (before-arrival photos, a crew note, a time-stamped checklist) to support that. The instinct is to post the evidence directly in the reply to "win" the dispute publicly. Don't. A calmer structure works better: Acknowledge the concern without conceding fault: "We take damage claims seriously and looked into this right away." State what you found factually, without accusing the customer of lying: "Our crew documented the site with photos before starting work, and we'd like to go through those with you directly." Invite a private conversation rather than litigating the facts in the thread: "Please call or message us directly so we can resolve this together." Here's a case worth planning for: a review claims a cleaning crew cracked a bathroom tile, but the crew's intake photos, timestamped before the visit began, show a hairline crack already present. Posting those photos directly in the reply as proof feels satisfying but tends to read as combative to a neutral reader scrolling past. The steadier version — a short public acknowledgment plus an invitation to review the photos together privately — protects both the business's credibility and the customer's privacy, and it leaves room for the customer to quietly realize they were mistaken without a public "I told you so" moment. Template: when fault is disputed Sometimes there's no clean documentation either way — no before photos, conflicting accounts, a genuine gray area about whether pre-existing wear or your crew's work caused the issue. In that case, the response should stay neutral and solution-focused rather than taking a firm position publicly that you can't fully back up: "We understand this is frustrating, and we want to get to the bottom of it with you directly rather than going back and forth here." Offer a concrete next step — a site visit, a call with the crew lead who was there, or a review of whatever documentation exists — rather than a vague "we'll look into it." If the dispute ultimately can't be resolved to both sides' satisfaction, a measured closing reply ("we offered a site visit and a call; we stand ready to continue that conversation directly") reads better to future customers than silence or an ongoing public argument. Template: when an insurance claim is involved Once a customer mentions filing a claim against your liability insurance, or asks you to, the public review reply should stay minimal and procedural — this is no longer a conversation to have in the review thread, and anything you say publicly can become relevant to the claim itself. A safe structure: acknowledge that you're aware of the situation, confirm you're working through it via the appropriate channel ("our insurance carrier is in contact with you directly"), and stop there. . Avoid admitting or denying fault in public once a claim is active, even if you were comfortable doing so before the claim was filed. When to flag a review to Google instead of replying Replying is the right move in the vast majority of property damage disputes, but a few situations call for flagging the review to the platform instead of responding publicly: the review is from someone who was never actually a customer, it contains a direct threat or harassment rather than a factual complaint, or it includes content that violates the platform's policies outright (fabricated claims, posted by a competitor, or doxxing-style personal information about your staff). Google, Yelp, Angi, and Thumbtack all have review flagging mechanisms for policy violations , though a flag based on simply disagreeing with a customer's account of what happened is unlikely to succeed and shouldn't be the default response to every property damage claim. A good rule of thumb: if the review is a genuine (even if factually wrong) customer complaint, reply using one of the templates above. If it's not from a real customer or clearly violates platform policy, flag it instead of engaging publicly. For general guidance on tone and structure across negative reviews, see our piece on how to respond to negative reviews, and if the dispute escalates to a formal complaint, our guide on BBB complaints covers what that process looks like and how it differs from an ordinary review. Should I ever offer a refund or discount in a public reply to resolve a damage claim? No — keep any offer of compensation out of the public reply entirely. Discussing a refund, discount, or settlement amount in public invites other customers to reference it in their own disputes, and it can complicate an active insurance claim if one is in play. Make any such offer directly to the customer, privately, after moving the conversation off the review platform. What if the customer posts a photo that seems to support their damage claim? Don't dispute photo evidence point-by-point in public, even if your own documentation tells a different story. Acknowledge the concern, state that you have your own documentation from the visit, and invite them to review it together directly — a side-by-side public argument over photos reads poorly to onlookers regardless of who's actually right. Every review from Google, Yelp, Angi, Thumbtack, Nextdoor and BBB in one inbox → Try Tailwind free. Tailwind runs $5 a month per tool, or $50 a month for the Full plan covering every tool, with the first month free and no card required to start.