Asking for a review sounds simple. You had a good interaction with a customer, you'd like them to say so somewhere visible. In practice the question of when, how, and where to ask is more complicated than most owners think, and the platform rules around asking for reviews (especially on Google and Yelp) draw lines that are easy to cross without realising. This guide covers asking for a review in both senses: asking customers for the structured feedback you collect through your own forms, and asking them to leave a public review on a third-party platform.

On this page

Two kinds of "review" worth asking for

When most owners think about "asking for a review," they think about Google or Yelp. That's the public, visible piece. There's a second kind of review that's at least as useful and often more useful, which is the structured feedback you collect on your own forms. Both are reviews of your business. They serve different purposes, work in different windows, and benefit from being asked differently.

Structured feedback is what the customer tells you directly, in a format you control. It's usually delivered as a short form after the interaction, on a QR code or short link. It catches the silent middle (customers who'd never write a public review but will fill in a short form), and it gives you texture you'll never get from a star rating.

Public reviews are what the customer tells the world. They're harder to get, weighted toward the extremes (very happy or very unhappy), and they drive how prospects find and judge you.

Both matter. The mistake most owners make is asking only for the second kind, which means they miss everything the silent middle had to say.

When to ask

Timing is more important than wording.

For structured feedback, ask while the experience is still fresh. For an in-person business, that's at the till, at the table, or on the way out. For online, that's right after the service is delivered or the order arrives. The window closes fast; a customer who isn't asked within twenty-four hours of the experience is much less likely to respond, and the response gets fuzzier the longer you wait. Why timing matters as much as the question covers the timing problem in more depth.

For public reviews, you can ask a bit later. The customer needs to have processed the experience enough to want to write about it. Same day works. Three days later works. Two weeks later usually doesn't (they've moved on).

There's a useful sequence here: ask for the structured feedback first, and then prompt for the public review afterwards, only to customers who indicated they had a good experience. This is the loop most reputation tools support, and the one that respects the platform rules around solicitation (more on that below).

What to say when asking for a review

The most effective asks are short, specific, and easy to act on.

For structured feedback at the point of experience:

"Quick favour: can you scan this and tell us how it went? Takes a minute and helps us a lot."

For follow-up by email or SMS:

"Hi [name], thanks for coming in today. If you've got a minute, we'd really value your thoughts on how it went: [short link]."

For a public review request, after positive structured feedback:

"Thanks for letting us know. If you'd be willing to share that on Google, it helps other people find us: [Google review link]."

The principles are the same in each case:

  • Specific (not "leave us a review") rather than generic
  • Personal (a human asking) rather than corporate
  • Easy (one click, one tap) rather than involving any navigation
  • Honest about why you're asking (helps the business, helps other people find you)

The mistakes are equally consistent:

  • Long preambles about how important the customer is
  • Pre-filled scripts in the review request
  • Templates that read as templates
  • Multiple asks in one message

Channels: how to deliver the ask

A short list of what works for each channel and what doesn't.

QR code at the point of experience. The highest-converting channel for in-person businesses. The customer is right there, has just had the experience, and has their phone. Place the code where the customer naturally pauses (the till, the table, the receipt). The QR code feedback guide covers placement in depth.

SMS. Works well for the follow-up ask, especially for service businesses that have the phone number already. Response rates are high; the cost per message is low. Keep it short.

Email. Works for online businesses and for follow-ups where you have the email address. Response rates are lower than SMS, but volume can make up for it. Subject lines matter more than body copy. Avoid anything that sounds like a campaign.

In person at the till. The single most effective channel for short structured feedback (via QR), and the second-best for public review asks. A staff member politely mentioning "if you've got a second to leave a review, it really helps us" converts better than any automated channel.

Printed prompt with no human ask. Receipts, table tents, bag inserts. Lower conversion than an active ask, but cumulative effect at scale is meaningful and the cost is near zero.

Platform rules around asking for reviews

This is the part most owners don't know about, and the part that can get you into trouble if you don't.

Google. You can ask customers for reviews. You cannot selectively solicit only customers you think will leave positive reviews. "Review gating" (where you only ask happy customers and route unhappy ones elsewhere) is explicitly against Google's review policy. Enforcement is uneven; the businesses that get caught get penalised.

