The 48-Hour Review Nudge: Wording That Gets the Click

You sent the review text after the job. Crickets. The instinct is to let it go — you don't want to nag a paying customer. But here's the thing: most non-responses aren't rejections. They're phones left in another room, kids screaming, life happening. A single well-timed nudge recovers a meaningful share of them.

This post sits inside our contractor Google-reviews guide — the pillar post for the review engine. The pillar covers the first ask; this post is the follow-up that makes the first ask pay twice.

Why 48 hours

The first ask goes out shortly after job completion, while satisfaction is fresh. The nudge goes out 48 hours later, and the timing is deliberate:

• Not 24 hours: too soon — it reads as nagging, and the customer who meant to do it "tonight" hasn't had their tonight yet.
• Not a week: too late — the emotional glow of the finished job has faded, and your text is now competing with a week of life.
• 48 hours: the sweet spot. Long enough to feel like a separate, gentle touch; short enough that they still remember the tech's name and the fixed AC.

One nudge only. A third ask crosses from persistent to pestering, and the review you extract from a annoyed customer isn't the review you want anyway.

The anatomy of a nudge that works

Four elements, in this order:

• 1. The soft opener. Acknowledge the first message without guilt-tripping: "Quick follow-up" or "In case you missed this." Never "You didn't leave us a review" — accusation kills goodwill.
• 2. The friction killer. Restate how easy it is: "30 seconds," "two taps." People overestimate the effort of leaving a review; your job is to shrink it in their mind.
• 3. The direct link. The full Google review URL, not "search us on Google." Every extra step loses people. The link should open the review box directly.
• 4. The graceful exit. "No worries if not" — paradoxically, giving permission not to do it increases the doing. Pressure creates avoidance; ease creates action.

The scripts

The standard nudge (most trades):

The personal version (when the tech had a real rapport):

The short version (for customers who hate long texts):

Automation: set it and forget it

This nudge should never depend on anyone remembering. The setup in your CRM (customer relationship management system — the database where you track leads and customers) or your field service management (field-service software) software's messaging:

• Trigger: 48 hours after the first review ask is sent.
• Condition: only fire if no review was left. If your review tool tracks this automatically, use it; if not, the office checks the Google profile each morning and suppresses the nudge for anyone who already reviewed. A nudge to someone who already left a review is the fastest way to annoy a happy customer.
• Stop rule: if the customer replies anything at all, the sequence ends. No further review texts, ever, for that job.

Compliance notes

Review texts are business texts, so the standard rules apply: 10DLC business-texting registration (A2P = application-to-person; 10DLC = the standard 10-digit business texting number) before sending — approval typically 1–7 days, ~$15–$20 one-time; opt-out language in the first text of any sequence; TCPA (federal telemarketing law) quiet hours (no texts before 8am or after 9pm recipient's local time). On the review side: never offer anything in exchange for the review — no discounts, no gift cards, no "leave a review for $10 off." That violates Google's policy. And never filter: the nudge goes to every customer, not just the ones you think are happy (review gating — steering unhappy customers away from the review ask — is prohibited by Google). General information, not legal advice.

What if they still don't respond?

After the nudge, the review pursuit for that job is over — no third text. But the customer isn't out of the review engine; they've just moved to the passive track. The QR code on the invoice, the email signature line, and the seasonal re-ask (one polite text per year to past customers who never reviewed) keep the door open without nagging. The discipline here matters: the shops with the best review counts aren't the ones that ask the most times per job — they're the ones that ask once or twice per job across the most jobs. Breadth beats repetition.

One more nuance: track why the nudge fails when it does. If a particular tech's jobs consistently produce no nudge responses, the problem is usually upstream — the in-person ask never happened, or the job itself left the customer lukewarm. The nudge can't fix an experience problem; it can only surface one. That's diagnostic value, not failure.

A worked example

Example: a plumbing shop sends the first review text 2 hours after each job, then the 48-hour nudge to non-responders. In a typical month of 60 jobs: 18 customers review from the first text, and the nudge goes to the other 42. Of those, 9 leave reviews after the nudge. The nudge — one automated text, zero staff time — produces a third of the shop's monthly reviews. The owner didn't get more persuasive; the system just asked the people the first ask missed.

Related guides in this series

The full ask-and-nudge framework lives in the contractor Google-reviews guide — the pillar post. For the surfaces that collect reviews with no ask at all, read the passive review system. And for what to do when a review comes back at 3 stars instead of 5, the recovery playbook is coming in this series.

The done-for-you version

This post is System 4 from the Leveraged Owner Starter Pack — the done-for-you version with the full 5-step setup guide, every script, the worksheets, and click-by-click setup instructions for all 8 systems. The Starter Pack includes all three nudge variants plus the suppression-check setup guide.

Stats sourced as labeled: no third-party statistics used in this post; the worked example is illustrative, not a customer result.

Keep building your systems

Related guides from the Leveraged Owner blog: