A neutral request identifies your store, gives the customer a useful review link, and welcomes the experience they actually had. Adapt these illustrative templates to a message you control.
Make the request easy to understand
Identify who is asking, which experience you mean, and where the link leads. Use the recognized store name and ask one short question instead of supplying desirable adjectives. You can mention delivery, communication, or service without suggesting the conclusion.
Choose recipients consistently and allow time to experience the purchase. Do not use a satisfaction question to show the review link only to happy customers. Offer normal support without requiring someone to leave, edit, or delete a review.
After an order has arrived
Use this example in an authorized follow-up after the customer can receive and assess the order. Replace bracketed fields before sending. If delivery is uncertain, check it instead of assuming arrival. Keep unnecessary personal order details out.
Illustrative email: Subject: How was your experience with [Store]? Hi [Name], thanks for shopping with [Store]. We would like to hear about your experience with the order, including anything we could improve. Please share your honest feedback on ReviewList: [Your store review link]. Positive and negative experiences are equally welcome. [Store support contact, if needed]
After support or a repeat purchase
For support feedback, describe the interaction without claiming the issue was resolved unless you know that it was. For repeat customers, ask about their current experience rather than collecting a second copy of the same story. ReviewList allows one current direct review per business; authors can edit their review as their experience develops, with updates returning to moderation.
Illustrative support follow-up: Thank you for contacting [Store]. We would value your honest account of the service you received and what happened next. You can share your experience here: [Review link]. Illustrative repeat-customer follow-up: Thank you for shopping with [Store] again. If you would like to share how your experience has developed, write or update your review here: [Review link].
Preview the route before sending
A shared customer review link belongs in messages you send yourself. A ReviewList campaign uses its own neutral invitation message and a private recipient link; inspect the workspace preview instead of assuming these templates replace the campaign’s built-in wording. Never publish a customer’s private campaign link in a newsletter, packaging insert, or public page.
Test the destination and remove unreplaced placeholders. Customers need an account, with moderation before publication. A request neither verifies purchase nor guarantees a review. Check accuracy and clarity first, then use actual delivery and submission reporting to improve the workflow.
Request copy review
| Element | Check before sending |
|---|---|
| Sender | The store name and contact route are recognizable. |
| Experience | The interaction described really happened; delivery or resolution is not assumed. |
| Wording | Honest feedback is welcome without a suggested rating or conditional reward. |
| Link | A public store link for your own message; a private link only for its campaign recipient. |
| Placeholders | Every example field is replaced and the destination is checked. |
Questions and answers
Can I customize ReviewList’s campaign email with this copy?
These examples are for messages you control. ReviewList campaigns show the built-in invitation preview in your workspace. Check that actual preview before sending.
Can I offer a reward for a five-star review?
No. ReviewList prohibits rewards conditional on sentiment and requests that require a positive rating. Invite authentic customers fairly and welcome their actual experience.
Can the invitation say the customer is purchase verified?
An invitation does not establish purchase verification. Do not attach that claim to the request. ReviewList’s verification labels have separate requirements.
Sources and scope
ReviewList publishes this guide to explain a practical research or review workflow. Linked sources support the specific external principles discussed; they are not endorsements of ReviewList. Current merchant terms and the details of a particular order may differ.
Editorial date: Oct 13, 2026. Suggest a factual correction.