Review Outreach
Playbook
The get-reviews system as a weekly routine.
A one-time seeding blast to past customers plus an always-on post-delivery flow, sentiment-neutral and compliant. One engine feeds all three venues.
The Point
Reviews are the on-site authority signal AI weighs most, and Yoreh starts near zero. The fastest safe path to a citable base is a one-time seeding blast to your past customers, then an always-on post-delivery flow, both sentiment-neutral and compliant.
The Customer Review Strategy explains which venues and why. This document is how you actually run it: the seeding blast, the always-on flow, the timing, the templates, and the tracker. For platform rationale and the full template library, see the Customer Review Strategy.
Targets
Aim for the ~38 cold-start floor by week 6, and toward 80 with responses by week 12. I'd weight everything toward your jacket buyers. Three venues, one flow.
- Cold-start floor. Roughly 38 to 40 reviews is where a profile starts to register. Aim there by week 6, and toward 80 with responses by week 12.
- Jacket-weighted. I'd prioritize your smart-ring-jacket buyers. Recency and volume on the flagship line matter most for both Google stars and AI citation.
- Two venues, one flow. Judge.me, which you already run and which carries the
Review/AggregateRatingschema, and Trustpilot, added as a second-step ask on top. One engine feeds both; do not run separate campaigns.
You already have a review system running. Judge.me is installed and sending automated requests when orders are delivered, and Klaviyo post-purchase flows exist alongside it. An earlier version of this playbook read as though you were starting from nothing.
So Play 2 below is not "switch on automation", it is audit the two systems, pick one owner for the review ask, and turn the other one's ask off. The full merged sequence is specified in the Customer Review Strategy, section 05. Run that audit before the seeding blast, or the blast lands on top of an automation that is already emailing the same people.
SMS is out entirely. Yoreh collects no SMS marketing consent, so every SMS element has been removed from both documents.
Play 1: The Seeding Blast
Convert your standing goodwill into a review base on day one. Segment your past-customer list, jacket buyers first, and drip a single sentiment-neutral ask across the first two weeks.
- Export your past-customer list from Shopify (all fulfilled orders). Segment: jacket buyers first, then everyone else. Exclude anyone the existing automation has already asked, which is what the Play 2 audit tells you.
- Send a single, sentiment-neutral request per segment (template R1 below). Space your sends to respect the app's free-tier invite cap (for example 50/month) and deliverability. Drip over the first two weeks rather than one blast.
- Ask for the review on the on-site app; add a secondary Google ask for your most engaged segment.
- Do not offer a reward for a positive review. A small thank-you (a discount on next order) offered to all reviewers regardless of rating is allowed; a reward tied to a 5-star is not.
Play 2: The Always-On Flow
Automate one post-purchase request timed to real usage, not order date. One ask, one reminder, then stop. Add a printed QR insert to every shipment.
- Audit before you automate. List what Judge.me and Klaviyo each send today, choose one owner for the review ask, and switch the other off. Send a test order all the way through to confirm only one email arrives.
- Check the surviving request is timed to real usage, not to order date. Some Yoreh pieces are made to order (14 to 21 day dispatch, 5 to 7 day delivery), so the request should fire about 7 to 10 days after delivery, once the piece has been worn. A trigger set on order date will reach people whose piece is still in transit.
- One automated ask, one reminder 5 to 7 days later, then stop. Two touches, no more. Email only, since there is no SMS consent to send against.
- Add a printed insert card with a QR code in every shipment (template R4), the highest-converting offline nudge.
- Route unhappy responses to
hello@yoreh.cofor a private fix before they post. Standard and compliant, as long as every customer is still invited to review publicly.
Compliance Guardrails
Sentiment-neutral only, verified purchasers only, and honor every opt-out. These are the non-negotiables that keep the whole system safe.
- Rule 01Sentiment-neutral only. Ask every customer for an honest review. Never ask for a positive one, and never filter who gets invited by predicted rating.
- Rule 02EU Omnibus / verified purchase. Only invite real purchasers, label reviews as verified, and never edit or suppress genuine reviews.
- Rule 03Email. Clear sender, one-click unsubscribe, honor opt-outs.
- Rule 04SMS. Not in scope. Yoreh collects no SMS marketing consent, so there is no compliant list. Email carries the whole sequence.
Core Templates
The full library of six templates lives in the Customer Review Strategy. These three do most of the work: the seeding request, the post-delivery request, and the Google follow-up.
[First name],
You ordered [product] from us a while back and we would genuinely like to know how it is wearing.
If you have two minutes, an honest review helps other people find us and tells us what to make next.
[ Leave a review ]
Thank you for supporting a small studio.
Fin, founder, Yoreh.
[First name],
Now that you have had your [product] for a week or so, how is it?
An honest review, good or bad, genuinely helps.
[ Leave a review ]
Any issue at all, just reply to this email and we will make it right.
R4 (the printed QR insert) and the remaining library templates live in the Customer Review Strategy.
Weekly Rhythm
Four moves a week. Top up invites under the cap, respond to every review within 48 hours, handle complaints same-day, and update the tracker.
- Send. Top up your invites to stay under the app cap; process any new past-customer segment.
- Respond. This one is yours. You said you will handle review replies yourself, which is the right call: replies in the founder's voice are the thing a faceless brand cannot copy. Every new review within 48 hours, positive and negative. Responses are themselves a ranking and trust signal.
- Route. Handle any private complaint the same day.
- Log. Update the tracker.
Tracker
One row per week, six columns. Watch the running total against the ~38 floor by week 6 and ~80 by week 12.
| Week | Invites sent | New reviews | Venue | Running total | Notes |
|---|---|---|---|---|---|
| 1 | app / Google / TP | seeding: jacket segment |
Target line to watch: running total vs the ~38 floor by week 6, ~80 by week 12.
Hand-Off Note
There is no app choice to make and no billing to set up: Judge.me is already
installed and running on your store, and the Review /
AggregateRating schema ships with the theme work. What this playbook does depend
on is the audit in Play 2, mapping the existing Judge.me and Klaviyo sends
and reducing them to one ask. Do that before the seeding blast in Play 1, not after.
Two things you have already taken on: the printed QR insert card in every shipment, and review replies in your own voice within 48 hours. Both stay with you by design.