> ## 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](https://help.retainful.com/automations/overview.md#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

> [card] [Abandoned cart recovery](https://help.retainful.com/automations/abandoned-cart-recovery.md)
>
> Win back the \~70% of shoppers who start checkout and leave. The single highest-ROI automation in ecommerce.

> [card] [Welcome series](https://help.retainful.com/automations/use-cases/welcome-series.md)
>
> Greet new subscribers, introduce your brand, and turn the signup discount into a first order.

> [card] [Post-purchase & cross-sell](https://help.retainful.com/automations/use-cases/post-purchase.md)
>
> Thank new customers, set expectations, and recommend the perfect next product.

> [card] [Replenishment reminder](https://help.retainful.com/automations/use-cases/reorder-reminder.md)
>
> Nudge customers to reorder consumables right as they're about to run out.

> [card] [Win-back](https://help.retainful.com/automations/use-cases/win-back.md)
>
> Re-engage customers who used to buy but have gone quiet — before you lose them for good.

> [card] [Back in stock](https://help.retainful.com/automations/use-cases/back-in-stock.md)
>
> Tell waiting shoppers the moment a sold-out product returns, while intent is still high.

## How to choose

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

## 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](https://help.retainful.com/automations/triggers.md)).
2. **A short first delay**, then the first email.
3. **One or two follow-ups**, spaced a day or more apart.
4. **A [Binary](https://help.retainful.com/automations/steps.md#binary-ifelse) check** — has the goal happened (a purchase, a reorder)? If yes, exit; if no, continue.
5. **An optional [coupon](https://help.retainful.com/automations/coupons.md)** in the final message to close the loop.

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


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.