Review Automation for Roofers: After Final Inspection, Not After the Storm Call

Review automation for roofers is a Google review SMS that goes out after final inspection, not after the storm call. The homeowner has walked the roof or the attic with you, the punch list is done or clearly scheduled, and the invoice matches the job that actually finished. You do not ask for five stars on the day the tarp goes on. You do not offer a deductible “help” for a review. This page is the trigger. The wider asking habits are on our Google reviews for roofers guide.

Storm-day asks feel desperate. They also review a promise, not a finished roof. Wait until inspection is signed and the yard is as clean as you said it would be. Then send one text with a direct link.

This is the text after inspection, not a storm-season reviews pitch

The automation starts when the job status says final inspection passed, not when the adjuster is still scheduling.

Roofing shops lose reviews in the gap between “we got the contract” and “the dumpster is gone.” The sales visit is emotional. The homeowner is scared, wet, or staring at a quote. A review that day is about fear and a handshake. Six weeks later, if nobody texts after the walkthrough, the profile still shows last year’s work. Competitors who ask after inspection, every time, look busier than shops that did the same number of roofs.

This article does not replace the roofing reviews guide linked above. That one covers what to say when someone writes about a leak or a crew. This one is the machine: which status change sends the link, what the text says, and what you refuse to attach to it. Build the link with a direct Google review link so they do not land on a search page of storm chasers.

Use final inspection as the trigger, not the contract and not the tarp

Send the request only after the finished roof has been inspected with the homeowner, or after a repair is closed and holding.

A full replacement has too many dates. Contract signed. Materials ordered. Tear-off. Dry-in. Shingles. Gutters. Magnet sweep. Final walk. The review belongs to the last of those, when the homeowner has seen the completed roof and you have either cleared the punch list or written the date you will return for a missing piece. If a small item is still open, say so in the text only if you must, or wait until that item is done. Do not ask them to review a roof you have not walked with them.

Repairs and leak calls can close the same day, if the leak is stopped and you have shown them what you did. A tarp is not a finished repair. A tarp is weather protection. The review text waits until the permanent work is in and inspected. Asking under a blue tarp reads as pressure, and the review, if it comes, will be about the storm, not the workmanship.

Insurance jobs need the same finished-work rule, with extra care on the wording. Do not text “glad we handled your claim” or “we saved you the deductible.” You are a roofing company. The review is about the roof, the crew, the cleanup, and whether you did what you said. Leave the carrier, the scope fight, and the supplement out of the SMS. If the job is stuck in a supplement and the roof is not finished, do not send the request.

Do not fire on “contract signed” or “deposit received.” Those events measure sales, not a roof. A stack of five-star notes written at signing, before a shingle is touched, is exactly the pattern that makes a profile look bought. Time the text for the afternoon of inspection, or the next morning if the walk ended at dusk. One reminder two days later if they did not tap the link. Then stop. Roofing customers are also getting texts from the adjuster, the supplement desk, and the neighbor’s canvasser. Be the short one.

Write a walkthrough text, not a storm-chaser blast

The SMS thanks them for the inspection, names the company, and gives one Google link. It does not mention stars or insurance money.

Hi Elena, this is Ridgeline Roofing. We finished the final inspection on your roof today. If you have a minute, you can share how the job went on Google: [review link]. Reply STOP to opt out.

Repair version, only after the leak is closed:

Hi Marcus, Ridgeline Roofing here. The repair is complete and we walked the area with you. You can leave a note on Google here: [review link]. Reply STOP to opt out.

Do not write “if you are happy with your new roof, please leave 5 stars.” Do not write “your neighbors are watching.” Do not attach before-and-after photos that show the house number. Do not name the claim number. The homeowner can describe the crew and the cleanup in their own words. You do not script the rating.

Email is the reminder, two days later, same link, no urgency line like “last chance before the next storm.” Subject: “Final inspection with Ridgeline Roofing.” Keep extra wording with our SMS request templates, then freeze the roofing versions so a sales rep does not add a referral bounty.

Every inspected job gets the link, not only the smooth replacements

Completed inspections get the same Google link. You do not quiz them on stars and hide the public page from anyone who is frustrated.

Roofing tools often sell a “protect your rating” fork: happy homeowners go to Google, frustrated ones go to a private form. That is review gating. It is selective solicitation. It also fails the thing you actually need, which is a profile that matches the roofs you built, leaks included when they happened. If a crew left nails in the driveway, you want to know, and the homeowner still gets the same link as the neighbor who loved the color.

Handle the problem in the field. Nail sweep, flashing, a missed vent. Do not offer a gift card, a waived change order, or help with a deductible in exchange for a review. That is an incentive, and Google treats incentives for reviews as misleading. If the homeowner says stop texting, stop. If the job is in a live dispute and inspection has not passed, the trigger has not fired. That is a status check, not a personality check on the sales call.

