Reviews are one of the signals a homeowner weighs in the moment they choose who to call. Asking for them is easy to intend and easy to skip. The crew leaves, the invoice goes out, and the request either never happens or happens weeks later when the customer barely remembers the job. Automation fixes the consistency problem, as long as it is built with a few rules in place.
When should the review request be sent?
As close as practical to the moment the work is finished, such as the final walkthrough or job completion. That is when the result is visible and the crew is fresh in memory, so the customer can describe something specific. Waiting longer tends to make the ask harder to answer well. Confirm the timing against your own response data.
The trigger should be an operational event, not a calendar guess. Job marked complete, final walkthrough logged, or final invoice paid are all reasonable triggers depending on how the business runs. What does not work is sending on a fixed day of the week, because that decouples the ask from the experience.
How many times should you ask?
Once, plus at most one reminder a few days later if there was no response. That is the point where additional requests start to cost more in goodwill than they return in reviews. If both go unanswered, stop. A customer who did not want to write a review is not going to change their mind on the fourth message, and pestering a happy customer is a good way to make them less happy.
What should the request actually say?
Short, personal, and specific. Come from the person the customer dealt with, reference the actual work, and include the direct link so no searching is required. Do not script the review, do not suggest a rating, and do not offer anything in exchange for it.
- Sent under the name of the estimator, foreman, or owner the customer interacted with.
- References the specific job, such as the room or the service performed.
- Includes one direct link to the review destination, not a menu of platforms.
- Makes clear the review is optional and takes a minute.
- Never offers a discount, gift, or incentive in exchange for a review.
Why is review gating a problem?
Review gating means surveying customers first and only sending the review link to the ones who answer positively. It is a common feature in reputation tools and it conflicts with Google's policies on soliciting reviews, which prohibit discouraging or preventing negative reviews. Beyond the policy question, it produces a review profile that does not reflect the business and tends to be obvious to anyone reading carefully.
The legitimate version is to send everyone the same request and to run a separate, genuinely useful feedback path for service recovery. If a customer is unhappy, you want to know quickly and fix it. That is a different message with a different purpose, and it should not be used as a filter on who gets asked for a public review.
How should negative reviews be handled?
Respond publicly, quickly, and without arguing the details. Acknowledge the experience, state what the business is doing about it, and move the specifics to a private channel. Prospective customers read responses as much as they read reviews, and a measured reply to a bad review often does more for trust than another five-star entry. What damages a profile is a pattern of defensive or absent responses.
What are the rules on automated text requests?
The same rules that apply to any business messaging. Consent needs to be captured and recorded, every message needs a working opt-out, stop requests must be honored immediately, and carrier registration for business messaging needs to be in place and verified with your provider rather than assumed. If review texts stop arriving, the diagnostic path is the same one described in business texts not sending and A2P 10DLC.
This is operational guidance rather than legal advice. Platform policies and messaging regulations change, so verify current requirements with the platform and your provider.
Where does review automation fit in the wider system?
It is the last step of the same loop that starts at capture. A completed job triggers the request, the review strengthens the local profile, and the local profile feeds the next inquiry. The profile side of that is covered in Google Business Profile optimization, and the automation lives in the CRM for contractors scope alongside estimate follow-up.
For trade-specific versions of the same loop, see the painting estimate follow-up sequence or the flooring measure booking workflow.