Yelp. Yelp's policy is to discourage all solicitation. Asking customers for Yelp reviews can trigger a "consumer alert" warning on your profile. Their position is that reviews should come from customers who decided to write one without prompting. This is much stricter than other platforms, and worth understanding before you build any kind of ask into your Yelp workflow.

Trustpilot. Trustpilot encourages business-initiated invitations through their tools. Their position is the opposite of Yelp's: they want you to invite customers, and they provide infrastructure for it.

TripAdvisor. Allows asking. Provides tools for requesting reviews from recent guests.

Booking.com. Reviews are built into the booking flow. You can't ask outside that flow; you don't need to.

Facebook. Allows asking. No formal solicitation policy.

The practical implication: build your ask flow around Google as the primary platform you direct customers to, with Trustpilot or industry-specific platforms as secondaries depending on category. Do not build a Yelp-directed ask flow. For everything, avoid the appearance of selectively soliciting only positive responses; even where it's not explicitly banned, it produces less trustworthy review patterns and can be detected by platform algorithms over time.

The loop: structured feedback first, public review second

The cleanest pattern for asking for a review respects both the platform rules and the practical reality that not every customer is happy enough to leave a public review:

  1. Ask every customer for structured feedback via your own short form.
  2. Read the responses (or have a tool summarise them for you).
  3. For customers who indicated they had a good experience, optionally show a prompt asking if they'd also leave a public review.
  4. For customers who indicated a problem, route the response to whoever can act on it, and follow up to address the issue.

This pattern is sometimes called "review routing" or "positive response routing." Qria supports it as a built-in feature: positive responders on a QR-code form see a prompt to also leave a Google review, while critical feedback stays in the system for the business to act on. The structured feedback piece runs alongside your public review aggregation, so reviews from Google, Yelp, Trustpilot, TripAdvisor, and Booking.com sync into the same dashboard as the form responses, summarised together by AI.

The reason the loop works is that it doesn't selectively solicit positive Google reviews; it asks everyone, reads what they say, and offers the public-review path to customers who indicated they had a positive experience. The asking happens at the structured-feedback level, where it's allowed and useful.

What not to do

A short list of mistakes that backfire:

  • Offering incentives for reviews. A discount, a free coffee, a gift card. Most platforms prohibit this. Customers can spot it, and reviews you bought aren't worth what you paid for them.
  • Asking too soon. Before the experience is complete, before the customer has formed an impression, before they've had time to want to say something.
  • Asking too often. A customer who's already left you a review doesn't need to be asked again.
  • Pre-filling the review text. Some tools offer a "suggested review" prefill. Customers don't fall for it; reviewers and platforms can tell.
  • Routing only happy customers to public review platforms while routing unhappy ones to a private complaints flow without ever asking the question. This is the version of review gating that gets businesses penalised.
  • Asking for a review on every channel at once. Pick one. Multiple asks dilute response on all of them.

Frequently asked questions

Is it okay to ask customers for a review on Google?

Yes. Asking is allowed. Selectively asking only customers you think will leave positive reviews is against Google's policy, but a general ask of every customer is fine.

Can I offer a discount in exchange for a review?

No. Most platforms prohibit incentivised reviews, and even where they don't, the reviews you generate this way aren't useful (customers know what you want from them) and can be detected over time.

When is the best time to ask for a review?

For structured feedback, immediately after the experience. For public reviews, same day or up to a few days later. Two weeks later, the response rate drops sharply.

What should I say when asking for a review?

Keep it short, specific, and personal. "If you've got a minute, we'd value your thoughts on today; here's a quick link" works better than any longer pitch.

Should I ask every customer for a Google review?

You can ask, but you'll get higher quality results if you first ask for structured feedback and then only prompt the positive responders to leave a public review. This isn't review gating; it's reading customer sentiment before deciding whether the public-review path is appropriate.

How many reviews should I be aiming for?

Quality and recency matter more than total count. A steady trickle of recent reviews is more valuable than a big batch followed by silence. Aim for a regular cadence rather than a target number.