Your team agrees to ask for reviews, but each technician chooses a different moment and wording. Some customers receive three requests. Others receive none because they raised a complaint.
Set a consistent customer moment, one owner, and a neutral request. The process should invite honest feedback without selecting customers by how positive you expect their response to be.
Apply the same request timing regardless of satisfaction; handle service complaints through the support process without withholding the review invitation.
Choose the moment and the responsible person
For a hypothetical home-service company, the request follows the completed appointment and the ordinary service follow-up. The office coordinator sends it through an approved customer communication channel. The technician can tell the customer a request will follow, but does not send a second one.
| Workflow field | Completed example |
|---|---|
| Trigger | Service completion recorded and normal follow-up handled. |
| Eligible recipients | Customers with a genuine completed service experience and an appropriate communication route, regardless of expected rating. |
| Sender | Office coordinator using the company process. |
| Message | Neutral request with the correct Google review link. |
| Follow-up | At most one planned reminder under the company's communication rules; stop on an opt-out or customer request. |
| Duplicate prevention | Mark the request against the completed job; check the record before sending again. |
| Exceptions | Handle privacy, incorrect contact, and communication restrictions through the coordinator; do not filter on satisfaction. |
Pick a cadence appropriate to your customer relationship. This example is a workflow recommendation, not a platform requirement that every company should send a reminder.
Use copy that leaves the customer's judgment alone
Request example: “Thank you for choosing us for your recent service. If you would like to share your experience, you can leave an honest Google review here: [review link]. Your feedback helps other customers understand the service.”
Do not ask for five stars, supply a flattering review for the customer to paste, or attach a discount to completion. Google allows requests for reviews but prohibits incentives for posting or changing them. Its Maps content policies also prohibit selectively soliciting positive reviews or discouraging negative ones.
If you use a private satisfaction survey, keep it independent of access to the public review request. Sending happy customers to Google and unhappy customers to a private form creates the wrong selection rule. The review workflow should not sort customers into public and private paths based on their score.
Give staff instructions for difficult cases
A customer with an unresolved issue needs service attention. Route the issue to the person who can address it. Do not condition help on removing a review, and do not offer compensation in exchange for a changed rating.
If the contact information is wrong or the customer opts out, stop the communication according to your process. That exception concerns contact or permission, not the expected review sentiment. Record enough context to prevent another staff member restarting the request by mistake.
For public responses, assign someone who can acknowledge the concern and move private details into an appropriate support conversation. Do not publish job records or personal information to defend the company. A useful response can state the next contact route without arguing over every detail in public.
Check whether the process runs as designed
Review a small set of completed jobs: did the coordinator send the intended request once, did the link point to the right profile, and did opt-outs stop the follow-up? Review the replies separately for service improvements. Avoid treating a target review count as permission to pressure customers.
Check the link and the handoff
Open the actual review link on a phone before handing it to staff. Confirm the business name and destination; a copied link for another location can send customers to the wrong profile. Give the coordinator a simple way to replace a broken link in the approved message without starting a separate request campaign. Keep the service issue route visible alongside the feedback process so customers can reach someone who can help. That support route must remain available whether a customer writes a review or chooses not to.
Our Business Profile audit checks the profile and inquiry path. This workflow handles the ongoing request process. Explore our SEO services for help keeping local search activity accurate and useful.

