Ask for the review the day the job is done
5 min read
By Lumina Software
- Operations
- Service business
- Customer communication
- Follow up
- Automation
Most service businesses ask for reviews at the wrong time, or never. The best time to ask is the same day the job is marked done, while the customer still remembers the tech's name.
That one change is easy to set up, and it does more than any review tool's fancy features.
Why the ask never goes out
Here is how it usually goes. The owner says "we should get more reviews." Someone tells the techs to ask in person. A few do it for a week. Then a busy Monday hits and nobody asks again.
Or the shop buys a tool that sends review requests. It runs off a list that someone has to upload. The upload happens twice, then stops. Nobody notices for months, because nothing breaks out loud. The reviews just stop coming in.
I think the problem is almost never the wording of the ask. It is that the ask depends on a person remembering, on a day when they have ten other things to remember.
So tie it to something that already happens every time. In most shops, that is the moment a job, visit, or appointment gets marked complete.
Send it when the job closes
Pick the one status change your team already does for every job. For a plumber, it might be the tech closing the work order on the phone. For a clinic or med spa, it might be the visit being checked out at the front desk. For a realty team, it might be the file moving to closed.
Hook the review text to that change. When the status flips, a text goes out a little while later. Not instantly, because a text that arrives while the tech is still in the driveway feels like a script. A couple of hours later, or that evening, feels like a person.
Keep the text short:
"Hi Sam, thanks for having Marco out today. If we did right by you, a quick review helps us a lot. (link)"
A few things matter in that line.
Use the tech's or provider's first name. People remember the person, not the company. A review ask from "the team" reads like a mass blast.
Send one link that goes straight to the place you want the review. Not your home page. Not a page with five buttons for five sites. Every extra tap loses people.
Send it from the number they already know. If they called you at that number, a text from it looks real. A text from a random short code looks like spam.
Send it once. Maybe one gentle nudge a few days later. That is it. Three or four reminders turns a happy customer into an annoyed one.
Read the replies, all of them
This is the part most setups get wrong. People don't only tap the link. They reply to the text.
"Marco was great, thanks!"
"Still hearing a drip under the sink."
"Who do I talk to about the bill?"
If those replies go to an inbox nobody reads, you just asked a customer to talk to you and then ignored them. The drip under the sink is worth far more than a review. It is a callback you can do before it turns into a bad review on its own.
So decide before you turn this on who reads the replies, and by when. One named person. The same day. If the reply is a problem, that person calls the customer, not texts. A call says "we heard you" in a way a text does not.
I'd also say this plainly. Send the ask to everyone whose job closed, not only the ones the tech thinks went well. Picking who gets asked is a guess, and the customers who had a rough visit are the ones you most need to hear from. If something went wrong, you want them replying to your text, not to the whole internet.
What can go wrong
A few things break this setup. Most of them are boring, which is why they get missed.
The job never gets marked done. If techs close work orders in batches on Friday, every review text goes out Friday night for jobs from Monday. Check how your team really uses the status before you tie anything to it.
The phone number on file is wrong or old. The text goes nowhere and nobody knows. Look at how many review texts fail to deliver each week. If the number is high, the problem is in how numbers get typed in at booking, not in the review step.
Repeat customers get asked every visit. Someone who books a cleaning every month does not need a review ask every month. Set a rule, such as once a year per customer, and stick to it.
The link breaks. Review pages change. Click your own link once a month. It takes ten seconds.
The ask goes out after a job that was cancelled or turned into a no-charge return trip. Make sure the trigger is "completed," not "closed for any reason." Those are often different statuses, and the wrong one sends a thank you to someone whose visit never happened.
What I'd do this week
Don't buy anything yet. Start by looking at your own system.
Find the one status that marks a job as done. Look at the last 20 jobs and check that the status was set on the day the work happened. If it wasn't, fix that habit first, because everything else depends on it.
Write the text. Keep it under 30 words, with the person's name and one link.
Pick the person who reads replies, and tell them it is part of their day now, not a side task.
Then turn it on for one week and read every reply that comes back. You'll learn more about how your jobs really went from those replies than from the reviews themselves.
This is the kind of small system we build inside businesses at Lumina Software. The hard part is rarely the text. It is making sure the trigger fires on the right jobs and someone owns the answers.
Tomorrow, pull up the last 20 closed jobs and check what day each one was marked done.
Written by Lumina Software. Have a question? Book a call