How to Ask for Reviews Without It Feeling Awkward
BACK TO BLOGS
ReputationSeptember 27, 20266 min read

How to Ask for Reviews Without It Feeling Awkward

KEY TAKEAWAYS

  • Timing beats wording. The same request converts far better within two hours of the job than two days after it.
  • Asking in person and following with a link outperforms either on its own.
  • Never filter customers by how happy they seem before sending the link. Google removes reviews gathered that way.
  • Incentives of any kind violate Google's policy, including a prize draw.

This article is about the request itself: who to ask, when, and in what words. The mechanics of sending those requests automatically, and what reviews do to your map pack ranking, are covered in how to automate Google review requests. If one has already gone wrong, see what to do about a bad review.

The short answer

Ask in person as the job finishes, while the technician is still on site and the relief is fresh, then send the link by text within two hours. That combination converts far better than any wording change, because it catches the customer at the only moment they genuinely feel like doing you a favour.

Why the timing matters more than the words

Gratitude in home services has a short half-life. At the moment the heat comes back on, the homeowner is relieved and thinking about you. By the following afternoon the problem is solved, normal life has resumed, and your text is competing with everything else on their phone.

Contractors rewrite the message when the response rate disappoints. The message is rarely the problem. A plain request sent within two hours will beat a beautifully written one sent three days later, every time.

When sentTypical response
Asked on site, link within 2 hoursStrongest
Link same evening, no verbal askModerate
Link next dayWeaker
Link 3+ days laterMarginal
Emailed with the invoiceWeakest
Roughly how the same request performs depending on when it lands. Directional, from what we see in client accounts.

Who to ask

Not everyone, and not randomly. The customers most likely to write something useful are the ones whose problem you actually solved, who dealt with the same technician throughout, and whose job had a clear ending.

Emergency call-outs and completed installations are the best candidates. Ongoing maintenance contracts and jobs that ran over or needed a return visit are the worst, not because those customers are unhappy, but because there is no single moment that feels like a finish.

There is a line here that matters. Choosing to ask customers whose jobs went well is fine. Screening customers with a survey and only sending the review link to the happy ones is review gating, and it is prohibited. More on that below.

What the technician should actually say

Scripts fail when they sound like scripts. What works is short, specific, and framed as a favour rather than a transaction:

"If you were happy with how that went, a quick Google review genuinely helps us. I'll text you the link before I leave, it takes about a minute."

Three things are doing the work in that sentence. It names the platform, so the customer knows what is coming. It tells them the link is arriving, so the text is not a surprise. And it states how long it takes, which removes the main reason people mean to do it and never do.

The follow-up text

One message, from a number the customer recognizes, with the direct link and nothing else. No paragraph about how much you value feedback. Something close to: "Thanks again for having us out today. Here's that Google link if you have a minute: [link]".

One reminder after three days if nothing happens. Then stop. A second reminder converts almost nobody and irritates the people who deliberately ignored the first.

We set the whole request flow up so it fires from your job completion without anyone remembering.

BOOK A DEMO

The rules you cannot break

No gating

Sending a survey first and only passing the satisfied customers through to Google is against Google's policy. It is also detectable, since the review pattern looks unnatural, and the penalty is the removal of reviews you spent months collecting.

No incentives

No discount, no prize draw, no free filter, no entry into anything. This catches out contractors who think a raffle is different from a bribe. Google's policy does not distinguish between them.

No writing them yourself

Including drafting one for a customer who says they are happy to leave a review but does not know what to write. Suggest what to mention, never supply the text.

No bulk requests from one device or network

Handing a tablet to customers on site, or asking the whole office to review you, produces a pattern that gets flagged. Reviews should come from the customer's own phone, on their own connection.

What a good review actually contains

Star ratings help your average. Text helps you get found, because the words customers use become terms your profile can surface for.

A review saying "great service" is worth less than one saying the electrician replaced a panel in Delmar on a Saturday. The second contains a service, a place and an urgency signal, and that combination is what makes a review useful beyond the number.

You can influence this without dictating it. Prompting the technician to say "mention what we did if you get a chance" reliably produces longer, more specific reviews than a bare request.

A realistic target

Most trades businesses in a Capital Region market need somewhere between twenty-five and sixty reviews to stop being the obviously thin option, and a steady trickle thereafter matters more than the total. Twelve reviews spread across the last year beats forty that all arrived in one week two years ago.

If you are starting from one or two, one a week from jobs you are already completing gets you to a credible position within six months without any additional marketing spend.

Frequently Asked Questions (FAQ)

Q: Can I ask past customers from years ago? A: Yes, and it is worth doing once. Keep it honest about the gap, something acknowledging that it was a while back. Expect a low response rate, and spread the requests over weeks rather than sending them all on one day, because a sudden cluster looks unnatural.

Q: What if a customer says yes and then never does it? A: That is most of them, and it is why the link has to arrive while you are still standing there. One reminder three days later is reasonable. Beyond that you are spending goodwill for very little.

Q: Should I ask for reviews on Yelp and Facebook too? A: Concentrate on Google first, because it is what feeds the map pack and where nearly all homeowners look. Yelp explicitly discourages soliciting reviews and will filter ones that look requested, so asking there can be counterproductive.

Q: Is it acceptable to put a review link on the invoice? A: Acceptable, but weak. Invoices arrive at a moment associated with paying money, which is the wrong emotional context, and they are frequently opened days later. Use it as a backstop, not the main route.

Q: How many is enough? A: Enough to not look like the thinnest option in your map pack. Look at the three businesses currently ranking above you locally and treat their count as the bar. Recency then matters more than continuing to climb.

Book a call and we will build the ask into your job flow so it happens on every completed job.

BOOK A DEMO

HOW BRAIN KINDLE HELPS WITH THIS