How to ask customers for reviews: timing and wording

Most satisfied customers never leave a review. Not because they are unwilling, but because nobody asked, or because they were asked at the wrong moment in a way that took too much effort. Unhappy customers, meanwhile, often find their own way to a review site. The result is a public picture that is thinner and harsher than your real one.

The fix is to ask, consistently and fairly. This guide covers when to ask, which channels work, example wording you can adapt, the rule you must not break (asking only the happy ones), and how to give unhappy customers a private route to you without stopping them from posting publicly.

Ask everyone, not just the happy ones

Start with the rule, because it shapes everything else.

Some businesses send a short question first ("How did we do?") and then invite only people who answered positively to leave a public review, sending everyone else to a private form. This is often called review gating. Google's policies for business reviews say you should not discourage or selectively solicit positive reviews from customers, so gating breaks Google's rules, and other review platforms have similar policies. You can read Google's own wording in its prohibited and restricted content policy.

Beyond the rules, gating does not serve you well:

• It makes your public reviews less believable to readers, who expect to see a few honest complaints.
• It hides the information you most need, because the reviews you filtered out are the ones that tell you what to fix.
• It can cost you your reviews entirely if a platform decides you have broken its policies.

So the principle is simple. Every customer gets the same invitation to review you publicly. You can also offer every customer a private way to talk to you. What you cannot do is decide who gets which based on whether they seem happy.

When to ask

The best moment is shortly after the customer has had the experience you want them to describe, while it is still fresh and before ordinary life takes over.

Avoid asking before the customer has had a chance to judge, such as the moment an order is placed. Avoid asking repeatedly. One request and, at most, one gentle reminder a few days later is enough.

Which channels work

Use the channel you already use with that customer.

• Email. Works for almost any business with an email address on file. Easy to include a direct link to your review page.
• Text message. Short and immediate. Good for appointments and local services, if the customer has agreed to hear from you that way.
• In person. A friendly mention at checkout or at the end of an appointment, backed by a card or a printed QR code that links to your review page.
• Receipts and packaging. A short line and a QR code on an invoice, receipt or delivery note.
• Your website. A link in your footer or on your contact page, for people who come looking.

Whatever the channel, the link should take people straight to the place where they can write a review, with as few clicks as possible. Every extra step loses people.

How to word the request

Keep it short, personal and honest about what you are asking for. Say who you are, thank them, ask clearly, and make it easy. Do not offer rewards for reviews: most platforms do not allow incentives, and a paid-for review is worth less to readers anyway.

A post-stay email for a hypothetical small hotel:

Subject: How was your stay?

Thank you for staying with us last week. If you have a couple of minutes, we'd be grateful if you could leave a review on Google. It helps other travellers decide, and we read every one.

[Leave a review]

If anything wasn't right, you can also reply to this email and it will come straight to me.

A text after an appointment:

Thanks for coming in today. If you have a moment, a quick review would help us a lot: [link]. Any problems, just reply here.

A line at the bottom of a receipt:

Enjoyed your visit? Tell others on Google or TripAdvisor. Something not right? Tell us directly at the address below.

Notice that each example invites everyone to review publicly and, in the same message, offers a private route. Neither depends on how the customer felt.

Giving unhappy customers a private route, fairly

It is perfectly reasonable to want to hear about problems directly, so you can put them right. The key is that the private route is offered alongside the public one, to every customer, not instead of it for some.

Here is a pattern that respects the rules:

1. Send everyone the same short feedback form after their visit or order. One rating question, such as a would you recommend us question, and one open text box.
2. Show everyone the same review links on the thank-you screen, regardless of their answer. Do not hide or show the links depending on the score.
3. Follow up privately with low ratings. If someone gives a low score, send a personal apology and a route to a named person, and alert the team so someone deals with it. This does not stop them reviewing publicly; it simply means you are also trying to fix the problem.
4. Thank everyone. A happy customer gets a thank-you; an unhappy one gets an apology and action.

What decides the follow-up is what you do in response, never whether the customer is allowed to see the review link. Our guide to closing the feedback loop covers the follow-up side in more detail.

If a customer who had a bad experience goes on to post a negative public review anyway, reply to it well. See how to respond to negative reviews.

Make it a routine, not a campaign

A burst of review requests followed by months of silence produces a lumpy, unrepresentative set of reviews, and readers notice when every review on a page arrived in the same fortnight. A steady, automatic request after every visit or order works better: it keeps your reviews recent, which matters to people scanning your profile, and it gives you a fair sample of what customers think.

A few practical habits help:

• Automate the request so it does not depend on someone remembering.
• Check that review links work, and that they point to the right location if you have several.
• Track how many customers you asked and how many reviewed, by channel, so you can see what works.
• Read what comes in. More reviews are only useful if someone looks at what they say; our guide to Google reviews analysis explains how.

A short checklist

• Ask every customer, the same way, regardless of how happy they seem.
• Ask soon after the experience, once, with at most one reminder.
• Link directly to the review page.
• Offer a private route to a person alongside the public link, never instead of it.
• No incentives for reviews.
• Reply to reviews, good and bad.
• Feed what you learn back into fixes.

Doing this with Userforms

Userforms can send a short feedback form after each visit or order, built from a template or by describing what you want in a sentence. Put the same review links in front of everyone who answers, and let Journeys follow up automatically: an apology and a route to a person after a low rating, a thank-you after a high one, and an email alert to your team when something needs attention. On Pro, Journeys can also trigger webhooks, WhatsApp and Telegram actions.

Your Google, TripAdvisor, Yelp and Trustpilot reviews can be imported alongside your form replies (Plus plan and above), so you can see what both groups are saying, grouped into topics with their tone.

You can start for free, or see what each plan includes on the pricing page.