A builder review request is four lines: the milestone you just finished, an invitation to describe the experience honestly, one direct link to your Google Business Profile and a sign-off from a person the buyer knows. No suggested rating. No praise for the buyer to paste. No service tied to participation. It reads like a project message, not a campaign.
What belongs in every builder review request?
Start from the project record. Name the work that just finished, say who is asking and give the buyer one next step. The request should sound like your normal messages about plan review, selections, site progress and handoff.
The other reviews and reputation articles connect request language to timing, response and reuse rules.
- Milestone: State the completed phase in plain language.
- Honest invitation: Ask the buyer to share their own experience.
- Direct destination: Provide one approved profile link.
- No condition: Say explicitly that participation is optional.
- Human close: Sign from a role the buyer recognizes.
Before you use any wording, set the trigger described in when to ask a buyer for a review.
How should the script change by project milestone?
The structure stays the same. The subject matches what the buyer has lived through so far. Check the platform's current solicitation rules before you use these templates. Replace the bracketed fields with verified project information and cut any line that does not fit your process.
| Moment | Script | Internal check |
|---|---|---|
| Design phase complete | “We have completed your plan and selections handoff. If you would like to share how the design process worked for you, here is our review link: [link]. We appreciate an honest account in your own words.” | Approved plan and handoff are recorded |
| Owner orientation | “Thank you for walking the home with us today. If you would like to describe your experience from planning through orientation, you can leave an honest review here: [link].” | Orientation occurred and punch list is logged |
| Punch list closed | “Our records show the agreed completion list is closed. If you would like to share how the build and completion process went, this link goes directly to our review profile: [link].” | Responsible role confirmed closure |
| Warranty visit closed | “We have marked the recent service visit complete. If you want to share your experience with our warranty process, you may do so here: [link]. Your feedback is your own.” | Service record has a final status |
Do not send all four to one buyer. Pick a small number of moments that matter and record every request you have sent.
Which lines should a builder remove from its templates?
Delete any line that tries to write the outcome. “Give us a top rating,” “help our score” and “tell everyone we are the best” make the request about your metric instead of the buyer's experience. No gifts, no priority service, no drawing entries in exchange for sentiment.
Do not hand the buyer a block of praise to paste. If they want help remembering, use neutral prompts: Which phase was clearest? How did communication work? What would another buyer want to know before starting? The buyer picks the facts, the words and the rating.
Give everyone the same opportunity. Sending happy buyers to the public profile and unhappy buyers to a private survey is a filter. The review policy compliance article lists what to check with each platform before you approve a template.
How should email and text versions differ?
Email gets one sentence of milestone context and a labeled link. Text is shorter and comes from a business number the buyer already knows. Neither needs a paragraph on why reviews matter to you.
Email version
Subject: Your build experience
“We completed [milestone] for your project. Sharing a review is optional. If you would like to describe that experience in your own words, use [link]. Thank you.”
Text version
“We completed [milestone]. If you would like to share an honest review of your experience, here is the direct link: [link]. Thank you.”
Store approved templates with channel, owner and revision date. The Search presence stage ties them to the Google Business Profile and other profiles you control. Our agents draft variants from approved language and flag missing placeholders. People verify the milestone, the recipient and the destination before anything sends.
What should the follow-up script say?
Send one follow-up only if the program defines one. Silence is not a sales objection. The follow-up restates the optional request and the link: “A quick follow-up in case the review link was buried. If you would like to share your experience, it is here: [link]. No reply is needed.”
Record the follow-up so the buyer does not get another from the office, the superintendent and the warranty lead. Stop at the program limit or when the buyer declines. If the buyer replies with an unresolved concern, route it into the project or service process. Do not try to recover the review by text.
If a critical review appears, move to the fact-checking workflow in responding to negative builder reviews. The builder reviews program guide has the full operating structure.
Questions about review request scripts
Can we ask the buyer to mention a specific superintendent?
A builder review request should not direct praise toward a superintendent. Ask an open question about communication and let the buyer choose people or phases to mention.
Should the message include several review sites?
Use one approved review destination in each builder request. Check that the profile belongs to the builder and has a responsible monitoring owner.
Can we reuse the same script for warranty work?
A warranty review script should name the completed service event accurately. Keep participation optional and separate from coverage or future service handling.
Should the request come from the owner?
Send a builder review request from a role the buyer recognizes. Confirm the milestone, recipient, destination and prior request record before sending.