A roofing review request text should identify your company, ask for an honest review, and include a direct link to leave it. Keep the request separate from any repair discussion, and don't ask for a particular rating. The templates below give your team copy-paste wording and a workflow for handling replies without turning a simple request into a nagging campaign.
Start with a message the homeowner can recognize
Use this default template after your team's normal project closeout. Replace every bracketed field before sending.
Hi [First name], this is [Sender name] with [Roofing company]. Thanks for choosing us for your roof [replacement/repair]. Would you leave an honest Google review of your experience? Here's the link: [Review link]. Reply STOP to opt out.
The sender should be someone the homeowner knows, or someone clearly identified as part of your company. A text from an unfamiliar number with nothing but a link can look suspicious.
Use the review link available through your Google Business Profile rather than making the homeowner search for your company. Google explains how to obtain and share that link. Test it on a phone before adding it to your template.
Keep the wording neutral. Google's fake engagement policy prohibits offering incentives for reviews and selectively soliciting positive reviews. Don't use “If you loved your roof, review us; otherwise, contact the office.” Give customers the same opportunity to describe their experience, including criticism.
Give someone ownership before the request goes out
A saved template doesn't solve a missing handoff. Decide who confirms the project record is ready, who sends the request, and who handles replies.
For an owner-operator, that may all be the owner. Keep the task in the customer record so it doesn't depend on remembering a conversation later.
For a company with office staff and separate production crews, the production lead can record the closeout status. The office manager can then check the contact details and send the request from the company's designated texting number. The person who sends it also needs a clear route for assigning service concerns.
Before sending, check:
- The customer's name, mobile number, and project type are correct.
- The company has appropriate permission to send this type of text, and the customer hasn't opted out. Don't assume a number collected for scheduling authorizes every future message.
- Another employee or system hasn't already sent the request.
- Replies will reach an inbox someone on your team owns.
If you use automated requests, configure suppression rules for opt-outs and duplicate sends. Verify how your texting provider handles STOP and other opt-out requests. Adding an opt-out sentence doesn't replace consent requirements.
Use a consistent closeout milestone across customers rather than deciding who gets asked based on expected sentiment. For the timing decision, use this guide to when to ask for a roofing review after a job.
Match the script to the conversation
The default message works when there hasn't been a recent review discussion. These alternatives fit different situations without asking the homeowner to write a sales pitch.
When the homeowner already agreed to receive the link
Hi [First name], it's [Sender name] from [Roofing company]. Here's the Google review link you asked for: [Review link]. Thanks for sharing your honest experience. Reply STOP to opt out.
Only use “you asked for” if that happened. A template shouldn't invent a conversation.
When the homeowner says they don't know what to write
You can describe your experience in your own words. If it helps, mention how communication went or anything you think another homeowner should know. Here's the link again: [Review link].
Don't supply a finished review for the homeowner to paste. Avoid coaching them to mention particular keywords, employees, or positive claims. Their experience should determine the content.
When an unanswered request needs a reminder
Hi [First name], [Sender name] with [Roofing company] following up on our review invitation. If you'd like to share your experience, here's the link: [Review link]. If you've already left a review, thank you. No need to reply. Reply STOP to opt out.
Use this only after checking the conversation and opt-out status. A reminder can help someone find the link again, but repeated nudges can become an annoyance. Set a firm endpoint instead of leaving the request in an open-ended sequence.
Don't send this reminder when the homeowner has already replied with a question. Answer the person before sending more scheduled messages.
Route replies before sending anything else
The next action should depend on what the homeowner says. A delivered text doesn't mean the request has been handled.
| Homeowner reply | Team action | What happens to reminders |
| --- | --- | --- |
| Says the link doesn't work | Test the link and send the corrected destination | Pause while fixing the issue |
| Says they already reviewed | Thank them and mark the request complete | Stop |
| Declines or opts out | Record the preference and honor it | Stop |
| Reports a roof or cleanup concern | Assign it to the person responsible for service and acknowledge the concern | Stop the review sequence and handle the conversation |
| Asks about another roofing project | Create a separate inquiry and assign it to the sales owner | Pause while the team responds |
Here's a service-reply template your team can adapt:
Thanks for letting us know, [First name]. I've passed your concern about [issue] to [Responsible person]. They'll contact you to discuss the next step.
Send that only after making the handoff. Don't promise a callback time your team hasn't agreed to meet.
Stopping reminders during an active service conversation isn't a reason to deny someone the opportunity to review. Never make repairs or other assistance conditional on leaving, changing, or removing a review. If the homeowner has already posted criticism publicly, use this guide to responding to negative roofing reviews alongside the private service conversation.
Find the broken step before rewriting the text
Keep a simple record of request status, delivery problems, replies, and the next assigned action. If you can't reliably match a public review to a customer, don't assume that person ignored the request.
Use the evidence in the record to decide what needs attention:
| What you find | What it may mean | What to check next |
| --- | --- | --- |
| Closed projects have no request recorded | The production-to-office handoff is missing | Confirm who creates and completes the task |
| Messages fail to deliver | The number or texting setup needs attention | Verify the contact record and provider error details |
| Homeowners ask who is texting | The sender isn't recognizable | Add the employee name, company, and accurate project context |
| Homeowners report trouble opening the link | The destination may be wrong | Test the exact saved link on a phone |
| Requests deliver but receive no visible response | Customers may be busy, uninterested, or unable to complete the review | Check the link and message clarity, then respect the endpoint |
| Questions arrive but sit unanswered | Sending is working; reply ownership isn't | Assign an inbox owner and a backup |
That last failure can also lose a new roofing inquiry. A homeowner might reply asking about another property or additional work. Move that conversation into your normal lead tracking process rather than leaving it buried in a review thread.
Track that inquiry separately through your team's sales process to a signed roofing job. A review, a reply, and a booked estimate are different events. None proves that a project was won.
Save the default script, test its link, and assign the reply owner before enabling reminders. For related guidance on managing customer feedback, visit the roofing reviews and reputation hub.