How to ask for reviews: timing, channels, and templates

Knowing how to ask for a review matters less than knowing when, and both matter less than how little you make the person do. Most review requests fail at a predictable point: the customer says yes, then meets a form, a login, or a five-step process, and quietly stops. This guide covers timing, channel, and wording, with templates for email, SMS, and in-app, plus how to ask on Google, what to do when the review isn't good, and how to make the whole thing repeat itself.

Timing beats wording

You can rewrite a request twenty times and move the response rate less than you would by sending the same words two weeks earlier.

There's a window after someone gets value from you, and it's shorter than most companies assume. A customer who has just solved the problem they hired you for will say yes to almost anything reasonable. The same customer, six weeks later, has moved on — the problem isn't top of mind, your name isn't either, and your request now reads as an interruption from a company they barely think about.

So the trigger should be an event, not a date. A support ticket resolved happily, an onboarding milestone hit, a repeat purchase, a renewal, a reply that says "this is exactly what we needed" — these are the moments. Quarterly review drives fail because they ask everyone at a moment that's meaningful to your calendar and to nobody else's.

The one exception worth naming: for physical products, wait for delivery plus enough time to actually use the thing. Asking on the day it ships gets you a review of your shipping.

Which channel to ask through

Channel	Best moment to use it	What it's good for	Main weakness
Email	Any milestone with a paper trail	Detail, links, attachments, an easy record	Easy to ignore; lands in a crowded place
In-app prompt	Immediately after a success event	Highest context — they're already using the thing	Only reaches active users; annoying if mistimed
SMS or WhatsApp	Post-delivery, post-appointment	Read almost immediately, feels personal	Intrusive if the relationship isn't warm
In person or on a call	During a conversation that's going well	Hardest to refuse, highest quality yes	Doesn't scale; needs a follow-up link anyway
QR code on packaging or receipt	At unboxing, at the counter	Reaches customers you have no contact details for	No control over timing; low completion unless the landing is instant
Direct message on social	After someone posts something positive	The person already volunteered enthusiasm	Reads as opportunistic if the relationship is thin

The pattern across the row: channels that reach people in the moment beat channels that reach people at your convenience. Every one of them ends the same way, with a link — which is why the thing on the other side of the link decides whether any of this works.

B2B and B2C ask differently

The advice above holds in both, but the shape of the request changes.

In B2B the obstacle is rarely willingness — it's approval. A delighted user often can't say yes alone, because marketing, legal, or their manager has an opinion about the company appearing on someone else's site. Ask the person who used the product, then make it easy for them to forward the request internally: state what will be published, where, and that they can withdraw it later. A request that survives being forwarded is a request written for two audiences.

In B2C the obstacle is attention. Nobody needs permission, and nobody is thinking about you. The request has to land in the same minute the person is thinking about the product — after delivery, after the first use, after a support conversation went well. A B2C ask that arrives a week late is competing with everything else in an inbox, and it loses.

One consequence worth noting: B2B requests can be longer and more explanatory, because the recipient may need to justify saying yes. B2C requests should be short enough to read on a lock screen.

What to actually say

Three properties separate requests that get answered from requests that don't.

Be specific about what you're asking for. "Would you leave us a review?" is a request for an unbounded task. "Would you record two minutes about what your reporting looked like before?" is a request for a defined one, and defined tasks get done. Naming the length is part of it — an unstated time commitment is assumed to be large.

Say why you're asking this particular person. Not flattery — a reason. "You mentioned the onboarding was the part that surprised you, and that's the thing prospects ask us about most" tells them their answer is useful in a specific way. A mass-send tone invites a mass-send response, which is usually silence.

Make refusing easy. Counterintuitively, an explicit "no problem at all if you'd rather not" raises response rates, because it removes the pressure that makes people postpone the decision rather than make it. A postponed yes is a no with extra steps.

And keep the ask to one thing. A message that asks for a review, a referral, and a case study call is a message that gets deferred until there's time to think about it, which never arrives.

Review request templates

Three starting points. Change the specifics — a template that reads like a template gets treated like one.

Email, after a support win:

Subject: quick favour after that fix?

Hi [name] — glad we got the export issue sorted. If you have two minutes, would you be up for recording a short video about what that process looked like before? Mostly useful for people evaluating us who have the same problem. Link's below, it opens straight into a recorder — no account or download. Completely fine to skip it. [link]

SMS or WhatsApp, after delivery:

Hi [name], hope the [product] is working out. If you've got a minute, we'd love a quick review — this link opens straight to it, takes about 60 seconds: [link]

In-app, after a milestone:

You've just [completed the thing]. Mind telling other people what that was like? 60 seconds, opens in your browser, no forms. [Record something] · [Not now]

Two things all three share. The link goes somewhere immediate — not to a login, not to an app store. And the time commitment is stated up front, because the unstated one is always assumed to be longer.

Asking for Google reviews

Google reviews sit slightly apart from everything else here, because the mechanics are fixed and the payoff is different.

The mechanics first. Your Google Business Profile generates a direct review link — one URL that opens the review form with your business already selected. Find it in the profile dashboard under the option to ask for reviews, shorten it if you like, and use that link everywhere. Sending someone to search for your business and find the review box themselves adds three steps and costs you a meaningful share of the people who intended to help.

