A review request people act on

The customer looks at the finished work, says it came out better than she pictured, and asks whether you take Zelle. That is the moment to ask for a review. A couple of minutes later you are loading the truck, she is back on a call, and the moment is gone.

Nothing went wrong and she is still happy. But happiness is not what produces a review. What produces a review is a short window where someone feels the result and has their phone in their hand.

Read the room before you say anything

Asking at the wrong time costs you more than staying quiet: you turn a job into an ask before the customer has actually had a chance to feel done with it.

The line that decides timing is completion, not enthusiasm. Ask every customer once the job is genuinely closed out — not only the ones who happen to say something nice first. "Looks great," "that was fast," "you cleaned up better than the last guy" are good openings to ask on the spot, but their absence is not a reason to skip someone. Sorting customers by how happy they sound before deciding who gets asked is exactly what Google's policy prohibits: merchants may not "discourage or prohibit negative reviews, or selectively solicit positive reviews from customers." Reviews collected that way get removed, and Google can put restrictions on your profile.

Hold off only while the job itself is still open — never because you are guessing at the score:

• Something you promised to come back for: a part on order, a touch-up, a snag on the list
• A billing conversation that is not settled, including a change order they were surprised by

Once both of those are closed, ask — including the customer whose job needed a callback or ran into a problem along the way. Predicting a lower review and quietly skipping that ask is the same selective solicitation as surveying people first; the fix is the same either way: everyone whose job is actually done gets asked.

The moment the result feels real

That moment is not the same in every trade, and for some work it is not on the day you finish.

The bottom two rows are the hard ones. Recurring service has no handoff, so you have to make the moment: attach the ask to a visit where you did something extra. A property manager has only your invoice and the lack of complaints to go on, so name the job for them.

Count the steps between your message and the review box

Every step between the ask and the typing loses people who meant to help you.

Text homeowners: you sorted out the arrival time in that thread, so the link lands somewhere they recognize. Email commercial and property-manager contacts, because that is where the invoice went and where they are allowed to answer you from.

Pull the short link out of your Google Business Profile once and save it as a keyboard shortcut on your phone. To write a review, the customer has to be signed in to a Google account. Most people have one through an Android phone or a Gmail address and never think about it, and an account can be made with any email address.

Three asks for three kinds of customer

Give a reason, make one request, and stop.

In person, right at the walkthrough:

Glad it came out right. Most of my work comes from people finding me on Google — would you mind leaving a review? I'll text you the link before I pull out.

The customer whose job hit a problem you fixed:

I know the countertop delay pushed us a week. If you thought the way we handled it was fair, that's the kind of thing worth saying in a review — I'd appreciate it either way.

The property manager, by email, a week after the invoice:

The unit on Bellevue closed out with no callbacks. If you have two minutes, a short Google review from you carries more weight than anything I can say about my own work. Link below.

What kills all three is hedging. "No pressure, totally fine if not, whenever you get a chance" tells the customer you expect a no and hands them the exit.

Never sweeten it either. Two separate rules sit on top of this. Google's policy bars offering payment, discounts or free goods for a review at all. The FTC's Consumer Reviews and Testimonials Rule (16 CFR Part 465, in force since October 2024) is narrower: it bars an incentive given in exchange for, or conditioned on, a review saying something particular — a gift card for a five-star lands inside it. A no-strings thank-you is murkier, and a reviewer would still have to disclose it. So keep the simple rule: offer nothing.

When a yes never turns into anything

Most people who say yes will not post. They meant it, and then the week happened. Send one reminder a few days later that names the job, so it reads like a person and not a broadcast, then let it go. A second reminder makes a good customer feel chased, and you would rather keep the customer than the review.

A yes that went quiet is still a warm customer, and two things are easier for them than a public review:

• A line you can use. Ask if you can put their text message on your website. They already wrote it, so you are asking permission, not work.
• A name. "Do you know anyone else on your street dealing with the same thing?" often lands with someone who felt bad about not posting.

Make it ten minutes on Friday

The ask usually fails on logistics, not nerve. By Thursday you cannot remember which jobs closed this week or which number goes with which address, so nobody gets asked.

Make it a standing slot. Friday afternoon, open the week's finished jobs and sort each into two piles in a few seconds: ask now, or still open on the two items above. Text everyone in the ask-now pile, using your saved link, and write the date next to the name. That stops you asking anyone twice, and after a month it tells you your rate. At one review per four asks, twenty asks a quarter is twenty reviews a year — and that number decides whether the slot is worth keeping.

If you write your estimates in DoneQuote, the customer stays attached to the job, so that Friday list already exists with phone numbers on it instead of buried in your text history.