Pool work has one advantage most service businesses lack: the client can see the result. A green pool becomes clear, and that change is visible from the kitchen window. That visibility is the whole basis of a review routine. Ask at the moment the change happens and the client has something specific to write about. Ask at any other time and you are asking them to remember a feeling.
Reviews follow a visible result
A client who has watched a pool go from unusable to swimmable in a couple of visits has an opinion ready. They know what it looked like before. They can describe the difference, which is exactly what a review needs in order to be useful to the next person reading it.
The mistake is treating reviews as a general request for goodwill. A message at the end of the season asking for a review lands on a client whose last visit was three weeks ago and who is thinking about closing, not about the recovery. The specific moment produces the specific review.
Ask when the water turns
The trigger is a recovery: the visit where the pool stops being a problem. The technician knows when that has happened because they are the one who saw the water the week before. The cleanest arrangement is a simple flag from the technician, and a text from the office the same day.
The same logic applies at opening and closing, where the work is a single visible event rather than a series. Those are also the visits where the client is most likely to be home, which makes the ask feel like part of the service rather than a message out of nowhere.
Keep the ask small
A review request that asks for a paragraph will get nothing. A request that names what happened and offers one link gets a sentence, which is all a review needs.
Something close to this works: the pool is clear again after two visits, if that matches your experience a short review helps other owners find us, and here is the link. One link, one ask, no follow-up sequence. If the client does not reply, the answer is no.
Elevoi sends SMS follow-ups, so the review request can go out as a text from the same number that confirmed the booking, which is the number the client already recognises. Removing that small unfamiliarity is worth more than a longer message.
Decide who gets asked
Not every client is a good candidate, and asking the wrong one produces a review you then have to manage.
Ask the clients whose pools you turned around, the ones who have stayed through a season, and the ones who referred a neighbour without being prompted. Skip the client whose last visit ended in a disagreement about a bill, and skip the one whose pool has a structural problem you have already told them about. The ask is not a questionnaire, and nobody benefits from an invitation to complain in public.
Route the unhappy reply first
The most valuable thing a review request produces is not always a review. Sometimes it is a reply that says the pool is still cloudy, or that the technician came late, or that the gate was left open. That is a service issue you would otherwise hear about months later, or never.
Handle it as a service issue. The owner calls, the visit is checked, and the problem is resolved before it reaches a public page. A review request that surfaces a problem privately has done its job just as well as one that produces a public review.
Make it a monthly habit
Reviews accumulate when someone owns the routine. Once a month, look at the visits that involved a recovery or a season milestone, send the requests for the ones that went well, and check whether the requests are producing reviews or silence.
If they produce silence, the message is probably too long or the timing too late. If they produce reviews that mention a specific technician, keep that technician's name in future confirmations, because the review is telling you what the client actually values.
AI receptionist for pool services covers how the booking, confirmation, and follow-up messages run on one number, and text review requests for pool services covers the wording in more detail.