Intern
What you actually do
Count the ask emails. Kill the duplicate. Timing and stop tests. You are not sourcing photos this week.
Library / Wire / Yotpo reviews are events. Do not ask on day zero and do not ask twice.
Review apps (Yotpo, Judge.me, Stamped) often send their own emails while Klaviyo also asks. Then a customer gets two requests before the box arrives. Wire reviews as: who asked (one owner), when (after delivery/use), what event Klaviyo can use for post-purchase, and suppression after they reviewed or refunded.
Review apps (Yotpo, Judge.me, Stamped) often send their own emails while Klaviyo also asks. Then a customer gets two requests before the box arrives. Wire reviews as: who asked (one owner), when (after delivery/use), what event Klaviyo can use for post-purchase, and suppression after they reviewed or refunded.
Pick the ask owner: Yotpo or Klaviyo, not both. If Yotpo asks, strip review-ask from Klaviyo post-purchase. If Klaviyo asks, turn off Yotpo email and keep Yotpo as the display widget.
Timing matches the product. Beauty and supplements need use days. Furniture needs delivery. Asking on Placed Order day is how you get 'hasn’t arrived' reviews.
Submitted reviews should become a Klaviyo event if you will segment promoters or ask for UGC. If the event never arrives, you will keep asking.
Star rating can route: 5-star optional GBP/social, 1–2 star to CS. That routing is a system. Dumping everyone to a public link is not.
Do not pause this work for a 'UGC campaign'. Double-ask is a trust leak now.
Intern
Count the ask emails. Kill the duplicate. Timing and stop tests. You are not sourcing photos this week.
Operator
One owner. Timing matches delivery/use. Suppress. Route low stars. Widgets can stay.
CEO
Reviews are a post-purchase job. Double-ask is a brand tax. One owner and a sane delay are the system.
Yotpo (or review app) request, review submitted event, Klaviyo profile, Placed Order, Fulfilled/Delivered, review_asked, review_submitted, Klaviyo post-purchase flow, app emails (on or off).
Delivered or use-window reached → one review ask from one system
Review submitted → Klaviyo event/property; post-purchase review emails stop; maybe a thank-you, not another ask
Refund/return → suppress asks
Photo/review content can power Klaviyo later; it is not a reason to double-send now
One sentence on the spec. Disable the other channel’s review emails. Widgets can stay.
Why: Two askers is the whole problem.
Done when: A test buyer gets one request, not two, in the window.
Trigger on Fulfilled/Delivered if you have it, or a delay that matches AOV/shipping. Supplements: use window. Not T+0 from Placed Order unless digital.
Why: Day-zero asks manufacture one-stars about shipping that are really a timing bug.
Done when: A test order does not get an ask before the wait.
Yotpo integration or webhook: review submitted, rating. Suppress further asks. Optional: 4–5 vs 1–2 paths.
Why: Without the event, suppression is a hope and CS never sees bombers.
Done when: A test review stops the ask and sets a property/event.
Refunded or return started → exit review flows / Yotpo suppress. Same as post-purchase generally.
Why: Asking a returner for a review is careless automation.
Done when: Refunded test is out.
If rating ≤2 and you can see it: CS task, not a 'share on Google' ask. High stars can get a secondary GBP ask once, not a loop.
Why: Public-first on unhappy is the GBP lesson in a DTC skin.
Done when: A 1-star test notifies CS. A 5-star does not create a CS panic.
Place a test order. See how many review emails would send from Yotpo and from Klaviyo. Turn one off. Set delay. Submit a review. Confirm stop. Refund a second order; confirm no ask. Do not build a UGC contest.
A UGC agency or a review-gated discount until one ask owner and delivery timing exist. Paying for content on a double-ask machine is paying to annoy buyers.
Yotpo default emails on. Klaviyo post-purchase includes a review ask on day 2. Package arrives day 5. Refunds still asked. No rating routing. That is two vendors and no journey.
One asker. Delay holds. Submit stops. Refund excluded. Low-star to CS if you wired it.
Then Klaviyo must not also ask. Conversion with double-ask is still a tax. Pick the winner, measure, but one owner.
After access is true, yes. Still one owner, still suppress after submit, still refunds out.
Yes, and then Klaviyo can own the ask. Widgets without an ask journey still need a trigger from orders.
This week
This week: one ask owner, timing delay, submit event, refund exclusion. Pause UGC campaigns that add a third ask.
A full calendar and an empty pipeline is two databases.
Read ↗A high score in a CSV is not a qualified opportunity.
Read ↗If the thank-you does not change the contact, the page was a brochure.
Read ↗If paid lives in Stripe and the opportunity is still open, reporting is theatre.
Read ↗Working notes
Score your Klaviyo and lifecycle system the way an operator would. Request the file. It arrives by email — not a public dump, not a drip of slogans.
Email and WhatsApp stay open. A call is for installing the system — not for a tour of tools.