How to Respond to a Negative Google Review: 10 Contractor Examples

Use a four-part structure: acknowledge the concern, state only verified facts, offer a reasonable next step, and provide one contact route. Most public replies can stay between 50 and 100 words. That is a working guideline, not a Google requirement.

Match the apology to what you know. If dispatch records confirm a missed window, say so. If a customer alleges damage that you have not inspected, acknowledge the concern without declaring that your crew caused it. Empathy does not require guessing.

Think of the reply as the front door to resolution, not the whole service file. The reader should see that you listened and have a process for checking the problem.

Set an internal target to review new complaints within one business day. If the records are clear, respond then. If you need a technician's notes or an inspection, post a brief acknowledgment and move the investigation to a direct conversation. Do not promise a full resolution before you understand the issue.

For alleged gas leaks, exposed wiring, active flooding, or another immediate hazard, do not rely on the review thread. If you can identify the customer, attempt direct contact promptly. Tell them to avoid the hazard and contact the appropriate emergency service or utility when necessary.

Before replying, check the appointment window, dispatch notes, estimate, approved changes, job photos, and prior messages. Spend five minutes separating confirmed facts from claims. If you are angry, have someone else read the draft before posting.

These examples assume the facts described have been checked. Replace bracketed contact details with a monitored business number or email. Do not copy a sentence about an approval, fee disclosure, or missed appointment unless your records support it.

1. Late arrival with no update. Use when your crew missed the arrival window and dispatch did not notify the customer. “We missed your scheduled arrival window and did not keep you updated. We're sorry for the disruption. Please contact [service manager] at [business phone] so we can review what happened and confirm the next step on your job. We should have communicated the delay sooner.”

2. Price higher than expected. Use when you need to review the estimate and final bill rather than argue about your rates. “Thank you for raising the concern about your final bill. We want you to understand what each charge covers. Please contact [office] at [business phone] so we can compare the estimate, any approved changes, and the invoice with you. If something does not match the agreed scope, we'll address it.”

3. Disputed diagnostic fee. Use only when you have verified that the charge was disclosed. “We understand your concern about paying a diagnostic charge when a repair was not completed. Our records show that the visit fee was disclosed before booking, but we'd like to review the communication with you. Please contact [manager] at [business phone] so we can clarify what the visit included and address any billing error.”

4. Missed appointment. Use when the company failed to attend, not when you are still checking access records. “We did not attend your scheduled appointment, and we're sorry. Your time matters, and we fell short. If you still need service, please call [dispatcher] at [business phone] to discuss available options. We understand if you have already made other arrangements.”

5. No callback after an estimate request. Use when a lead went unanswered. “We're sorry your estimate request went unanswered. We should have told you whether we could take on the work and when you could expect a response. If you're still looking for help, please contact [office] at [business email] with your preferred callback time. We'll confirm availability before discussing an appointment.”

These complaints need more care because the cause, scope, or customer identity may be unclear. Offer a review or inspection when appropriate. Do not diagnose a roof leak, electrical fault, or equipment failure from a few lines in a public post.

6. Workmanship complaint or recurring problem. “We're concerned to hear that the problem has returned after our visit. We'd like to review the original work and discuss an inspection before making assumptions about the cause. Please contact [service manager] at [business phone]. We'll explain the available next steps and review any applicable warranty coverage with you.”

7. Alleged property damage. “We take your report of property damage seriously. Please contact [manager] at [business phone] so we can document the concern, review the job records, and arrange an appropriate assessment. Please share photos directly with our office rather than posting private property details here.” Follow your normal incident and insurance process separately.

8. Mess left at the job site. Use when the cleanup failure is confirmed. “We left debris behind, and that is not the condition we should have left your property in. We're sorry. Please contact [office] at [business phone] so we can arrange a suitable cleanup time with you. We'll also review the closeout checklist with the crew responsible.”

9. Unrecognized or suspected fake review. “We cannot match the information in this review to a job in our records. We'd like to investigate rather than make assumptions. Please contact [office] at [business email] with the service date and name used for the booking. Please do not post your address or invoice details publicly.” A different profile name does not prove a review is fake.

10. Warranty request outside the agreed scope. Use after checking the written warranty and job scope. “We understand your frustration about the requested repair. Based on our current records, it appears to fall outside the original scope and written warranty coverage. We'd be glad to review those documents and any additional information with you. Please contact [service manager] at [business phone] to discuss the assessment and available options.”

Move the details offline as soon as the discussion involves billing records, personal information, damage claims, inspection findings, or disputed promises. A useful public reply still acknowledges the actual complaint. “Call us” by itself gives future customers little reason to trust your process.

Give the customer one route and a responsible person or role. For example: “Please call our office and ask for the service manager.” Internally, assign that callback to someone. A polite reply followed by another unanswered call makes the complaint worse.

Avoid repeated public rebuttals. Post one useful response, then handle the investigation directly. If the matter is resolved, you can update your reply with a short factual note, but do not publish settlement terms or suggest the customer is satisfied unless they confirmed it.

If you believe a review violates Google's policies, report it through your Business Profile and retain relevant evidence. A negative opinion or an unrecognized name alone is not enough to establish a violation. Removal is not guaranteed, so keep any public reply measured.

AI is useful for removing defensive language and shortening a rough draft. It cannot verify what happened on a service call. Provide the complaint, confirmed facts, and the next step you can actually offer. Leave out customer names, addresses, payment details, and internal access information.

Review the draft sentence by sentence. Did it invent an apology for damage? Promise a refund? Say the owner investigated when nobody has? Delete anything unsupported. Then read it aloud. If it sounds like an argument or a corporate statement, simplify it.

For more reusable office workflows, the TradePrompt Master Vault ($49, 100+ prompts) is a natural next step. Keep the same rule across every prompt: your team supplies the facts and approves the action.