Most satisfied customers never leave a review. Not because they were unimpressed and not because they decided against it - because no one asked them at the right moment in the right way. The customers who do leave reviews unprompted are mostly the unhappy ones, which is why so many small businesses end up with rating profiles that look worse than the actual experience they deliver.
Asking for reviews is the most cost-effective thing a business can do to improve its reputation, and almost every business does it badly. They ask too late, they ask the wrong way, they make it feel transactional, or they do not ask at all. This article walks through how to ask in a way that produces real reviews from real customers without crossing into pestering.
Why timing matters more than wording
The single biggest variable in whether a customer leaves a review is the time gap between the experience and the request. A request sent immediately after the experience captures the customer while the impression is still vivid. A request sent two weeks later catches the customer when the experience has already faded into the background of normal life and the motivation to write anything at all has dropped to almost zero.
The right window varies by industry. For a restaurant, the window is the same evening or the next morning. For a tradesperson, it is the day the job is finished and the customer is standing in their finished space, still happy with the work. For a service business, it is the moment the deliverable lands. The wording of the request matters less than catching the customer inside the window.
The reality
Most review requests fail not because the wording was wrong but because the timing was wrong. A perfectly crafted email sent two weeks after the job is finished will produce fewer reviews than an awkwardly worded text sent the same afternoon. The window of high willingness is short. The system has to be set up so the request goes out inside the window automatically, not when someone in the office happens to remember.
The mechanics of the ask
A good review request has four properties. It is sent at the right time. It comes from a person, not from a generic system address. It explains why the review matters in concrete language. And it makes the next step a single tap or click, with the link going directly to the place the review will be left.
The four properties of an effective request
- Timed correctlyInside the window of high willingness for your industry. The same day or the day after the experience for most businesses; the moment of completion for most service work.
- PersonalFrom a named person at the business, not from "the team" or "noreply". The named person creates a sense of obligation that "the team" does not.
- Specific about the whyAn explanation that small businesses depend on reviews to be found, that the reader's review will help other people in the same situation, and that it takes a few minutes. Not generic appeals to "rate your experience".
- One tap to the destinationA direct link to the review form on the platform you actually want the review on. Not the homepage of the platform. Not a choice between three platforms. One link, going to one place.
The medium
SMS produces the highest response rate by a significant margin for most small businesses. Email is the second-best option and is more practical for businesses that already have customer email addresses but not phone numbers. In-person QR codes work for foot traffic businesses but produce lower volume than direct contact. Verbal asks at the end of an interaction work surprisingly well when the staff member is comfortable with them, and almost not at all when they are not.
The wrong medium is whichever one you cannot reliably get through. A beautiful email sequence to an inbox the customer never checks is worse than a less polished text to a phone they read constantly. Pick the medium based on where the customer's attention actually is, not on which one is most comfortable for the business.
What to actually say
A working request template
- 1
Open with the customer's first name and a sentence that references the specific thing the business just did for them. Not "thanks for choosing us" - something concrete, like "thanks for trusting us with the kitchen install".
- 2
One sentence explaining why the request matters. Small business, reviews help us be found by other people who are looking, every review makes a real difference. Avoid the language of corporate communications.
- 3
The link, on its own line, with a clear label. "Leave a Google review here" is better than a bare URL.
- 4
A sentence acknowledging that it is a few minutes of the customer's time and that you are grateful for it whether they do or do not. Removes the pressure and makes it feel like a request, not an obligation.
- 5
Sign off with a real first name. Not "the team", not the business name, not a department.
The mistakes that make customers feel pestered
Three common mistakes turn a request into a nuisance. The first is asking too many times. Once is a request; twice is a reminder; three times is harassment. If a customer has not responded to two messages, the third one will not change their mind and will damage the relationship.
The second is offering incentives. Discounts, prize draws, free products in exchange for reviews - all of these violate the policies of every major platform and produce reviews that read as paid because they are. The platforms detect them, the customers feel bought, and the resulting reviews are worse than no reviews at all.
The third is filtering for positive reviews only. Sending the request only to customers who already said they were happy, asking customers privately how they would rate the experience and then only sending the link to the high scorers - both of these are detectable, both violate platform policies, and both undermine the legitimacy of the rating profile when customers notice the pattern.
Do not pre-filter customers
Asking only happy customers for reviews is gating, and platforms penalise it. Google, Trustpilot, and TripAdvisor all explicitly prohibit "review gating" - the practice of soliciting reviews only from customers expected to leave positive ones. The penalty when detected can include profile suspension. The right approach is to ask every customer the same way, accept that some reviews will be critical, and let the volume protect the average.
How often is too often
One request, one reminder a few days later if the customer has not responded, and then nothing. That is the entire cadence. The reminder is optional and should only go out if the customer has not actively declined - some customers reply saying they would rather not, and those should be removed from the system immediately.
The exception is for customers who have been with the business for a long time and have only ever been asked once. A second cycle a year later, framed around a recent piece of work, lands fine. The principle is that the request should always be tied to a specific recent experience, not to the calendar.
Once is a request. Twice is a reminder. Three times is harassment.
What to do with critical responses
When the system goes out to every customer, some of the responses will be critical. This is the right outcome - it means the system is working honestly. Critical reviews give the business something to respond to publicly and demonstrate to other customers that the business engages with feedback rather than curating it.
The article on responding to negative reviews covers the response framework. The short version is: acknowledge, do not contradict, offer a private path forward, sign off. Critical reviews handled well are better than no reviews at all, and they give the rating profile a credibility that uniformly five-star profiles never have.
When to get specialist help
Most businesses can build a working review request system on their own. The cases that benefit from specialist help are businesses with complex customer journeys where the right moment to ask is not obvious, businesses that have tried to build a system and are getting low response rates, and businesses recovering from a rating problem where the request volume needs to be calibrated against platform sensitivity.
If you are running a business with happy customers and a rating that does not reflect them, the first step is the same. Tell us what is happening. The first conversation costs nothing and we will tell you exactly what your request system should look like for your specific industry, customer journey, and current rating profile.