Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Checklists

Review Request Launch Checklist

A launch checklist for asking customers for reviews by email, text, card, app prompt or in person: who is asked, timing, incentives, platform rules and replies.
Checklistbeginner9 min readUpdated

When to run this checklist

Run it before a review request starts, whether it is a post-purchase email, a text after an appointment, an insert card, an app rating prompt or a request staff make in person. Run it again before the request changes: a new trigger, new wording, a new review tool, a new location joining, and above all before any incentive is attached, because incentives are where platform rules and consumer protection direction bite hardest.

Whoever owns the journey that carries the request runs the list: the lifecycle marketer for a store's post-purchase flow, the owner or marketing lead for a local business profile, the app team for a rating prompt, and the operations lead where staff ask in person. Someone who knows each platform's rules should see the incentive lines.

Neighbouring pages sit on either side. When the request is a step in an automated email or text journey, the email automation flow launch checklist gates the flow as a whole; this list covers the request inside it. A local business setting up its profile for the first time starts with the Google Business Profile setup checklist, and the Google Business Profile optimisation guide explains where reviews fit in the profile. App rating prompts are designed in the tutorial on app rating prompts and review replies. Replying to reviews is owned by the reply guides; this list only asks that someone owns it.

Before you start

  • The request itself: the message, card, prompt or script, with its trigger and any reminder.
  • The list of who is eligible, and how the sending tool decides it.
  • Each review platform's rules for requests and incentives, read in its own help centre.
  • Any feedback form or survey the business already sends after a purchase or visit.
  • Any incentive, prize draw or staff target linked to reviews, current or planned.
  • The consent records for customers who will be asked by text.
  • The moderation policy and the review markup on product pages, if the store has them.
  • A phone, to walk the path from request to published review.

The checklist

The groups follow the order of the request: who receives it, when and how it is asked, which rules govern it, and what happens once a review is written. A line that cannot be ticked stops the request until it can.

0/18

Who is asked

Timing and the request

Rules and incentives

Publishing and replies

Where each check is explained

The widget keeps the lines short so they can be ticked; the reasoning lives in the guides. Each check links to the page that explains it.

CheckExplained in
Every eligible customer askedCollecting reviews in the reviews and social proof guide
No form gating happy customers to the platformLocal reviews and reputation management
Staff, family and connected people disclosed or kept outIncentives, fake reviews and the rules
No shared devices or bursts to a backlogLocal reviews and reputation management
Request triggered from delivery or completed useTiming and the request
App prompt wired to a moment of completed valueSetting up app rating prompts and review replies
Product or service named, with a direct link to the formTiming and the request
At most one reminder, no discount in the requestTiming and the request
Request placed in the post-purchase flowBuilding a post-purchase email flow
Platform rules checked before any incentiveLocal reviews and reputation management
Any permitted reward independent of sentimentIncentives, fake reviews and the rules
Incentivised reviews labelledIncentives, fake reviews and the rules
No generated, bought or staff-written reviewsAI claims, endorsements and consumer protection
Messaging consent applied to text requestsE-commerce email and SMS flows
Moderation policy published and followedNot getting product reviews
Markup only for visible reviewsReview markup in the reviews and social proof guide
A named reply owner per platform and locationManaging reviews across many locations
Path walked from request to published review on a phoneNot getting product reviews

If an item fails

The who-is-asked and rules groups are the hard stops. The reviews guides draw on the FTC's business guidance and endorsement guides, the Competition and Markets Authority and Google Business Profile Help, and between them state one direction: fake reviews are prohibited, asking only likely-positive customers or suppressing negative feedback misrepresents the picture, incentives cannot depend on what the customer writes, and connections between reviewers and the business must be disclosed. On that reading, a gating form, a selective send or an incentive the platform does not allow is removed before the request starts, not fixed in the next version. That is general direction from those guides, not legal advice; a business trading in several countries checks the position in each.

Incentives deserve a line of their own, because the answer differs by platform. The local reviews guide reads Google's help centre as prohibiting incentives for reviews on a business profile, and the app ratings tutorial says both app stores prohibit incentivising ratings, so on those platforms no reward is permitted at all. Where a store's own review system allows one, it has to be offered whatever the customer writes and the reviews it produces labelled as incentivised wherever they appear. A staff target or prize draw tied to review counts is an incentive too, and the commonest way a business breaks its own rules without meaning to. Generated reviews are fake reviews, as the guide to AI claims and consumer protection puts it, and so are reviews written for a customer or by staff.

