How to Ask for Google Reviews: Timing, Wording, and the Text That Works

The ask is 90% timing and 10% wording. Trade-specific satisfaction peaks, the exact text that converts, and the in-person line your techs can actually remember.

System 4 from the Leveraged Owner Starter Pack

By Leveraged Owner · The 5-Star Review Engine

The tech just got the heat back on. It's 68 degrees in the house for the first time in two days. The homeowner is standing there in a t-shirt, smiling, saying "you're a lifesaver." That moment — right there — is worth more than any review software ever built. Everything in this post is about catching it.

The automation that fires the ask is covered in How to Automate Google Review Requests After Every Job, and the strategy overview is the pillar guide, How to Get More Google Reviews as a Contractor. This post is the human half: when to ask, what to say, and how to say it so it doesn't feel like begging.

Timing: the satisfaction-peak map by trade

A review request is perishable. Ask at the peak and it's a favor between friends; ask three days later and it's homework. The peak is different for every trade:

HVAC: the moment comfort is restored — heat back on, cold air blowing. The relief is physical and immediate. Peak lasts hours, not days.
Plumbing: when the problem is visibly solved — leak stopped, water heater hot, drain flowing. Have the tech run the faucet and show them it works; the demo is the peak.
Roofing: the final walkthrough. Walk the property together, point out the details, hand them the warranty paperwork. Standing in the yard looking at a finished roof is the highest-satisfaction moment in the trade.
Electrical: after the tech explains what was done — panel labeled, everything tested, the "here's what was wrong and what I fixed" walkthrough. Understanding creates confidence, and confidence creates reviews.

The automation fires 30–60 minutes after the tech leaves — close enough to the peak to ride it. But the in-person ask, when the tech plants the seed before leaving, multiplies the text's conversion. The two work together: the tech mentions it, the text delivers the link.

The in-person line (one sentence your techs can remember)

Techs won't memorize a paragraph. Give them one sentence:

"Glad we got it fixed — I'm going to send you a quick text with a link, and if you could leave us a Google review it'd really help me out."

Why this works: "help me out" — it's personal, not corporate. The customer met the tech, not the brand. And "quick text with a link" sets up the automation so the text doesn't arrive as a surprise.

The text: the exact wording

Hi [First Name], this is [Tech Name] from [Business Name] — glad we got the [service] sorted today. Would you mind leaving us a quick Google review? It really helps our small business: [Review Link]. Reply STOP to opt out.

Dissecting the 40 words:

"this is [Tech Name]" — from the person they met, not "the team."
"glad we got the [service] sorted" — references their specific job, proves it's not a blast.
"quick Google review" — "quick" sets the effort expectation at 60 seconds.
"helps our small business" — the real motivator. People don't review to help corporations; they review to help the nice tech and the local shop.
The direct link — straight to the review form. Not your website. Not a Google search. The form.

The follow-up (where the second half of reviews come from)

One ask captures the eager third. The 3-day follow-up captures the "meant to do it" majority:

Hi [First Name], [Tech Name] from [Business Name] again — just a friendly nudge on that Google review if you have 60 seconds: [Review Link]. No worries either way! Reply STOP to opt out.

"No worries either way" is the load-bearing phrase — it removes guilt, and guilt is what makes people delete instead of tap. Never send more than two automated touches; the third ask is where "persistent" becomes "annoying."

Trade-specific timing nuances

HVAC replacements (big ticket): wait until the first full day of comfort — the morning after the install, when they wake up to a quiet, comfortable house. The automation delay can stretch to next-morning for installs.
Plumbing emergencies: ask same-day. Emergency customers feel the strongest gratitude (you saved their night) but it fades fastest. Strike while the relief is hot.
Roofing: the walkthrough is the ask moment — but send the text the next morning, when they're looking at the roof in daylight and feeling good about the decision.
Electrical: same-day is fine, but the explain-it walkthrough has to happen first. A customer who doesn't understand what was fixed won't review it.

What never to do

Never offer payment or discounts for reviews in ways that violate Google's policy. "Leave us a 5-star review for $20 off" gets reviews removed and risks your profile.
Never filter unhappy customers before the ask (review gating). Asking "how did we do?" first and only sending the Google link to happy responders violates Google's policy. Same ask, same link, everyone.
Never ask at the wrong moment. Mid-job, at invoicing (when they're thinking about money), or days later — all worse than the peak.

Training your techs to ask (the human half)

The automation sends the text. The tech makes it land. But most techs would rather wrestle a condenser than ask for a review — it feels like begging. Reframe it in training:

It's not begging, it's informing. Most happy customers have no idea reviews matter to you — and many want to help but don't know how. The ask is a favor you're offering them the chance to do.
One sentence, not a speech. "Glad we got it fixed — I'm going to send you a quick text with a link, and if you could leave us a Google review it'd really help me out." Memorize it, say it, move on. The shorter the ask, the less awkward it feels.
Role-play it once. In the next team meeting, have each tech say the line out loud. The first time is awkward; the tenth time is automatic. Awkwardness is a training problem, not a personality problem.
Show them the scoreboard. When reviews mention a tech by name, share it with the whole team. Techs who see their name in 5-star reviews start asking without being told.

When they say no (or look uncomfortable)

It happens — some people hate writing reviews, some are private, some are just having a day. The graceful exit:

"No worries at all — just glad we could get it taken care of!"

Smile, move on, let the automated text do its quiet work later (many "no"s in person still tap the link when it arrives — saying no to a face is harder than ignoring a text, and the text has no face). Never push, never guilt, never ask twice in person. One graceful ask beats three awkward ones, and the tech who handles "no" well is the tech customers request by name.

Compliance notes

No paying for reviews. Never offer discounts or incentives for reviews — it violates Google's policy.
No review gating. The same ask goes to every customer, not just the happy ones.
Texting rules: 10DLC business-texting registration on your business number (the carriers' registration system for business texting; 1–7 day approval, ~$15–$20 one-time), opt-out language in the first automated text, and TCPA (federal telemarketing law) quiet hours (no marketing texts before 8am or after 9pm recipient local time). This is general information, not legal advice.

Related guides in this series

The strategy: the review-engine pillar guide. The automation: How to Automate Google Review Requests After Every Job. Five more ask templates: Google Review Request Text Templates: 5 Messages That Get Reviews. Browse the full blog for everything published.

The done-for-you version

This post is System 4 from the Leveraged Owner Starter Pack — the done-for-you version with the full review-engine setup guide (standard operating procedure), the trade timing maps, every ask script, the tech training one-pager, and click-by-click setup instructions for all 8 systems.

See the $27 Starter Pack

Stats sourced as labeled: no third-party stats in this post — timing guidance is built from customer-satisfaction practice.