How do you ask customers for reviews without breaking the rules?
By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
Run the free review audit See pricing · See a sample provenance report
Short answer
Ask every customer the same way, send every customer to the same public place, and offer nothing for the review or its content. Concretely: one short message, triggered by the completed transaction (not by how happy the customer looked), that thanks them, links to the public review page, and — separately, without routing — invites private feedback for problems. Capture the transaction reference in your request record so a returning review can be linked. Then audit monthly: gating and incentive counts on new imports are your proof the ask stayed clean.
What is a compliant review request?
A compliant review request is a solicitation designed so that the resulting review profile represents the real spread of experiences: universal (every customer is asked), unfiltered (no sentiment pre-screen before the public link), and unincentivised (no value connected to writing, posting or praising). It may still be warm, well-timed and well-written — compliance constrains the routing and the reward, not the courtesy.
Timing by transaction, not by mood
The single most effective compliance fix is changing the trigger. Mood-triggered asks — the server judges the table is delighted, the technician judges the repair went beautifully — import the staff member's guess about sentiment into the solicitation, and the profile quietly becomes the record of judged-delightful moments. Transaction-triggered asks — the invoice closes, the booking completes, the order delivers — treat every customer identically and capture, as a by-product, the exact reference that later links the review. You will collect some one-star reviews you would previously never have seen. That is not the system failing; that is the system finally describing your business, and it is what makes the four- and five-star reviews beside them worth money.
The workflow is the same on every plan, and the free tier does the complete job for one location: import by CSV upload or paste (up to 500 reviews per import on Free), read the full risk analysis and report, open a provenance certificate for any review, and publish the verified-experience widget. Pro ($29/month, 3 locations, 5,000 reviews per import) adds the full provenance chain detail, the evidence export, AI reply drafts and the reviewer-fraud graph. Agency ($79/month, 50,000 reviews per import) is the multi-location tier. Nothing about the free audit is a sample or a teaser — the report you get free is the real analysis of your real rows.
The private channel, placed correctly
Service recovery still matters, and a private route for problems is legitimate — placed beside the ask, not before it. 'If anything went wrong, tell us here and we will fix it' as an additional sentence, with the public link present in the same message, is service. The same sentence as a gate — problems go private, praise goes public — is suppression with good manners. Write the message once, have a second person read it specifically for routing ('does anything in this message steer by sentiment?'), and freeze it. Frozen wording can be trained, audited and defended; improvised wording by eleven staff members cannot be any of the three.
ReviewProof's import is forgiving about format and strict about meaning. Column names are matched flexibly — body, review or text for the review itself; rating or stars; reviewer, author or name; a verified flag and a transaction reference when you hold them. Rows are capped per import by plan (500 on Free, 5,000 on Pro, 50,000 on Agency), which is generous for a single location's history. What the importer will not do is upgrade a review's status: a row that arrives without a transaction link is analysed fully and still labelled UNLINKED, because the label is the product.
Mistakes that undo the work
Adding 'we would love a five-star review!' to the frozen message reintroduces sentiment-steering in the adjectives. Asking twice when the first ask gets no response, but only ever chasing the customers who seemed happy, rebuilds the filter the trigger was meant to remove. And printing the ask on materials given out selectively — in the bag only when the sale felt good — is mood-triggering in paper form.
A detail worth knowing before you start: ReviewProof analyses what you give it. The CSV importer reads reviewer, rating, title, body, date and source columns, plus a verified-transaction flag and a transaction reference when you have them. Reviews with a transaction link are marked verified; reviews without one are marked UNLINKED — kept in the audit, visible in the report, but excluded from the verified-experience widget, which only displays reviews that are both transaction-linked and in a kept or published state. That single rule is the difference between a widget that markets and a widget that proves.
Worked example: the ask that lowered a rating and raised the business
A fictional worked example, written to show the numbers and the decisions in practice.
A tour company replaced its guide-dependent asks ('our guides reminded happy guests') with one message sent on booking completion, reference included. Over the next season its average rating fell from 4.9 to 4.6 — and its ReviewProof audit showed gating and incentive counts of zero, a verified share above 80%, and a negative count that finally looked like a real operation's. The owner, braced for the rating fall to hurt, found the opposite in partner negotiations: two hotels cited the auditable profile — not the rating — when renewing allocations. The ask did not get worse at collecting reviews; it got honest at collecting them, and honesty turned out to be the asset.
Your five-action checklist
- Trigger the ask from the completed transaction, never from judged mood
- Use one frozen message for every customer, with the public link inside it
- Offer nothing — no discount, entry, gift or upgrade — connected to the review
- Place the private problem channel beside the ask, never in front of it
- Capture the transaction reference in the request record for later linking
Frequently asked questions
Can we ask for a five-star review specifically?
No — that steers sentiment, the core of gating and bought-sentiment violations. Ask for an honest review, of the actual experience, from everyone.
How soon after the transaction should we ask?
Promptly, while the experience is fresh — the trigger is the completed transaction itself. The exact hour matters far less than the universality.
Is a follow-up reminder allowed?
A single neutral reminder to everyone who was asked keeps the design clean. Chasing selectively — reminding only the delighted — rebuilds the filter.
How do we prove our ask is clean?
The audit proves it: gating and incentive counts of zero across monthly imports, plus the frozen message itself kept with your records.
Keep reading
Related guides from the ReviewProof library:
- How do you import reviews into ReviewProof by CSV?
- Paste import or file upload: which should you use?
- How do you read a ReviewProof risk report?
- How does the verified-experience widget decide what to show?
- How should you use AI-drafted replies to reviews?
- How do you write a review-request email that does not gate?
- How do you audit reviews across multiple locations?
Start with the tool itself: open the free audit desk, see how ReviewProof works, compare Free, Pro and Agency plans, inspect the sample provenance report, or browse all ReviewProof guides.