> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aresdeploy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to Get More Google Reviews for a Service Business

> A practical, compliant method for getting more Google reviews for a home or field service business, plus what Google's review policy actually prohibits.

<Note>
  Key Takeaway: More Google reviews come from asking every customer, right after the job, through the channel they already use. Consistency beats cleverness, and gating or buying reviews violates Google's policy.
</Note>

Getting more Google reviews is mostly a systems problem, not a marketing problem. Businesses that ask 100% of customers, right after service, in a channel people actually read, out-review businesses that only ask their happiest few by hand.

A Google review is defined as a star rating and optional written comment a customer attaches to your Google Business Profile, visible directly in Google Search and Google Maps results. Review velocity means the pace at which new reviews arrive, and for local search purposes it matters almost as much as your overall star average, since a profile that hasn't added a review in four months reads as inactive to both customers and Google's ranking systems.

## Why do Google reviews matter so much for service businesses?

Reviews are one of the few things a stranger can see before they've spoken to you, and for home and field service businesses they often substitute for the referral a customer would otherwise need from a neighbor. BrightLocal's consumer research consistently finds that most people read online reviews before choosing a local business, and Google itself reports that a significant share of all searches carry local intent, meaning someone typing "plumber near me" is already deciding partly on what shows up next to your name.

Reviews also compound. A profile with 40 recent reviews and a 4.8 average beats a profile with 6 reviews and a 5.0 average in most buyers' minds, because volume signals that the rating is real rather than lucky. That's the part most service businesses get backwards: they wait for a "good enough" job to ask, instead of asking on every job and letting the average take care of itself. The goal isn't a fixed number either. A steady weekly cadence, tied to your job volume, beats a one-time push followed by two months of silence.

## What's the single biggest lever for getting more reviews?

Timing, not wording. Ask within a few hours of the job finishing, while the work is fresh and the customer is still glad it's done, not three weeks later in a generic monthly newsletter. The second lever is coverage: ask every customer, not just the ones who said "great job" on their way out. Most negative experiences never turn into negative reviews if nobody's watching for a pattern, but most positive experiences also never turn into reviews unless someone asks.

## What's the best way to ask, by channel?

| Channel                                       | When it goes out                        | Typical response                                         | Effort required                 | Best for                                      |
| --------------------------------------------- | --------------------------------------- | -------------------------------------------------------- | ------------------------------- | --------------------------------------------- |
| Text (SMS) link                               | Same day, within hours                  | Often highest of any channel, since texts get opened     | Low once set up                 | Most home and field service businesses        |
| Email request                                 | Same or next business day               | Usually lower opens than text                            | Low                             | Customers who've opted into email over SMS    |
| QR code or printed card                       | At the moment of service                | Inconsistent, depends on the customer remembering        | Medium, needs printed materials | In-home visits with no phone number collected |
| Automated review-request software (like Ares) | Triggered when a job is marked complete | Consistent, since every customer gets asked the same way | Very low after setup            | Businesses that keep meaning to ask and don't |

Text wins for most service businesses because it matches how people already talk to their plumber, electrician, or HVAC tech. Email still works for customers who've said they prefer it, and a printed card beats nothing for a business with no digital lead capture.

## What you must never do: gating and buying reviews

Two shortcuts show up constantly in service-business marketing advice, and both are against Google's policy, not just risky.

Review gating means asking a filtering question first, like "Were you happy with our service?", then routing only happy customers to a public Google review while diverting unhappy ones to a private form. It looks efficient. It's also a direct violation of Google's review policies, because it manipulates which opinions the public sees, and Google has suspended and removed reviews from profiles caught doing it.

Buying reviews, whether from a marketplace or an incentive tied to leaving five stars, is the other line you don't cross. Paid or incentivized reviews violate Google's terms and are detectable at scale, and the downside far outweighs the short-term bump. Asking everyone, compliantly, already outperforms gating over time, because it produces a realistic distribution of ratings that looks earned, which is exactly what it is.

## How do you respond to reviews, especially negative ones?

Respond to all of them, not just the five-star ones. A prompt, specific reply to a negative review often matters more to future customers than the review itself, because it shows how you handle a problem when one shows up. Keep responses short, acknowledge the specific issue, and move the resolution offline rather than litigating details in public.

## A simple weekly review-request routine

* Pull the list of jobs completed since your last check, not just the ones that "felt good."
* Send the review request the same day, by text if you have a mobile number on file.
* Respond to every new review within 48 hours, negative ones first.
* Once a month, scan for a pattern in any repeated complaint (late arrival, pricing confusion, callback delays) and fix the underlying process, not just the review.

## A hypothetical example: a residential plumbing company

This is an illustrative walkthrough, not a claimed Ares client outcome. Say a single-location plumbing company completes about 15 jobs a week and has 22 total Google reviews after three years, added in occasional bursts whenever the owner remembered to ask. If that owner started texting a review link to every customer within hours of job completion, even a modest response rate would roughly double the total review count within a couple of months, arriving every week instead of in rare clusters. Nothing about the service changed. Asking became systematic instead of occasional.

## How Ares fits into this

Ares manages Google Business Profile and automates review requests as part of its broader job as an AI operator for home and field service businesses. When a job is marked complete in the CRM, Ares sends the review request automatically by SMS or email, tracks who's been asked, and flags negative feedback to the owner for a fast, direct response instead of silence. It never gates who gets asked and never pays for or incentivizes reviews; every customer gets the same request. This runs alongside Ares's core work of answering and booking leads, covered in the guide on [follow-up and nurture sequences](/leads/follow-up). Pricing is \$299 a month standard, or \$100 per seat for enterprise, detailed on the [billing page](/account/billing).

Review automation won't fix a business with a real service problem, and it's not a substitute for resolving the complaints that show up in negative reviews. For a broader look at which parts of local marketing are worth automating versus which still need a person's judgment, see [Should I Fire My Marketing Agency and Use AI Instead?](/guides/should-i-fire-my-agency-use-ai)

## Frequently asked questions

<AccordionGroup>
  <Accordion title="How many Google reviews does a service business need?">
    There's no fixed number, but a steady weekly cadence matters more than a one-time total. A profile adding two or three reviews a week looks more credible to both customers and Google than one that got 30 reviews in a single push two years ago and none since.
  </Accordion>

  <Accordion title="Is it against the rules to ask happy customers for reviews?">
    No. Asking customers for reviews is fine and expected. What's against Google's policy is filtering who you ask, known as review gating, where you route only satisfied customers to the public review page while diverting unhappy ones elsewhere.
  </Accordion>

  <Accordion title="Can I offer a discount for leaving a Google review?">
    No. Incentivizing or paying for reviews, including discounts tied to leaving a review, violates Google's review policies and can result in reviews being removed or a Business Profile being suspended.
  </Accordion>

  <Accordion title="What's the best time to ask a customer for a review?">
    As close to job completion as possible, ideally the same day. Response rates drop the longer you wait, and a request sent weeks later often gets ignored entirely.
  </Accordion>

  <Accordion title="Should I respond to negative Google reviews?">
    Yes, and quickly. A short, specific, non-defensive response to a negative review often reassures future customers more than another five-star review does, because it shows how the business handles problems.
  </Accordion>

  <Accordion title="Does review automation replace the need to fix service problems?">
    No. Automating requests and responses gets you more honest feedback faster, but a pattern of negative reviews still means something in the actual service needs to change, not just the messaging around it.
  </Accordion>
</AccordionGroup>