A few rules specific to this platform. Don't ask in bulk from a single sitting, because a cluster of reviews arriving within an hour looks exactly like what it is. Don't offer anything in return; Google's policy is explicit and enforcement includes removing the reviews you paid for. Don't filter — asking only customers you expect to be positive, or routing unhappy ones to a private form first, is against the terms and increasingly detectable. Ask everyone, and treat the occasional bad review as the cost of a profile people believe.

What Google reviews buy you is independence. A visitor knows you didn't write them, can read the bad ones, and can see how you responded. What they can't do is answer a specific objection — they're short, written to no brief, and structurally uniform. If the thing stopping your prospect is whether this works for a team of three, no volume of five-star ratings addresses it. You also can't move them to the page where the decision happens; a Google profile is not your pricing page.

So ask for both, in different moments. Google reviews for independent credibility, your own collected reviews for the pages that need to persuade. On the display side, how to display reviews on your website covers what each method costs you in page speed.

Asking for video specifically

Video is the strongest thing you can ask for and the one most people assume they'll be refused, so it gets asked for last or not at all.

The assumption is usually wrong, but not for the reason you'd hope. Customers aren't refusing because they're camera-shy — they're dropping out of a process. A customer who agreed to record something and then met an app install, an account creation, and an email confirmation goes quiet somewhere in that chain. Completion rate tracks the number of steps between "sure" and a record button, not the medium. That's a design problem, and it's fixable in a way that shyness isn't.

Two adjustments do most of the work. Send a link that opens straight into a camera prompt, and give the person questions rather than a blank invitation — "tell us what you think" produces rambling, "what were you struggling with before?" produces something usable. A full question set is in video testimonial questions, the video-specific version of this guide is how to ask customers for video testimonials, and what to do with the footage once you have it is covered in video testimonial best practices.

Asking for feedback is a different request

These get conflated, and conflating them costs you both.

Feedback is private and diagnostic. You want the truth, including the parts that would look bad in public, and you want it from people who are unhappy as much as from people who aren't. A review is public and promotional, and asking an unhappy customer for one is asking them to lie or to leave.

So sequence them. Ask for feedback broadly, read it, and then ask for reviews from the segment whose feedback was good. This isn't manipulation — it's the difference between market research and marketing, run in the right order. Asking both in one message gets you a diluted version of each.

When the review isn't good

Ask enough people and eventually someone tells you something you'd rather not publish. This is the point where most review programmes drift into only asking the customers who'll say nice things, which is the beginning of a proof section nobody believes.

Two things are worth separating. A negative review on a public platform is a reputation event, and the response to it is a response — visible, unpanicked, specific about what you'll do. Prospects read the replies more carefully than the reviews, and a company that answers criticism calmly reads as one that has nothing to hide. A negative response to your private request is something better: free diagnostic information from someone engaged enough to explain the problem. Fix it, tell them you did, and a surprising number of those people become the ones who record a testimonial six months later.

What you shouldn't do is route unhappy customers into a private feedback form while sending happy ones to a public platform. That's review gating, it violates the terms of most platforms including Google, and it's easy to detect from the outside because the resulting rating distribution looks nothing like a real one.

The one legitimate filter is what you publish on your own site. You're not obliged to embed every submission — moderation before publication is normal and expected. The distinction is between choosing what to feature and manipulating who gets asked.

Making it repeatable

Most companies run one review push, collect a handful, and never do it again. The section on the site stays frozen at that batch, dated, and starts reading as an abandoned corner rather than as evidence.

The fix is to attach the request to something that already happens, instead of scheduling it. If your product has a success event — a project shipped, a milestone hit, a plan renewed — that event is your trigger, and the ask can fire automatically from it. If your business runs on human contact instead, attach it to a habit: the last message of a completed engagement, the follow-up call after delivery, the reply to any customer who volunteers praise. In every version, the rule is one ask per win rather than one campaign per quarter.

Two guardrails keep automation from turning into spam. Cap how often any individual can be asked — once a year is plenty for most businesses — and suppress anyone who has already recorded something or already said no. And keep a human in the loop for the message itself; a request that reads as generated will be treated as generated.

The other half of repeatability is what happens after the yes. If each submission means downloading a file, hosting it somewhere, and editing the page by hand, the process will stop the moment you get busy. Whatever you use should take the recording, hold it for approval, and publish it without anyone touching code.

What kills response rates

The most common failure has nothing to do with the wording. It's what happens after the yes. A request that lands somewhere requiring an account, an app, or a form with eleven fields converts a willing customer into an abandoned tab. Everything else on this page is downstream of that.

The rest is smaller but adds up. Asking too many people at once produces a batch of identical, dutiful reviews written to no particular purpose. Asking the same person repeatedly after silence turns a soft no into a hard one. Offering a discount in exchange for a review taints everything you collect, and on most platforms breaks the terms of service outright. And publishing what arrives without checking consent creates a problem you'll discover at the worst possible time — a name and face on a commercial page needs a lawful basis, and consent belongs inside the collection flow rather than in an email chase afterwards.

For where the collected proof should go once you have it, social proof examples sorts the options by how easy each is to fake, and the tooling side is covered in video testimonial software.