Getting Reviews as a Roofing Company: The Final-Walkthrough Ask

The crew pulls away. The homeowner stands in the driveway looking at a brand-new roof — the biggest single home improvement they've ever bought, gleaming in the afternoon sun. Right now, in this exact minute, they feel something close to awe. By next Tuesday, it's just "the roof." The review window for roofing is the walkthrough itself — miss it, and you're asking someone to get excited about shingles from memory.

This is the roofing layer of the review engine — the full automated system is How to Get More Google Reviews as a Contractor (Without Begging) (Pillar C: 5-Star Review Engine). Roofing's twist: it's a high-ticket, low-frequency, high-emotion purchase with a built-in cinematic moment (the finished roof) — and a built-in complication (insurance jobs where satisfaction arrives months later, when the claim closes).

The story arc: why roofing reviews write themselves (if you capture them)

A roof replacement has a narrative most trades can't match: the ugly tear-off morning, the skeleton of decking at noon, the transformation by evening. Customers experience this as a story — and stories are what people want to tell in reviews. Your job is to hand them the pen at the climax:

• Document the arc for them. Tear-off photo in the morning, progress photo midday, finished photo at walkthrough — texted to the homeowner as it happens. By the final walkthrough, they've been narrating the job to their spouse all day. The review is already half-written in their head.
• The walkthrough is the ask moment. Not the next day, not "when you get a chance." At the walkthrough, standing under the finished roof, while the emotion is live.
• The drone-photo trigger. If you fly a drone (or even take a good ladder photo), the finished-roof aerial is the single best review trigger in roofing. Text it to the homeowner with the ask — people review the photo as much as the roof.

The final-walkthrough ask: script and choreography

The ask works best spoken first, then texted. The spoken version is casual — the project manager says it while handing over the warranty paperwork:

"We're all done — here's your warranty packet. Thanks for choosing us — I'm going to text you our Google review link. It takes about a minute and it genuinely helps a local company like ours. Would that be okay?"

The "would that be okay" is the hinge — a yes is a micro-commitment, and micro-commitments get followed through. Then the text fires within the hour:

Attaching the finished photo in the same text is the move. It gives them something to look at, something to show the neighbor, and a visual anchor for the review they're about to write.

The insurance-job complication (and the fix)

Retail roofs close the emotional loop at the walkthrough. Insurance jobs don't — the homeowner's satisfaction is tangled up in the claim: the adjuster, the supplement, the depreciation check. Asking at the walkthrough still works, but add a second trigger:

• Ask at the walkthrough anyway. The roof looks great; the emotion is real. Capture it.
• Add the claim-closed follow-up. When the final depreciation check arrives and the file closes — that's the second relief moment. A text then ("Glad the claim wrapped up clean — thanks for trusting us with it. Here's our Google review link: [link]") catches the customers who were too claim-stressed to review at the walkthrough.
• Track claim status in your CRM (customer relationship management — your customer database) so the follow-up fires on reality, not on a calendar guess. The trigger is "claim closed," not "45 days later."

The repair-job ask: small ticket, same system

Don't skip reviews on repairs — they stack up and they convert. The repair ask is simpler, sent same-day:

Repairs are also your review volume play: a roofing company doing 10 repairs a week has 10 weekly ask opportunities. Replacements get the glory; repairs build the count.

When the review doesn't come: the 48-hour nudge

The walkthrough ask captures the willing. The nudge captures the forgetful — and in roofing, "forgetful" is most of them. If no review appears within 48 hours of the walkthrough text, fire one follow-up. Just one:

The "reply here first" line is doing the same double duty as the replacement follow-up: it catches problems before they become reviews, and it makes happy customers feel cared for. After the nudge, stop — two asks is the limit. The customer who hasn't reviewed after two asks isn't going to, and a third ask trades goodwill for nothing. They'll still refer you; not everyone is a reviewer, and that's fine.

Compliance: the lines you don't cross

Two rules, non-negotiable. Never filter unhappy customers before the review ask — asking "were you happy?" and only sending the review link to the yeses is review gating, and it violates Google's policy. Everyone gets the same ask. Never pay for or incentivize reviews in ways that violate Google's policy — no discounts for 5-stars, no gift cards for reviews, no "review us and we'll waive the deductible" (which is its own legal problem in many states). The walkthrough ask above is the compliant way: ask everyone, ask at the peak, make it frictionless.

The numbers that justify it (attributed honestly)

Related guides in this series

The full engine is How to Get More Google Reviews as a Contractor (Without Begging) (Pillar C). For the job-photo communication system that feeds the walkthrough moment, see the roofing job-photo update guide in this series — and for the storm-season lead flow that precedes all of it, the roofer's storm-season setup.

The done-for-you version

This post is System 4 from the Leveraged Owner Starter Pack — the done-for-you version with the full review-engine setup guide, every ask script (including all trade-specific variants), the insurance-job follow-up triggers, the response templates, and screen-by-screen setup instructions for all 8 systems.

Stats sourced as labeled: BrightLocal 2026 (71% use Google to find local businesses, 68% won't use a business under 4 stars).

Keep building your systems

Related guides from the Leveraged Owner blog: