By hand
Only the friendly jobs.
Someone texts the customers who smiled. The hard jobs get silence. A month later the public page shows a handful of reviews, and the crew cannot say who was asked or who was skipped.
Review requests
Reviews, asked every time.
Review requests are one ask, sent after the work is done, to every customer. The ask does not sort people by how happy you think they are. It does not offer money, a discount, or a free visit in exchange for stars. A public reply sits in a queue until someone on your team lets it go.
Two ways
A favor you remember, or the same ask every time.
With the system
Every finished job.
When a job is marked done, the customer gets the ask you already approved, by text or email, with your Google review link. The same words go to the easy jobs and the ordinary ones.
Status
Built to order.
There is no switch for this. We build it around the way you close a job, for home services, dispensaries, and vet and dental desks. A named person owns the reply queue.
The rule
Ask for a real visit. Do not buy the star.
Google Maps user content policy tells businesses not to ask only the people they expect to be positive, and not to pay, discount, or give free goods for a review, a change to a review, or a removal. Google Business Profile review help says you may ask customers who had a genuine experience, including with your own link or a QR code, and that you should answer the reviews you get.
After the work.
The ask goes out when the job, the visit, or the order is complete. It does not go out to a list of strangers, and it does not go out before they have anything to describe.
No gate.
We do not send happy customers to Google and unhappy customers to a private form. Everyone who finished the work gets the same public ask. A complaint can still come to you in the same thread. It is not a filter.
No reward.
The message does not offer a coupon, a free service, or a gift for leaving a review or for changing one. If you want a thank-you that is unrelated, it is a different message, and you approve it on its own.
The yes
Public words wait in the queue.
The ask is approved once.
You sign the text or the email before it becomes the habit. After that, finished jobs can trigger it. Changing the ask means signing the new one.
Every public reply waits.
A draft answer to a review sits until a person posts it. That includes short thank-yous. The queue is the record of what almost went up, and of what did.
A claim stays with you.
The draft can thank them for the visit. It cannot invent a medical result, a product effect, or a promise about the next job. Those lines come from your team or they do not go out.
The record
What the month can show you.
Reviews in the month.
How many new reviews arrived, next to how many asks went out. The pair tells you whether people are being asked, which is the part you control.
Average rating.
The average on the profile, read from the profile, for the month you choose. It is a description of what is public. It is not a target we set for you.
Time in the queue.
How long a drafted reply sat before a person posted it or discarded it. That is a wait inside your office. It is not a promise about how fast we answer the public.
Where it sits
Text, email, and the Google profile.
The channels.
The ask goes by text or email. The link is your Google review link. We are not building a private star widget that hides the low scores.
After a visit or a job.
A reminder before the appointment is a different system. Appointment reminders tries to keep the chair full. This one speaks after the work exists.
While the tech is out.
A text that says where the crew is belongs to job status updates. Reviews start when that work is finished and the customer has something to describe.
Who it fits
Three desks, the same ask.
Trades, shops, clinics.
Home services, dispensaries, and vet and dental each follow their own rule for a public reply. A shop still cannot imply a medical result. A clinic does not invent a treatment claim.
You need a done state.
If the office cannot say when a job is finished, the ask has nothing to hang on. Fix that mark first. Then the message has a moment.
Someone must read replies.
A queue with no owner becomes a pile. Name the person before the first ask goes out. The plan is where that name gets written down.
Questions
Before you ask for a review.
Can we ask only the customers who seemed happy?
No. Google’s Maps user content policy says a business should not selectively ask for positive reviews. The ask in this system goes to customers who finished the work, not to a hand-picked friendly subset. If a job went badly, you can still call them yourself. You do not get a second, hidden path that keeps them off the public profile while everyone else is sent to it.
Can we offer a discount for a review?
No. The same Google policy bars payment, discounts, and free goods or services in exchange for a review, for a change to a review, or for taking one down. The message we send does not carry an offer. If your shop wants a promotion, it is a different text, approved on its own, and it does not mention stars.
Who posts the reply?
A person on your team. The system can draft a short thank-you from the language you approved. It does not publish that draft. Every public reply waits in the queue until someone posts it or throws it out. The log stores both the draft and the version that went up.
What do you count?
Reviews that arrived during the month, the average rating showing on the profile, and how long a drafted reply sat in the queue before a person acted. The queue time is an office measure. It does not describe how quickly the public hears back. Your own profile is the source of the rating.
Does this work for a clinic or a dispensary, or only for trades?
The shape is the same for home services, dispensaries, and vet and dental desks. The words are not. A clinic reply cannot invent a treatment result. A dispensary reply has to stay inside what that shop is allowed to say in public. We write the ask with you, and the person who posts replies is yours.
After the job
Tell us how reviews are asked for today.
A stack of business cards, a text from the owner, or nothing at all is a real starting point. We will say whether this ask is the first build.
Get your free Systems Plan