Abandoned cart
When to use it
Section titled “When to use it”- Your store sends an event when checkout starts and another when an order is placed.
- Most of your shoppers give an email or phone number before checkout.
Where the data comes from
Section titled “Where the data comes from”| How | What |
|---|---|
| Events from your app or website (needs a developer) | Your store sends checkout and order events (a plugin, the Web SDK, or a webhook from your platform). |
What it sets up
Section titled “What it sets up”| Kind | Name | What it does | Lands |
|---|---|---|---|
| Template | Your cart is waiting (email) | "You left something behind" email with a button back to the cart. | Ready |
| Template | Your cart is waiting (SMS) | Short SMS the next day. | Ready |
| Follow-up | Abandoned cart | Email, then SMS; exits on an order. | Off |
The questions it asks
Section titled “The questions it asks”| # | Question | Default | Fills in |
|---|---|---|---|
| 1 | What's your shop called? | none, must answer | org_name |
| 2 | Which event means checkout started? Its properties should include the cart link and items. | Checkout Started | checkout_event |
| 3 | Which event means the order went through? | Order Completed | order_event |
| 4 | Send an SMS the next day as well? | Yes | send_sms |
| 5 | How long after checkout starts should the email go? | 1h | first_delay |
Other settings
Section titled “Other settings”These have defaults. Change any that don’t fit.
| Setting | Default | Key |
|---|---|---|
| Sender address | ‹workspace default_sender› | email_from |
| Event property with the cart link | cart_url | cart_url_property |
| Greeting when a first name is missing | there | greeting_fallback |
Timings
Section titled “Timings”- Email 1h after Checkout Started; SMS 1 day after that, if switched on.
- Stops as soon as Order Completed arrives. At most one sequence per shopper per 3 days.
Channels
Section titled “Channels”| Channel | Needed for | Before it can send |
|---|---|---|
| The first reminder | A verified sending domain for ‹workspace default_sender›. | |
| sms | The second reminder (optional) | An SMS provider, or Origamy managed SMS after business verification (KYC). |
What you need to do
Section titled “What you need to do”- Send Checkout Started with properties cart_url (a link that restores the cart), item_names and total, and Order Completed when an order is placed.
- Verify the sending domain; for SMS, connect a provider or finish business verification.
- Switch the follow-up on and test it with your own email and phone.
This playbook is synthesized: no customer has run it with us yet. If you build it, tell us what you changed, and we’ll replace it with the real version.
Copilot eval
Section titled “Copilot eval”The request used to test the copilot on this playbook (a live eval):
When someone starts checkout on our store and doesn't buy, email them an hour later with a link back to their cart, then text them the next day. Stop as soon as they place the order.
It passes when every piece is a valid draft and everything lands off, with at least: workflow, message_template.