· 4 min read
How to Ask a Customer for a Review
Manesh Jayawardhana
CIO & Co-founder
Most review requests fail for one of two reasons: they arrive at the wrong moment, or they read like they were sent by a system rather than a person.
“Your feedback matters to us” three weeks after a purchase gets deleted. “Thanks for choosing us for Friday’s catering — if it went well, a one-line review really helps a small place like ours” gets answered, because it’s specific and it’s obviously from someone.
What makes someone actually write one
Three things, and none of them is persuasion.
Timing. Soon after the experience, while the detail is still available to recall. For a service, a day or two after delivery. For a product, after it’s been used, not at checkout.
Specificity. Naming the actual purchase proves a person is asking. A generic request signals an automated sequence, and automated sequences get ignored.
Low friction. One link, going directly to the review form. Every extra step — log in here, find the business, select a category — loses people who genuinely intended to write something.
There’s also a rule worth knowing before you design any of this. Filtering out unhappy customers before showing them the review link is called review gating, and it violates the terms of Google and most major platforms. Google’s own policy is explicit about not discouraging or prohibiting negative reviews. Ask everyone; fix the service instead.
Why people get stuck here
- Asking too early. At checkout the customer has nothing to review yet.
- Asking too broadly. “Leave us a review” with no context reads as spam.
- Too many steps. A link to a homepage rather than the review form loses most of the people who clicked it.
- Gating. Screening for satisfaction first feels sensible and is against the rules.
What a good request looks like
One sentence of context, one link
Name what they bought, say why a review helps, give the link. Two sentences maximum for SMS, three for email.
Honest about the effort
“A one-line review” sets an achievable bar. “Tell us about your experience” implies an essay, and people who don’t have time for an essay write nothing.
Sent by a name
From a person at the business, not a no-reply address. It changes the response rate more than the wording does.
| Channel | Length | Best For |
|---|---|---|
| SMS | One sentence, one link | Local services, quick jobs |
| Two or three sentences | Larger purchases, B2B | |
| In person / card | A QR code to the form | Hospitality, retail |
Common mistakes to avoid
- Screening customers for satisfaction before offering the review link — that’s review gating and it’s prohibited.
- Offering a discount in exchange for a review, which most platforms prohibit and which readers discount anyway.
- Sending the same message to everyone with no purchase detail.
- Chasing more than once. A single follow-up is reasonable; a sequence of four is a complaint waiting to happen.
- Directing people to a review site your customers don’t use, rather than the one that matters for your business.
How to do it with Review Request Generator
The Review Request Generator drafts a message that fits the channel, with nothing sent from the page itself.
- Name the business and the specific purchase or job.
- Choose the channel — SMS needs one sentence and a link, email can carry a little more.
- Pick a tone that matches how you normally speak to customers.
- Send it while the experience is recent, to everyone, not just the customers you expect to be happy.
Other customer-facing templates are in the tools directory.
Frequently asked questions
When should the request go out?
After the customer has actually experienced the thing — after delivery and use, not at purchase. For a service, within a day or two. Any later and the specifics have faded.
Can I ask only happy customers?
No. Review gating breaches the terms of Google and most major platforms, and it distorts the signal that makes reviews worth reading. Ask everyone; treat negative reviews as information.
Should I offer an incentive?
Most platforms prohibit incentivised reviews or require clear disclosure. A specific, human request outperforms a discount anyway — people write reviews because they were asked properly, not because of a voucher.
Final thought
Write the message you’d send to one customer you remember, then use that for everyone. The specificity is what works, and it survives being templated better than you’d expect.