Review request to review rate
Shows whether the timing and message actually lead homeowners to leave a review.
In roofing, neighbors talk. A new roof is visible from the street, and after a storm the whole block is deciding who to call. Reviews on Google matter for the same reason: homeowners compare roofers quickly, and trust is the deciding factor when they cannot judge workmanship themselves.
Most roofing companies ask for reviews inconsistently, usually when a rep remembers. A review and referral process asks every customer at the right moment, typically after the final walkthrough and cleanup, and makes it easy to recommend you to the neighbor. Unhappy customers go to a person first, so problems get fixed before anyone asks for a public review.
When the job is marked complete and the walkthrough is done, the homeowner receives a short thank-you message with a quick satisfaction question.
Happy customers get a direct link to your Google review page. Anyone with a concern is routed to the production manager to resolve first.
A follow-up message a week later invites the homeowner to refer a neighbor, with a simple link that records who referred whom in the CRM.
Referred leads are tagged automatically, and the office gets a reminder to send the referral thank-you when a referred job is signed.
How we deliver this: AI automation for small business or fractional CTO leadership, scoped in writing and run over 90 days. See pricing or the sample scope.
Shows whether the timing and message actually lead homeowners to leave a review.
Referrals usually close more easily than paid leads, so tracking them shows the value of asking.
Counts concerns raised privately and resolved, which protects your rating and your warranty relationships.
For example, in an illustrative case a crew finishes an insurance replacement on a street where several homes were hit by the same storm. The day after the walkthrough, the homeowner gets a thank-you text and rates the job highly, then receives the Google review link. A week later a referral message lets her share your contact with two neighbors. Both leads arrive tagged with her name, and the office sends the thank-you when one signs.
We would review your current Google rating, the timing of recent reviews and how complaints have surfaced in the past year. Then we would agree a pilot: an automated thank-you and review request after the walkthrough, plus a simple referral link, measured over 60 days.
Usually after the final walkthrough and cleanup, once the homeowner has seen the finished roof and the yard is clear. On insurance jobs, some companies wait until the final payment is settled. We would look at when your customers are happiest and when complaints usually appear before setting the timing.
You can ask how the job went and offer to fix problems, but you should not stop anyone from leaving a public review. Google and the FTC both have rules about selective review requests and incentives. We would design the process so everyone can still review, and suggest you confirm the details with your own advisers.
Not always. Some roofing CRMs can send review requests directly, and tools like Podium or NiceJob add tracking and reminders. We would check what you have first. A dedicated tool makes sense if you want review monitoring across locations or text-based referral tracking.
Illustrative defaults for a roofing company. Replace them with your numbers.
a month in staff time, before any lost sales
Illustration only, not a forecast or guarantee. Recovered staff time becomes a cash saving only if spending actually declines or the time goes into paid work. Tool costs are an assumption; we replace every number here with yours before recommending a scope.
Review and referral requests: full guide
In 30 minutes we look at one recurring workflow, what it costs you today and whether there is a credible case to improve it. If there is not, we will say so.
30 minutes with Phil or Martin. No technical brief, no pitch deck. Phil or Martin replies personally, usually within one business day.