A win-back campaign should solve a reason for inactivity, not simply send a bigger coupon to every old customer. This playbook defines the audience, sequence, economics and stopping rules.
Define inactivity relative to the buying cycle
A customer is not lapsed simply because a calendar says 90 days. A replacement part, a seasonal item and a monthly consumable have different normal intervals. Estimate the expected repeat window by product or segment, then define inactivity as a meaningful delay beyond that window.
WooCommerce’s example uses minimum and maximum days since purchase to identify inactive customers. That is a useful starting mechanism, but the values must come from your data. This campaign sits inside the broader customer-retention system and should not overlap with a normal replenishment reminder or a recent abandoned-cart recovery.
| Customer state | Example rule | Best treatment |
|---|---|---|
| Within normal cycle | Not yet due to repurchase | Education or service only |
| Approaching expected repeat | Near usual interval | Replenishment reminder |
| Meaningfully late | Past segment threshold | Win-back candidate |
| Inactive beyond useful contact | Very old or invalid context | Preference check or suppression |
Diagnose why customers may not have returned
A generic “we miss you” message assumes the customer forgot. Inactivity may instead come from excess product life, poor fit, out-of-stock items, service failure, changed need, price pressure or channel migration. Use order history, support reasons, returns and feedback to create a small set of plausible causes.
- One-time or gift buyers may never have had a repeat need.
- Customers who complained need resolution, not a promotion.
- Buyers of a discontinued SKU need a truthful replacement path.
- Heavy discounters may be inactive only because the previous offer ended.
- Customers who moved to another channel may still be active but invisible in one dataset.
Connect recurring reasons to the customer review and feedback system. A campaign should not mask a product or service defect.
Segment by relationship, not just last-purchase date
Start with a few actionable groups. One-time buyers need reassurance and education. Former repeat buyers may respond to convenience, availability or recognition. High-return customers require a different decision from high-contribution customers. Segment only when the message or offer will genuinely change.
| Segment | Likely question | Message angle | Exclusion check |
|---|---|---|---|
| One-time buyer | Was the first purchase useful? | Usage help and relevant next product | Return or complaint unresolved |
| Former repeat buyer | What changed? | Availability, convenience or improvement | Already reordered elsewhere in system |
| High-value inactive | Is the relationship still relevant? | Personal service and preference check | Sensitive issue needs human owner |
| Offer-only buyer | Would they buy without a deep discount? | Value and product fit before incentive | Unprofitable historical contribution |
The customer segmentation guide provides a wider framework, but the win-back audience should stay small enough to explain and audit.
Build a short sequence with a different job for each message
A useful sequence progresses from relevance to a reason to return and then to a respectful close. Repeating the same coupon three times is not a sequence. Each message should add information or choice, and all later messages must be suppressed after purchase, reply or opt-out.
| Touch | Job | Example angle | Stop condition |
|---|---|---|---|
| 1: Relevance | Reconnect purchase context | How to get more value from the product | Purchase, reply or opt-out |
| 2: Reason to return | Present a meaningful change | Restock, improvement or complementary item | Purchase, reply or opt-out |
| 3: Preference or close | Ask what is useful | Choose frequency, give feedback or pause | Any response or sequence end |
Use a direct product or category link, not a busy home page. A customer who needs help should be routed to a person rather than forced through promotional automation.
Set the win-back offer from incremental contribution
An incentive is a cost of reactivation. Calculate whether the incremental order contribution can fund the discount, message cost and likely returns. Do not compare the offer only with the customer’s lifetime revenue; the next order must still make commercial sense.
Incremental win-back contribution = reactivated order contribution − incentive − campaign cost − expected return cost. Compare this with a holdout group or historical baseline to estimate how many orders would have happened anyway. Use the unit economics guide before approving a broad discount.
| Offer | Potential benefit | Primary risk | Best control |
|---|---|---|---|
| No discount | Tests true relevance | Lower initial response | Strong product-specific reason |
| Fixed credit | Easy customer value | Consumes margin on small baskets | Minimum contribution threshold |
| Percentage discount | Scales with order | Large cost on high-value carts | Discount cap |
| Service benefit | Protects price integrity | Operational workload | Capacity and eligibility rule |
Use the right channel and respect customer choice
A historic order is not universal permission to contact a person forever. Check current channel consent, message purpose and opt-out state. WhatsApp policy requires the customer’s number and opt-in permission, compliance with applicable law and prompt respect for requests to stop.
Link WhatsApp execution to the WhatsApp selling guide. Keep email, SMS and WhatsApp permissions separate where required. The final message can offer a preference choice, but it should not pressure a customer to remain subscribed.
| Control | Required decision | Evidence |
|---|---|---|
| Eligibility | Why this person is a win-back candidate | Segment and last qualifying order |
| Permission | Which channel and purpose are allowed | Consent record |
| Frequency | How many touches are permitted | Sequence rule |
| Suppression | What stops all later sends | Purchase, reply, opt-out or complaint |
Automate the rule and keep exceptions human
The automation should identify the audience, apply exclusions, schedule touches and record outcomes. Humans should own complaints, product suitability, sensitive customer history and manual credits. Every branch needs an owner and a maximum response time.
- Calculate the lapsed threshold by product or segment.
- Build the eligible audience and remove exclusions.
- Assign the approved sequence and channel permission.
- Suppress immediately after purchase, response or opt-out.
- Route service issues to a human queue.
- Record reactivation window, contribution and reason codes.
Apply the controls from the marketing automation guide. Never upload an old contact list to a new tool without reconciling consent and opt-outs.
Use a reactivation window and a credible baseline
Choose the conversion event and time window before launch. A purchase within 14 or 30 days may be appropriate depending on the buying cycle. Count revenue and contribution separately. A high response rate can still be unprofitable if the incentive, returns or service effort is heavy.
| Metric | Definition | Interpretation |
|---|---|---|
| Eligible audience | Customers after all exclusions | True denominator |
| Reactivation rate | Eligible customers who buy in window ÷ eligible customers | Observed response |
| Incremental lift | Campaign reactivation minus baseline or holdout | Likely campaign effect |
| Contribution per eligible customer | Net campaign contribution ÷ eligible customers | Economic efficiency |
| Opt-out and complaint rate | Negative outcomes ÷ delivered messages | Trust and targeting quality |
Review by segment. One group may justify expansion while another should be suppressed or served differently.
Run a controlled win-back pilot
Choose one segment with a clear lapsed definition and a known reason to return. Manually inspect a sample of records, approve the sequence and hold back a comparable group when the audience is large enough. Launch in a volume the support team can handle.
At the end of the window, classify results as purchase, reply, service issue, opt-out, no response or bad data. Carry customers who need ongoing follow-up into a normal service or retention path. Do not keep them in a permanent win-back loop. The objective is a renewed useful relationship, not repeated pressure.
Frequently asked questions
What is a customer win-back campaign?
A customer win-back campaign is a short sequence designed to re-engage a previous buyer who has not purchased within the expected cycle. It should address a plausible reason for inactivity and use clear stopping rules.
When is a customer considered lapsed?
The right threshold depends on the normal repurchase interval for the product and customer segment. A useful rule is based on a multiple of the observed cycle rather than one fixed number of days for the entire catalogue.
How many messages should a win-back campaign include?
A small product business can start with two or three purposeful messages: relevance or education, a reason to return, and a final preference or feedback request. Stop after purchase, opt-out or the sequence limit.
Should every win-back campaign use a discount?
No. Product improvement, availability, education, service recovery or a relevant new option may be stronger reasons to return. Use an incentive only when the expected incremental contribution can fund it.
Which customers should be excluded from win-back campaigns?
Exclude recent purchasers, people who opted out, customers with unresolved complaints, refunded or fraudulent orders, invalid contacts and segments for which the message is not relevant.
How do I measure a win-back campaign?
Use an eligible audience, holdout where practical, reactivation window, contribution after incentive, opt-out rate and complaint rate. Do not attribute every later purchase to the campaign.
Leave a Reply