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
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.
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:
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.
Techs won't memorize a paragraph. Give them one sentence:
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.
Dissecting the 40 words:
One ask captures the eager third. The 3-day follow-up captures the "meant to do it" majority:
"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."
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 happens — some people hate writing reviews, some are private, some are just having a day. The graceful exit:
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.
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.
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.
Stats sourced as labeled: no third-party stats in this post — timing guidance is built from customer-satisfaction practice.
Related guides from the Leveraged Owner blog:
Review velocity for contractors: how many Google reviews per month move the needle, why freshness beats total count, and what enough looks like by market size.
NiceJob vs. Broadly vs. Podium for contractors: honest pricing, what each review platform does well, and the free DIY alternative for shops on a budget.
Reply YES to confirm texts cut contractor no-shows. The exact wording, timing, reschedule-link trick, and full confirmation cadence — a micro-system deep dive.