ReviewProof ⚖

How do you write a review-request email that does not gate?

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

A non-gating request email has one public review link, offered to every recipient on identical terms, with no pre-question about satisfaction, no star widget that reveals the link only for high scores, and no offer attached. A private 'tell us about a problem' link may appear in the same email, after the public link, framed as service rather than as the destination for unhappy customers. The email is triggered by the transaction for the whole cohort — buyers, all of them, including the ones whose delivery went wrong.

What is a review-request email?

A review-request email is the post-transaction message inviting a customer to leave a public review. It becomes gating through design details rather than intent: a satisfaction question at the top whose answers route differently, a thumbs-up/thumbs-down fork, embedded stars that deep-link only the happy path, or a send list filtered by a service score. Each detail is individually explainable; together they determine whose voice reaches the public record, which is the definition of the problem.

Anatomy of the clean email, line by line

Subject: a thanks, not a request for a favour — the favour framing primes obligation, and obligation distorts reviews too. Opening: one sentence naming the transaction ('your order of 12 May') — this also quietly aligns the customer's memory with the reference your system will link. The ask: 'Would you leave an honest review?' with the single public link. The service line, after the ask: 'If anything was wrong, reply to this email and we will put it right' — a reply, note, not a diversion form, keeping the conversation in the same channel as the request. Close: thanks again, a human name, no incentive, no deadline pressure, no 'five stars' anywhere. Short is not a style preference here; every extra persuasive sentence is another chance to steer.

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 send list is part of the wording

Email gating most often lives in the list, not the text. Lists filtered by 'completed without complaint', by a delivery scan, by an internal satisfaction score — each silently removes the customers most likely to write the reviews the public record most needs for credibility. Build the cohort by transaction alone: everyone whose order completed in the period, minus only the purely operational exclusions (no email address, a transaction that was fully refunded and annulled before use — and even those, apply uniformly and note the rule in your records). Then keep the rule with the frozen email. An auditor — or your future self — should be able to see the cohort rule, the message, and the audit counts, and watch the three agree.

After the first audit, the habit that matters is cadence. Re-import on a regular rhythm — monthly suits most locations — so new reviews enter the provenance record while the underlying transactions are still easy to match. Each import logs provenance events, moderation starts from kept (no suppression), and the certificate for any review shows its chain: imported, transaction-linked or not, analysed with its signals, moderated with its decision. A record built gradually like this is worth far more in a dispute than one assembled in a panic the week the dispute arrives.

Mistakes that undo the work

A/B-testing request emails for rating lift is optimisation aimed precisely at the steering effect — test open rates and clarity if you must test, never sentiment outcomes. Suppressing sends to customers who complained to support is list-gating in its purest form. And adding 'leave us a review on Google' links only in the happy-path branch of a post-delivery survey does not launder the gate through a survey tool.

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: a webshop rewrites one email and its list

A fictional worked example, written to show the numbers and the decisions in practice.

An online store's old flow sent a 'How did we do?' email with a star selector: four and five stars revealed the public link; one to three opened a service form. Its imported reviews showed the fingerprint — gating-phrase echoes in review text and a negative share under 2%. The rewrite removed the selector entirely: one email, one public link, service by reply, sent to every completed order in the weekly cohort. The first month's import showed a negative share of 9% — uncomfortable reading that the owner described, correctly, as the sound of the record becoming true. Her average settled lower; her verified widget, linking those very reviews to orders, became the page her wholesale enquiries were sent to.

Your five-action checklist

  1. Remove any satisfaction question, star selector or thumbs fork before the public link
  2. Write one email: transaction named, honest-review ask, one public link, service by reply
  3. Offer nothing in the email connected to the review or its content
  4. Build the send cohort by transaction alone and write the cohort rule down
  5. Keep the frozen email and cohort rule with each month's audit records

Frequently asked questions

Can the email include a private feedback link at all?

Yes, placed after the public ask and framed as service — ideally as a simple reply route. It must not be the routed destination for dissatisfied customers.

Is 'How did we do?' as a subject line gating?

The subject alone is not; a satisfaction question whose answers determine who receives the public link is. Judge the flow, not the phrase.

Should refunded customers get the email?

Apply one written rule uniformly — for example excluding orders annulled before use, including everyone else, complained or not — and keep the rule with your records.

How can we tell if our old emails gated?

The audit shows it: gating-language echoes in review text and an implausibly low negative share across the imported profile.

Keep reading

Related guides from the ReviewProof library:

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.