> ## Documentation Index
> Fetch the complete documentation index at: https://help.retainful.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Automation use cases

> A library of proven, high-ROI automations — what each one is for, when to use it, and the sequence that works.

These are the automations worth setting up first. Each one targets a moment in the customer lifecycle where a timely email earns real revenue — and each has a [template](/automations/overview#start-from-a-template) so you can launch it in minutes and customize after.

Start with the first two; they cover the highest-value moments for almost every store.

## The essentials

<Columns cols={2}>
  <Card title="Abandoned cart recovery" icon="cart-shopping" href="/automations/abandoned-cart-recovery">
    Win back the \~70% of shoppers who start checkout and leave. The single highest-ROI automation in ecommerce.
  </Card>

  <Card title="Welcome series" icon="envelope-open-text" href="/automations/use-cases/welcome-series">
    Greet new subscribers, introduce your brand, and turn the signup discount into a first order.
  </Card>

  <Card title="Post-purchase & cross-sell" icon="heart" href="/automations/use-cases/post-purchase">
    Thank new customers, set expectations, and recommend the perfect next product.
  </Card>

  <Card title="Replenishment reminder" icon="arrows-rotate" href="/automations/use-cases/reorder-reminder">
    Nudge customers to reorder consumables right as they're about to run out.
  </Card>

  <Card title="Win-back" icon="user-clock" href="/automations/use-cases/win-back">
    Re-engage customers who used to buy but have gone quiet — before you lose them for good.
  </Card>

  <Card title="Back in stock" icon="bell" href="/automations/use-cases/back-in-stock">
    Tell waiting shoppers the moment a sold-out product returns, while intent is still high.
  </Card>
</Columns>

## How to choose

| If your goal is…                  | Run this                                                           | Trigger                 |
| --------------------------------- | ------------------------------------------------------------------ | ----------------------- |
| Recover almost-sales              | [Abandoned cart recovery](/automations/abandoned-cart-recovery)    | Checkout started        |
| Convert new subscribers           | [Welcome series](/automations/use-cases/welcome-series)            | Subscribed to list      |
| Increase repeat purchases         | [Post-purchase & cross-sell](/automations/use-cases/post-purchase) | Order placed            |
| Sell more consumables             | [Replenishment reminder](/automations/use-cases/reorder-reminder)  | Order placed            |
| Reactivate lapsed customers       | [Win-back](/automations/use-cases/win-back)                        | Order placed + cooldown |
| Recover demand for sold-out items | [Back in stock](/automations/use-cases/back-in-stock)              | Product back in stock   |

<Tip>
  You don't have to choose just one. These flows run side by side without colliding — a contact is only ever in one run of a given automation at a time, and cart recovery exits the moment someone buys.
</Tip>

## The shape they share

Most of these follow the same proven skeleton, which the templates already encode:

1. **Trigger** — the moment that matters (see [Triggers](/automations/triggers)).
2. **A short first delay**, then the first email.
3. **One or two follow-ups**, spaced a day or more apart.
4. **A [Binary](/automations/steps#binary-ifelse) check** — has the goal happened (a purchase, a reorder)? If yes, exit; if no, continue.
5. **An optional [coupon](/automations/coupons)** in the final message to close the loop.

Once a flow is live, give it a week and open its [analytics](/automations/analytics) to tune the first delay and subject line.