ShipPlays newsletter
E-commerce
What the system does
Draft abandoned-checkout recovery emails from the cart they left and an offer policy you wrote. No invented discount, timer, or stock count. A human sends.
Draft the next checkout-recovery emails from carts that were actually abandoned and from an offer policy you wrote down. The draft may name the items in that cart. It may not invent a discount, a deadline, or a stock level. A person reads every draft and is the one who sends.
How it runs
- Write the offer policy before you export a cart
- Export only checkouts you are allowed to email
- Separate a template from a one-off
- Draft from the cart and the policy
- Run the policy checker before anyone approves
- You approve the draft, then you turn the send on
- Once a week, tighten the policy from what you refused
The playbook has the setup in that order, the exact prompts, and the guardrails.
Tools
- Shopify (opens in a new tab). The abandoned-checkout list: item titles and the time they left. Copy those fields. The first version does not get a token that can email customers.
- Klaviyo (opens in a new tab). Where you schedule the message after you approve it. Shopify Email is the same job if that is what you already use. The flow stays off until a human turns on that draft.
- A spreadsheet (e.g. Google Sheets) (opens in a new tab). The offer policy and the queue: checkout id, items, whether a code you already created is allowed, and status (needs edit, approved, sent).
- Claude (opens in a new tab). Drafts from one cart, or from one cart shape you have already approved. It does not see card data, and it does not get the key that sends mail.
Expected results
- A queue of drafts tied to real checkout ids, each marked needs edit, approved, or sent.
- Subjects and bodies that name item titles from that cart.
- An offer line that matches a code or threshold you already wrote down, or no offer at all.
- A refused-claims note on each draft, and a weekly list of lines the next draft is not allowed to say.
A human sends. The agent does not get the API key, and the flow stays off until you turn that draft on.