The review is decided before the invoice is paid
A homeowner forms their opinion of a plumbing or heating visit in the last ten minutes of it: whether the technician cleaned up, whether the price matched the quote, whether the explanation made sense. By the time a review request reaches them a week later, they are being asked to remember a feeling rather than report one.
That is why review efforts in home services underperform. The work is good, the customer is satisfied, and the request arrives too late, from an address nobody recognises, with no memory of the visit attached to it.
Ask while the relief is still fresh
The right moment is the same day, ideally within a couple of hours of the technician leaving. The customer has just had a problem solved. The house is quiet again.
Ask the technician to mention it before they go, in one sentence, without pressure: "You'll get a text from us about the visit — if it went well, a short review helps other people find us." Then the message arrives while the visit is still fresh in the customer's mind.
Send it by text, with one tap
Homeowners do not read business email on the day of a repair. They read texts. A short message naming the technician and the job, with a direct link to the review page, is the whole design.
Three things make the difference. The message identifies the business and the visit so it does not read as spam. The link goes straight to the review form rather than a homepage. The message arrives from a number the customer recognises, which is the same number that confirmed the appointment.
Elevoi sends that follow-up by text after the appointment, using the details already captured at booking. Nobody has to remember to send it, which is usually the reason review requests stop after the first busy week.
Make the ask specific and small
"Please leave us a review" is open-ended, and open-ended requests get postponed. A specific one is easier to act on: mention how the technician explained the repair, or whether the work was left tidy.
Keep it to one sentence of guidance. The customer is not writing an essay, and the review is more useful to the next reader when it says what happened rather than how wonderful everyone was.
Reply to what comes back
Reviews are not finished when they are posted. A reply that thanks the customer and names the specific job tells the next reader that someone is paying attention. A reply to a critical review, written calmly and without arguing the details, does the same and often more.
Read reviews as operational feedback rather than as a score. A comment about a late arrival window is a scheduling note. A comment about a technician not explaining the work is a coaching note. Route each one to the person who can act on it, and close the loop internally so the same comment does not reappear next month.
Keep it consistent across the crew
The effort fails when it depends on one organised person. If the request goes out only when that person is in the office, reviews arrive in clusters and stop during busy weeks.
Make the request part of the closing process rather than an extra task. The appointment ends, the follow-up goes out, the reply is logged, and the next job starts. That consistency produces a steady stream of reviews instead of a burst after a quiet month.
For a contractor with several technicians and a phone that rings all day, the AI receptionist for home services keeps bookings, confirmations and follow-ups running on the same rails.