Timing and wording failures can usually be fixed the same day and are not a reason to keep a fair request switched off. A request sent on dispatch, a reminder chain, or a discount in the same message as the request are changed in the sending tool before launch. A text request to customers whose consent covers only email waits until the segment reads the right consent field, as the e-commerce email and SMS flows guide explains.

In the last group, a moderation policy that has not been published, or that allows removing reviews because they are critical, stops the launch: moderation is for abuse, spam and personal data. Review markup that covers reviews the page does not show is fixed before more reviews arrive; the structured data guide explains what the markup must match. A missing reply owner can go ahead with a note and a date, but not for long, because requests produce reviews and unanswered critical reviews are read by everyone who comes after. If walking the path on a phone shows a login wall, a long form or a broken link, fix it first; the troubleshooting page on not getting product reviews diagnoses each.

Watch what the programme is judged on. A team rewarded for the count of five-star reviews will drift towards exactly the practices this list rules out; Goodhart's law explains why, and the fix is to judge the request on whether every eligible customer was asked fairly.

A dog grooming business starts asking for reviews (illustrative)

Illustrative example — not a real result

Text and card requests at three salons

Emvari Grooming, an invented dog grooming business with three salons, plans to ask every customer for a review of their salon's business profile: a text the evening after each appointment, and a card handed over at collection with a link and a QR code to the profile's review form. The owner runs the list with the three salon managers. The who-is-asked group fails on the first line checked: the booking tool already sends a two-question feedback form after each appointment, and anyone who scores four or five stars is shown a link to leave a public review, while lower scores go to a private inbox. Nobody had set it up deliberately; it was the tool's default. The owner switches the routing off, so every customer sees the same request. The rules group fails too: one salon manager runs a monthly staff draw with a £50 prize for whoever is named in the most new reviews, and has been telling customers about it. The draw ends that week. The text request passes the consent line only after the segment is rebuilt from the field recording consent to marketing texts, which 1,240 of the 1,900 active customers have given; the rest receive the card only. Each salon manager is named as the reply owner for their own profile, with the owner covering holidays. Walking the path on a phone shows the card's link opens the profile rather than the review form, so the cards are reprinted before the first one is handed over.

Common mistakes

  • Asking only after the good days. Selective asking produces a picture the business cannot defend and the platform may remove.
  • A feedback form that quietly gates. The routing was a default in the tool, and nobody checked it.
  • Rewarding staff for review counts. The target turns into pressure on customers and an incentive the platform does not allow.
  • Asking before the product arrives. The customer has nothing to say yet, and says nothing.
  • A discount in the request. The customer feels negotiated with, and the record no longer shows the review was unconditional.
  • Treating customer content as the business's own. Reviews belong to the people who wrote them; moderation that trims the critical ones is suppression.
  • Rating markup for reviews nobody can see. Schema markup has to match what is on the page.
  • No reply owner. Requests produce reviews, and critical ones left unanswered undo the social proof the request was meant to build.

The checklists library holds the lists that sit beside this one, from the Google Business Profile setup checklist to the launch of an automated flow.

Frequently asked questions

Is it allowed to ask only customers we know were happy?

No. The site's reviews guides describe selective asking as something Google's help centre prohibits for business profiles and regulators treat as misleading, because it gives a picture of the business that a fair request would not. The same goes for a feedback form that sends pleased customers to the review platform and the rest to a private inbox. Ask every eligible customer in the same way and let the reviews be whatever they are. This is general direction, not legal advice.

Can we offer a discount or prize draw in return for a review?

It depends on where the review is left, and on some platforms the answer is simply no: the local reviews guide reads Google's help centre as prohibiting incentives for reviews on a business profile, and the app ratings tutorial says both app stores prohibit incentivising ratings. Where a store's own review system permits a reward, it has to be offered whatever the customer writes and the resulting reviews labelled as incentivised. Check each platform's rules before attaching any reward, and keep discounts out of the request itself.

Does this list cover replying to reviews?

Only to the extent of naming who replies on each platform and at each location before the requests start, because requests produce reviews that need an owner. How to write the replies, triage critical reviews and escalate is covered by the reviews and reply guides the list links to, not by this gate.

Terms used on this page

Frameworks

Where this page is used

Also related

Sources

  1. FTC business guidance — Federal Trade Commission
  2. FTC Endorsement Guides: What People Are Asking — Federal Trade Commission
  3. Competition and Markets Authority — GOV.UK
  4. Google Business Profile Help — Google Business Profile Help

Related