# Build a Win-Back Email Campaign That Knows When to Stop

Type: Playbook
Canonical: https://sendops.dev/guides/win-back-email-campaign/
Publisher: SendOps
Updated: 2026-10-04

A win-back campaign invites an inactive customer to return with a relevant reason. Define inactivity from the product’s normal usage pattern, send a small number of useful messages, and stop when the person comes back. Keep consent and suppression separate from audience membership.

## Journey at a glance

- **Who it helps:** Previously active customers who have stopped using the product.
- **What starts it:** Entry into an inactivity segment based on your normal usage cycle.
- **The sequence:** Reason to return → wait → check return activity → one useful follow-up.
- **When it stops:** A meaningful return, account closure, or the final follow-up.
- **What to measure:** Useful return actions and sustained activity, alongside unsubscribes and complaints.
- **Beyond email:** Ask your app to send a permissioned push reminder when a mobile return is the next useful action.

## Define what “inactive” means for your product

A daily collaboration tool and an annual reporting product have very different usage patterns. Choose an inactivity interval that represents a meaningful change for your customers, not an arbitrary benchmark.

Use recorded product activity or a known last-active attribute. Treat customers who never activated separately from customers who used the product and left: they may need different help. Decide explicitly how missing activity data affects segment membership.

- Entry: a previously active customer enters the inactive segment.
- Goal: a meaningful return action, not just an email open.
- Exit: return, account closure, or another state that makes the invitation irrelevant.

## Offer a reason to return

The first message should make the value easy to understand. A relevant product improvement, unfinished project, or useful example can provide a reason to reopen the product. “Something new for your next project” is one possible starting subject.

Give the person time, then check for a return action. If they are back, stop the win-back reminders or move to guidance that fits what they are doing now.

If they have not returned, a second message can offer help or a different useful reason. Decide in advance where the sequence ends. Endless reminders are not a retention strategy.

## Keep a large audience without emailing all of it

Segmenting lets you work with the relevant group while retaining the rest of your customer context. SendOps does not charge per contact, so storing customers who are not currently in a campaign does not create an additional contact fee.

Delivery still has a cost, and eligibility still matters. Review subscriptions, suppression, and sending reputation before activating a large inactive cohort. A contact’s presence in your database does not make them eligible for every message.

## Connect the return signal to the workflow

Bring the return event from your product into SendOps and use it as a branch or goal-exit condition. For identified website visitors, website activity can also provide a relevant signal; it should not be confused with recognizing every anonymous visitor.

Set re-entry deliberately so the same person does not repeatedly receive the same campaign. Use a shadow rehearsal with a fixed list before opening enrollment to the wider segment.

## Look for useful returns

Track the behavior the campaign is meant to encourage: returning to a project, completing a task, or resuming regular use. Inspect the timing of the return as well as the fact that it happened.

Watch complaint and unsubscribe patterns alongside return rates. If a message attracts attention but makes customers less willing to hear from you, revise the audience, message, or frequency.

## Common questions

### When should I send a win-back email?

After inactivity becomes meaningful for your product’s normal usage cycle. Use your own customer behavior to choose the interval and avoid treating every product like a daily-use app.

### How do I stop emails when a customer returns?

Record a return activity or update a contact attribute, then use that signal in a goal exit checked before subsequent workflow steps.

### Does an inactive contact cost more on SendOps?

SendOps has no per-contact fee. Your platform plan and AWS sending costs still apply, but retaining an inactive contact does not add a contact-storage charge.

## Sources and related reading

- [Build dynamic segments](https://sendops.dev/product/audience/)
- [Workflow testing](https://sendops.dev/guides/test-email-workflows/)
- [Pricing calculator](https://sendops.dev/pricing/)