A review-request habit that does not feel like spam

A good Google review is one a real customer chose to write after the work was done. That is the whole standard. You can ask for that in a way that feels like part of a normal job, or you can ask in a way that feels like a campaign. Customers can tell the difference. So can other shop owners, and so can Google, over time, if you cross into fake or paid reviews. We are not going to do that here.

This is a weekly habit, about half an hour, for a 1–20 person home-service shop. It assumes you do not have a marketing department. It also assumes you will not send a review request to everyone in your phone at 9 p.m. on a Sunday.

When to ask

Ask after the job is actually finished and the customer is satisfied, not when you are still standing in a mess, and not two months later when the job is a blur.

The best time is often in person, at the end of the visit, after you have walked them through what you did and they have said it looks right. You can say:

"If you're happy with the work, a Google review helps other people in town find us. I can text you the link, or I can show you on my phone. Only if you want to."

If they say not now, let it go. If they say yes, make it easy. Have the Google Business Profile review link ready as a short URL or a QR code in the truck, not as a scavenger hunt through search results.

A same-day or next-day follow-up is fine for jobs where you left before they could look (a part on order, a unit that needs to run overnight). Do not build a seven-message drip. One short ask is enough.

Who should ask

The person who did the work, or the person who walked the job with the customer, should ask. In a one-person shop, that is you. In a two- or three-person shop, do not invent a rule that "the office always sends the request." The office can send a follow-up if the tech forgot, but the first ask is stronger from the person who just fixed the problem.

Write the expectation in one line: techs ask in person when the customer is happy; the owner or office does a weekly sweep for jobs where nobody asked.

A weekly 30-minute routine

Block half an hour, once a week, the same time if you can. Tuesday morning after the first wave of calls is a common choice. The block is for Google Business Profile, not for redesigning the website.

1. Look at last week's completed jobs. Mark which ones already got an ask, which ones should still get a single follow-up, and which ones should not (a dispute, an unfinished callback, a customer who already said no).
2. Send only those follow-ups, and only through a channel the customer already used with you. If you text, only text people who opted in, and include a clear opt-out (they can reply STOP). That is practical caution, not legal advice. Do not paste a paragraph about messages being monitored for quality.
3. Reply to every new review, good or bad, in a calm voice. Thank them for the specifics when they left some. Do not argue in public. Do not offer a coupon in the reply as a bribe for an edit.
4. Check hours, service area, and the primary category on the profile. If something changed (seasonal hours, a closed holiday), fix it in this same block.
5. Add one real photo from a job you have permission to show, or skip photos this week. Do not fake a job site.

If you want a tighter weekly checklist for the rest of the profile (photos, Q&A, categories), that belongs in a Google Business Profile weekly habit. This page stays on the ask and the bad-review path. The profile and the website that collects jobs should tell the same story: who you are, what you do, and how to reach a person.

What to do with a bad review

You will get one eventually, even if you do good work. Read it twice before you type. If there is a fact you can check (the date, the tech, the invoice), check it. Then reply in public, briefly, and move the details offline.

A usable shape:

"I'm sorry this missed the mark. I'm the owner and I'd like to make it right. Please call the shop at [number] and ask for me, or reply here with a good time to talk, and I'll follow up."

Do not attack the customer. Do not tell the internet they are lying. Do not ignore a review that names a real safety issue. If the review is clearly about a different business, use Google's process for that, and say so simply.

A bad review is also a job for the log. What happened, what you offered, and what you changed in the SOP so it is less likely next time. That is more useful than a paragraph of defense.

What you will not do

• You will not buy reviews, trade discounts for five stars, or write reviews for people.
• You will not stand over a customer while they type.
• You will not email or text the whole list "in case they forgot."
• You will not tell an unhappy customer they can have a gift card if they take the review down. Solve the job, then let them decide.

Those lines are there because they are common, and because they blow up trust faster than a quiet week of no new reviews.

A small script kit

In person, job just finished: "If you're happy with this, a short Google review helps. I can show you the link. No pressure either way."

Follow-up text (only if they opted in): "Hi, this is Dana at Hilltop Cleaning. Just checking that Friday's visit looks right. If you're willing, here's our Google review link: [link]. Reply STOP if you don't want texts from us."

Follow-up email: same idea, one short paragraph, one link, no images of fireworks.

What we would do in a 1–20 person shop

We would print the in-person script on a card in the truck this week, and we would put a 30-minute block on the calendar for the weekly sweep. We would not turn on a review platform, buy a pack of reviews, or write a long policy. After a month we would look at two numbers we actually have: how many completed jobs got an ask, and how many reviews we replied to. If the ask rate is low, we would coach the in-person line, not add more messages.

If a bad review arrives, the owner answers it the same day if possible, and the next weekly block is when we change the SOP, not when we write a manifesto.

This article was drafted with AI assistance and reviewed by AuraGrid Labs editorial. Front of Shop is published by AuraGrid Labs LLC.