
Customer feedback automation sends a short request to every customer after each job, routes any complaint or low score to a named person who replies, and sends the public review link to every customer, not only the happy ones. The last part matters because Google's policy for Google Maps reviews says merchants may not "selectively solicit positive reviews from customers."
Automation sends and routes. A person reads and replies. This article covers the pieces and the controls, using Google's own policy and help pages. It is not legal advice.
The Four Pieces of the Loop
A feedback loop after a job has four parts: the request, the routing rule, the reply, and the review link.
The request is a short message sent after the job is finished. For a post-service feedback survey, our advice is to keep it to a question or two, so it is quick to finish. The routing rule decides where an answer goes. The reply is a person's response. The review link is the public step, and Google's help page says you can ask customers to visit a Google link or scan a QR code to leave a review.
Each piece can run without anyone remembering it, except the reply. That one needs a person.
Route Complaints to a Named Person
Routing customer complaints is the part of the loop that most needs a design decision. Our advice is to decide, in advance, what counts as a complaint or a low score, and send it to one named person, not to a shared inbox no one owns. The automation's job is to put the message in front of that person fast, with the customer and job attached. Setting the rule is a short task, and it protects the reply from getting lost.
This is the same idea as in our Friday article on keeping the banquet event order current: give one detail one home with one owner, and make everything else read from it. For feedback, the detail is the complaint.
If you use an AI tool to draft replies, a person reads the draft before it goes out. Our Monday article on how to check AI output lists what to check.
Ask Every Customer for the Review
Google's policy page for Google Maps user-generated content lists rating manipulation as something merchants may not do. Among the listed items, merchants may not:
- "Discourage or prohibit negative reviews, or selectively solicit positive reviews from customers" - "Offer incentives - such as payment, discounts, free goods and/or services - in exchange for posting any review or revision or removal of a negative review."
The policy also says that when soliciting reviews, merchants "should not require or pressure users to leave ratings or write reviews while on the premises, nor should they request that specific content be included."
Here is what we take from that for a build. Do not set up a rule that sends the review link only to customers who gave a high score and keeps it from everyone else. That is our reading of the selective-solicitation line, and you should read the policy yourself. Send the link to every customer who finished the job. The automation can do that by sending the same message to everyone. A rule like that is sometimes called review gating, and we recommend against it.
Do not attach a discount or a gift to the review, and do not ask for particular wording. Keep the message plain: here is the link, and thank you.
The policy applies to Google Maps reviews. We make no claim here about any law or any other platform.
Reply to Reviews
Google's Business Profile help page says to "Reply to reviews," which shows customers that their feedback matters, and calls replying a best practice. It also says: "Honest and balanced reviews can help potential customers decide. A mix of positive and negative feedback often feels more trustworthy."
That is Google's statement about reviews, and we are not making a claim about how reviews affect sales. We have no figure for how many customers leave one, and we do not offer one.
Replying is the second half of closing the customer feedback loop. A complaint routed to a named person gets a private reply and a note of what was done. A public review gets a public reply from a person. Automation can prompt the person to reply and track which ones are still open. It should not write and post the reply alone.
Where to Start
Choose one type of job. Write the one or two questions you will ask after it. Name the person who receives a complaint and the person who replies to reviews, and write down what counts as a complaint. Send the review link to everyone who finishes.
Our article on customer service auto-replies covers automated responses to questions customers send you, and our guide to CRll-business) covers where the contact record and its history live.
To plan a feedback loop for one type of job, get your free AI assessment.
Frequently Asked Questions
Can I send the review link only to customers who were happy?
Google's policy for Google Maps reviews says merchants may not selectively solicit positive reviews from customers. We recommend sending the link to every customer. This is not legal advice.
Can I offer a discount for leaving a review?
Google's policy lists offering incentives, such as payment, discounts, or free goods or services, in exchange for posting a review as something merchants may not do.
What should a post-service feedback survey ask?
Our advice is one or two short questions about how the job went, plus a place for a comment. Keep it short.
Who should reply to a complaint?
A named person. The automation routes the message to that person, and the person reads and replies.

