Most service businesses agree that reviews matter. Most also have a review count that has not moved in months. The work gets done, the customer is happy, and the ask never goes out, because asking is nobody's job.
That is the pattern worth fixing. A review request is a small, repeatable step that sits right after the job closes, which makes it one of the easiest workflows to automate well. It is also easy to automate badly. Here is how it works when it is done with care.
Why the ask slips
The moment to ask is right after the work is finished. That is also the moment the team is moving on to the next job, sending the invoice, and clearing the calendar. Asking for a review feels optional, so it waits. A week later it feels awkward to bring up, so it never happens.
Nobody decided not to ask. The step simply has no trigger and no owner. Automation gives it both.
Step one: trigger it from the finished job
The request should start from a real event, not a calendar reminder. The cleanest trigger is the status that already means done in your system: a job marked complete, an invoice paid, or a project closed out. That ties the ask to work that actually happened, and it plugs into the same path as automated job closeout.
If your tools do not have a reliable done status, that is the first fix. A review request built on a guess will eventually ask someone whose job is not finished.
Step two: pick one timing rule
Timing matters more than wording. Too soon, and the customer has not seen the result yet. Too late, and the moment has passed. Pick one rule that fits the work, such as a day after a service visit or a few days after a project handoff, and keep it consistent. You can adjust it later once you see what gets responses.
Step three: ask once, with one link
The message should be short, personal, and easy to act on. Use the customer's name, mention the job, and give one direct link to your Google Business Profile review form. No survey first, no list of five platforms to choose from. Every extra click loses people.
Send one gentle reminder at most, then stop. A review request that keeps nagging does more damage than one that is never sent.
Step four: send unhappy replies to a person
Some customers will reply instead of reviewing, and some of those replies will be complaints. That is useful. Any reply goes straight to a named person on the team, not into an automated loop. A quick human response to a problem is worth more than any review, and it is the same principle as giving every workflow a defined stop where the machine hands back to a person.
What to leave out
Do not filter who gets asked based on a satisfaction score first. Google's review policies discourage selectively asking only happy customers, and it erodes trust. Ask everyone whose job is done. Do not offer discounts or rewards for reviews either, for the same reason.
Do not write or post replies to reviews automatically. A thank you to a five star review can be drafted for someone to approve, but the response should come from a person, especially when the review is critical.
Where to start
Look at the jobs you finished last month and count how many customers were asked for a review. If the answer is few or none, you already know the workflow is worth building. Write down your done status, your timing rule, and who handles replies. That short page is most of the spec.
Happy customers rarely leave reviews on their own. They leave them when someone asks at the right moment, every time.