Commercial and HOA work: send the request to the person who signed the completion, not every unit owner. Put that mobile number on the job so the sequence does not text a board member who never saw the roof.

DIY: inspection status, one link, one reminder, then stop

You can run this from the job board you already use, if “final inspection passed” is a real status and not a sticky note.

Create the review link for the profile that matches the city on the contract. Test it on a phone that is not the owner account. Multi-state storm crews need one link per real location, not one national page.

The trigger is inspection passed, job complete, or certificate of completion issued. Not lead created, not contract signed, not “canvasser knocked.” If JobNimbus, AccuLynx, or your sheet cannot text, export jobs that hit that status each afternoon and send from the company number. One job, one sequence. Do not re-text because a supplement changed the invoice after the roof was already reviewed.

Quiet hours still apply. A walkthrough that ends at 8 p.m. can wait until 9 a.m. Include STOP. Honor it the same day. Skip jobs waiting on material, jobs with an open leak ticket, and any number that belongs to the adjuster instead of the homeowner.

Log status date, send time, and opt-out. If inspections are closing and no texts leave, the status name in the software does not match the trigger. The shape matches other local review automation. The roofing detail is waiting for inspection, which is also the right time to ask for a Google review.

Get the free playbook if you want the request rules written down before a storm week. Check your Reputation Score if you want to see whether finished roofs are showing up as reviews at all.

What roofing companies break in storm season

The common failures are asking at the door, asking at signing, and answering insurance complaints with a sales story.

Door-knock review cards. A card in the mail slot on the first visit is not automation, and it is the wrong day. The homeowner has not lived with the roof. They will lose the card.

Canvasser scripts that say “our reviews speak for themselves, please add yours tonight.” The roof is not on yet. Stop coaching that line.

Photos of the house in a public review request. The SMS does not need a picture of their street. If you post a finished job later, get permission and crop identifiers. That is a posts problem, not a review-request problem.

A rating filter dressed up as “quality control.” Turn it off. The crew should still fix nails and flashing. The link stays the same.

A second company number for “the review guy.” Customers already have your production text thread. Use that number so the message is not a stranger.

Reply to insurance-complaint reviews with facts, not a claim narrative

Answer the public review with what the crew did and how to reach you. Do not recount the insurance file.

A review that says the crew was on time and the yard was clean can be thanked in two lines. Name the job type if they did: replacement or repair. Do not add “we work all insurance carriers” as a footer on every reply.

A review that says you delayed, changed the price, or left a leak gets a calm factual reply. “The final inspection was on Thursday. We returned for the valley flashing on Monday. If something is still open, call the office at this number and we will look at the job file.” Do not name the carrier, the claim number, the deductible, or what the adjuster “should have” paid. Those details are not for the neighborhood to read, and they are easy to get wrong in a hurry. If you have not opened the file, do not invent a date.

Do not ask them to take the review down in exchange for a repair you already owed them. Do the repair. Reply with the facts. Let them edit the review if they choose. You do not control that.

A Houston garage-door company we worked with changed follow-up, not the field work. Reviews went from 38 to 59 in 45 days, with a 15.9 percent request-to-review rate. The rating moved from 4.6 to 4.7. Replies moved to under 24 hours. Their words: “We didn’t change the service. We changed the follow-up.” That is a garage-door client, not a roofing number. Do not promise your count will move the same way. You can still steal the habit: inspect, text once, reply the same day.

What ReviewNix runs after you set it up once

ReviewNix sends the request when the roofing job is actually finished. You still write or approve anything that goes public as a reply.

Manual work is a production manager texting from a truck after dark, skipping the jobs that already took too long. Automated requests use the completed-inspection trigger, SMS first, email as the reminder, WhatsApp if that is how the homeowner already talks to production. The Google Business Profile is connected so the link and the new reviews are not in two logins. One reminder, then stop. STOP is honored. The dashboard shows which inspections produced a request, so storm week does not erase the habit.

AI can draft a reply. You edit it and you post it. Drafts must not invent a flashing detail, a warranty year, or a claim fact. One-star reviews and anything that names a job stay in front of a person. ReviewNix does not auto-post fake replies and does not attach an incentive to the ask.

Set it up once. Let ReviewNix handle the follow-up.

Start on the trial form: https://reviewnix.com/formpage

Frequently asked questions

Can we text the night we sign the contract, while they are grateful?

No. That review is about the sales visit. Wait until final inspection. A signature is not a finished roof.

What if a small punch-list item is still open?

Wait, or finish it first. Do not ask them to review a job you have already told them is incomplete. When the item is closed, send one sequence.

How should we reply if they blame us for the insurance company?

Facts about your work and a phone number. Do not narrate the claim, name the deductible, or argue the scope in public. Offer to look at the job file offline.

Should we only text homeowners who smiled at the walkthrough?

No. That is a rating filter. Every inspected, completed job with a reachable customer who has not opted out gets the same Google link. Fix the roof issue in the field. Do not hide the link.