How do you get more Google reviews for a service business?
Short answer
Ask every satisfied customer immediately after the job is finished, by text, with a direct link to your Google review form. Timing matters more than wording: the request should arrive while the technician is still on site or within the hour, and it should be automatic rather than remembered.
Key takeaways
- Reviews are a timing problem. The same request converts far better within an hour of completion than a week later.
- Text outperforms email because the link opens on the device already signed in to Google.
- Make the ask automatic on job completion, or it will happen only when someone remembers.
- Respond to every review, especially the critical ones. Future customers read the response as closely as the complaint.
Why do most review requests fail?
Not because customers are unwilling. Most people are happy to leave a review for work they were pleased with. Requests fail for mundane reasons: they arrive too late, they take too many taps, or they never get sent because asking felt awkward in the moment.
- Timing: satisfaction peaks when the job is finished and the mess is cleared. A week later that feeling has faded into normality.
- Friction: "search for us on Google and leave a review" is several steps. A direct link is one.
- Channel: an emailed request competes with a full inbox. A text is read within minutes.
- Consistency: relying on technicians to remember produces a trickle, not a stream.
When exactly should you ask?
As close to completion as you can manage. The strongest moment is while your technician is still on site and the customer has just seen the finished work. The next best is within the hour, triggered automatically when the job is marked complete.
There is one exception worth building in: if a job had a complication, a complaint, or a callback, do not fire the request automatically. Route it to a person first. Asking for a public review from someone with an unresolved problem is how you generate the review you least want.
What should the request say?
Keep it short, name the person who did the work, and include the direct link. Specificity is what makes it feel like a request rather than a broadcast.
Example: "Hi Sarah, thanks for having us out today. If Dave did a good job, a quick Google review would genuinely help a small local business: [link]. Either way, shout if anything is not right."
- Name the technician. It makes the request personal and gives the reviewer something concrete to write about.
- Say why it matters. "Helps a small local business" is honest and effective.
- Include the escape hatch. Inviting problems to come to you directly diverts some negative reviews into fixable conversations.
- Never offer anything in exchange. Incentivised reviews breach Google's policies and can cost you the whole profile.
How do you handle a negative review?
- 1
Respond, and reasonably quickly
An unanswered complaint reads as accurate. A calm reply reframes it as one perspective on a business that pays attention.
- 2
Write for the next customer, not the reviewer
Your audience is the person deciding whether to call you. They are assessing your temperament as much as the complaint.
- 3
Acknowledge, clarify briefly, move it offline
One short paragraph. Acknowledge the experience, correct any factual error without arguing, and offer a direct contact to resolve it.
- 4
Never argue in public
A defensive reply converts one bad review into evidence of a pattern, and it is permanent.
A steady flow of new reviews is also the best protection against any single bad one. A profile with a handful of reviews is defined by its worst; a profile with hundreds absorbs an outlier without much damage.
How do you make it a system?
- Trigger the request on job completion, not on someone remembering.
- Suppress it automatically for jobs flagged with a complaint or callback.
- Send one polite reminder after a few days if there is no response, then stop.
- Track requests sent against reviews received, so you can tell whether the problem is asking or converting.
- Route every new review to someone whose job it is to respond.
That last point is where most reputation efforts quietly stop. Collecting reviews is a workflow; responding to them is a habit, and it needs an owner just as much as the sales pipeline does.
Frequently asked questions
No. Incentivising reviews violates Google's policies and can result in reviews being removed or the profile being penalised. It also produces reviews that read as purchased, which undermines the credibility you are trying to build.
Ask every satisfied customer. Build in an exception for jobs with an open complaint, a callback, or a dispute, and route those to a person instead. Blanket automation with no suppression rule is how you invite public criticism.
Google first, because it carries the most weight for local search and appears directly in Maps results. Add industry-specific platforms where your customers actually look, but do not split a single request across several sites, since choice reduces completion.
Report it to Google with whatever evidence you have, and respond publicly in the meantime, factually and without heat. Removal is not guaranteed, so a measured reply matters: it is what prospective customers will see if the review stays up.