When to ask for a review, on which channel, and what to write - and what not to do: asking repeatedly, asking everyone, or offering something in exchange.
Key takeaways
- The right moment is immediately after the customer received value, not after the invoice was paid.
- One request is enough; a second reminder already costs you goodwill.
- The link must open the review form directly, not the business's main page.
- Do not ask everyone - ask people whose experience ended well.
Most businesses get no reviews because they never ask, and most of those who do ask get the timing wrong. One request, on a channel the customer reads, at the moment they are happiest - produces more reviews than any repeated reminder.
When to ask, by business type
| Business type | The right moment | Why |
|---|---|---|
| Service at the customer's home | Immediately after the visit | Satisfaction is at its peak |
| Online store | A few days after delivery | After they used it, not when it arrived |
| Ongoing service | After a meaningful milestone | There is something to write about |
| Restaurant or physical premises | The day of the visit | The memory is fresh |
| A long project | At handover, after successful delivery | Before maintenance discussions begin |
Row two is the one most often got wrong: a request sent the moment the parcel is delivered reaches a customer who has not opened it yet, so it gets fewer responses - and occasionally a negative review about something never examined.
What to write
Four elements and nothing more: a short thank you, why it helps you, how long it takes, and a direct link. All of it in two lines. A long request gets fewer responses, because it looks like a task.
What does matter is making it as specific as possible - the customer's name, and ideally what was done for them. "Thank you for choosing us" works less well than "thank you for trusting us with yesterday's installation", because the second proves a real person wrote it.
Which channel to send on
In Israel, WhatsApp and SMS get far better response than email, particularly when the request arrives close to the event. Email fits when it has another reason to be sent anyway - a service summary or an invoice - with the request sitting at the bottom.
What to know: a business-initiated WhatsApp message through the business platform requires a pre-approved template, so prepare it before building the process - more in WhatsApp broadcast versus campaign limits.
Why not ask everyone
Because a blanket request produces negative reviews from customers whose experience did not end well. The goal is not to hide negative reviews - that is not possible anyway - but to avoid soliciting them by accident.
The practical rule: do not send a request to a customer with an open service ticket, one whose delivery was delayed, or one who has already complained. Those customers get a phone call before any request - and once the problem is resolved they are often among the best reviewers you have.
What not to do
- Ask repeatedly. One reminder at most, and even that is not always right.
- Offer something in exchange. A discount for a review damages credibility and conflicts with platform policies.
- Write the review for them or supply suggested wording.
- Filter - sending only to people who said something nice on the phone.
- Ask employees and friends - it is recognisable, and it backfires.
The second point catches businesses out without their knowing: incentivising reviews conflicts with the major platforms' rules, and beyond that it produces reviews readers recognise as inauthentic.
What to do with a negative review
Reply. A short, factual reply with no argument, offering to continue privately - that is what other readers see, and it shapes their impression far more than the review itself.
What does not work: a defensive reply, a denial, or an attempt to explain why the customer is wrong. Even when they genuinely are, the next reader sees a business arguing with its customers. A reply that acknowledges the experience and offers to put it right is the only thing that turns a negative review into an asset.
How to build it
- Decide the trigger - exactly what fires the request, and after what delay.
- Add a check that skips customers with an open problem.
- Write two versions - one for service, one for products.
- Use a direct link to the review form.
- Measure - how many sent, how many written.
- Add an internal alert for negative reviews, so somebody replies.
Point 4 sounds technical and is decisive: a link that opens the business profile rather than the review form lowers completion substantially, because the customer has to find where to click.
Where should you ask - Google or somewhere else?
For most local businesses in Israel, Google reviews are what influence a new customer's decision, so they are the first target. For businesses selling through a platform - a marketplace, a comparison site, a booking platform - reviews there matter just as much, because that is what is visible at the moment of decision.
What does not work is asking for both in the same message. A customer given two options usually picks neither, so choose one destination per customer type and change it only when something else becomes more important.
There is also value in reviews that never reach a platform: a customer who sent you a kind sentence on WhatsApp gave you a genuine testimonial, and with their permission it can go on your site. It is not a substitute for a public review, but it is free and immediate.
What to measure
- How many requests were sent per month, and how many were delivered.
- How many reviews were actually written - the ratio between those two is the real metric.
- How long passed between the event and the request.
- The average rating from requested reviews versus unprompted ones.
The last often surprises: customers who are asked tend to rate higher than those who write unprompted, simply because a very unhappy customer writes without being asked. That is another argument for asking systematically rather than only when you remember.
Sources
Frequently asked questions
How many reviews are enough?
There is no magic number, but frequency matters more than volume: a steady stream of new reviews tells a reader the business is active, while fifty reviews from two years ago says the opposite. A standing process beats a one-off push.
What if nobody writes one?
Check three things in order: whether the request arrives at all (delivery rate), whether the link works and opens directly, and whether the timing is right. In most cases the problem is one of those three rather than customers' willingness.
Can we ask on the phone?
Yes, and it sometimes works best - especially after a successful service call. What matters is sending a message with the link immediately afterwards, because a customer who said "of course" on the phone will not go looking for where to write.
What about old reviews that hurt?
You cannot delete a genuine review, and it is not worth trying. What works is replying factually and generating a stream of new reviews reflecting the current state - a negative review among twenty recent ones reads very differently from one that is the most recent thing written.
Keep reading
Related service
Customer Service
One queue across every channel, with an owner and a deadline.
About the author
Yehonatan Saadia
Freelance automation, web & MVP developer
I'm Yehonatan Saadia, a senior developer who builds business automation, custom websites, and MVPs for small and mid-sized companies across the US, Europe, and Israel. These guides come from real client work, not theory.
Work with meHave a project like this?
Tell me what you're trying to automate or build and I'll tell you the fastest reliable way to ship it.