sample-reviews/*-review.md, with the search string printed in Sources.Win-back campaign· Conversational marketing
Win-Back Campaign — What It Is, and Why It Works Differently in Chat Than in Email
Quick answer: A win-back campaign targets customers who have gone quiet: they bought, or subscribed, or messaged, and then stopped for longer than their normal cycle. The business reaches out first, usually with a reason to come back (a reminder of what they used, an offer, a question about why they left) and usually in a sequence that ends after a few attempts. The term comes from email marketing, where a send costs nothing and the only constraint is the unsubscribe link. Chat channels invert that. On WhatsApp, a message to a customer who has not written to you in the last 24 hours has to be a message template, and a win-back is a marketing template by definition. Meta's own page on the subject, read 12 September 2026, says WhatsApp "may limit the number of marketing template messages a WhatsApp user receives from any business in a given period of time," that the limit "adapts automatically over time based on a person's recent engagement levels," and that WhatsApp "does not currently deliver marketing template messages to WhatsApp users with United States phone numbers." On Messenger, the message tags that used to let a bot speak first were never allowed to carry promotion and three of them stopped working in 2026 (the dates are in Sources). Meta's replacement path is utility templates or the Marketing Messages API; for a win-back, which is promotional, that means Marketing Messages, which is paid through an ad account and, per Manychat's help article of 27 August 2026, "currently in beta" in "a limited number of countries," which our Messenger tutorial lists as 20 markets including the US and excluding the EU, the UK and Canada. On a website widget there is no first message to send: the bot is a trigger that fires when the customer comes back on their own.
So a chat win-back is less a campaign you send and more a set of permissions you need first, a rationed send once you have them, and a stop rule that protects the sender number. The chatbot retention playbook covers the programme around it: which customers count as lapsed, which trigger catches them, and in what order to try the channels. This entry owns the message itself and the rules that constrain it.
Win-back, re-engagement, drip, abandoned cart
Four terms get used for each other, and the difference decides which channel rules apply and which message you write.
| Term | Who receives it | Who speaks first | Owned by |
|---|---|---|---|
| Win-back campaign | A customer who bought or subscribed and has stopped for longer than their normal cycle | The business | this entry |
| Re-engagement campaign | A subscriber or contact who stopped opening or replying, whether or not they ever bought | The business | chatbot retention playbook |
| Drip campaign | Anyone entered into a timed sequence, lapsed or not | The business, on a schedule | drip campaign |
| Abandoned cart recovery | A shopper who added to cart in the last hours and did not pay | The business, within a short window | abandoned cart recovery |
The practical test is the cycle. A customer who buys coffee beans monthly and has not bought in ten weeks is lapsed; a customer who buys a mattress every eight years and has not bought in ten weeks is not. Our editorial rule is to define lapsed as two to three times the customer's own median gap between purchases, computed per segment if the segments differ, and never as a single company-wide number of days. Re-engagement uses the same message shapes but a looser entry condition (stopped reading, not stopped buying), which is why it belongs to the playbook and not here.
What each channel lets you send to a lapsed customer
The channel rules below are the reason a chat win-back needs planning that an email win-back does not.
| Channel | What the first message has to be | Constraint (read 12 September 2026) |
|---|---|---|
| An approved marketing template, because the customer has not written in the last 24 hours | Meta's per-user marketing limit: delivered marketing templates count against a per-recipient cap that "adapts automatically" to the person's read rate and inbox volume; a reply "starts a 24-hour customer service window" inside which marketing messages "do not count towards the limit"; a message blocked by the cap fails with error code 131049 and Meta says to "wait at least 24 hours before resending"; the limit is not active for businesses or users in the EEA, UK, Japan or South Korea; and marketing templates are not delivered to US phone numbers (Meta's page does not address in-window delivery) | |
| Messenger | A Marketing Message to a contact on an opted-in Messenger List | Per Manychat's article: paid, charged "through the business's credit card connected to the Ad account(s)"; campaigns run on a daily or lifetime budget "for 30 days"; "currently in beta" and rolled out "in a limited number of countries" (20 markets including the US, not the EU, UK or Canada, per our Messenger tutorial, which also records Meta's caps: one marketing message per user per day and frequency limits enforced since 10 April 2026). Recurring Notifications, the free predecessor, was retired in early 2026 (Manychat: Meta "will begin sunsetting globally on January 12, 2026"; Meta's own FAQ gives two dates, and the product was kept in the EU, UK, Australia, Japan and Korea for existing integrations). Message tags "cannot be used for promotional content" and three of them stopped working in 2026 |
| Nothing automated outside the 24-hour window, for most accounts; a human agent has 7 days | Manychat: the Human Agent tag "works on both Instagram and Messenger" for up to 7 days after the last interaction, but "Automated messages are not allowed during the 7-day window"; "in February 2024, Meta paused allowlisting for the Instagram DM List Beta"; only accounts approved before the pause retain it | |
| Website chat (Tidio) | No first message; a trigger that fires when the customer returns | Tidio's Visitor returns to the site trigger "starts when the visitor returns to your site (is not a new visitor)"; the visitor hasn't contacted you for some time trigger counts "a specified time (counted in days)" and "will work only if the visitor has left you an email address" |
| In-app or email (Intercom) | A Series entered by rule | Intercom's Series: an Entry Rules block with "the filters a customer must match to enter," wait blocks ("Send an email → Wait for 3 days → Send a follow up chat message"), exit rules under which a customer who matches "will exit the series completely, and cannot re-enter," and a goal with a time limit after which a match "won't be counted" |
| SMS | A message to a number that opted in | Consent and STOP handling; see the SMS chatbot setup guide |
Two consequences follow. First, on WhatsApp the win-back competes with every other business's marketing for the same per-recipient allowance, so the customer who has not read your last three templates is exactly the customer Meta is most likely to withhold the fourth from; the WhatsApp broadcast guide covers what that does to a quality rating. Second, the cheapest win-back is the one where the customer speaks first, because a reply opens a service window and the sequence inside it is free of template rules: a utility message the customer expects (a delivery note, a renewal reminder) that ends with a question is often a better opener than a discount, and the lead nurturing automation guide works through the economics of metered channels in detail.
What a win-back message has to say
Three properties, drawn from the constraints above; they are our rules, not vendor requirements.
One reason, stated. The customer stopped for a reason, and the message either names a plausible one ("you last ordered in May; the blend you bought is back in stock") or asks ("was it the price, the delivery, or something else?" with three buttons). A template that says only "we miss you" spends a rationed send on nothing.
An answer that is cheap to give. On WhatsApp and Messenger the whole point is to get a reply, because a reply opens the 24-hour window. Buttons, not a request to type; a question, not an announcement. The quick reply entry has the per-channel button limits.
A stop. A win-back that keeps sending to a customer who does not answer is the block report that costs the number its rating. Our rule is two business-initiated attempts at most, a fortnight or more apart, then nothing until the customer moves; on WhatsApp, a 131049 error is not a retry, it is a stop for that recipient. Intercom builds the same idea in as an exit rule and Tidio as a per-person trigger limit ("decide how many times they should be fired per person").
How you know it worked
The win-back metrics are the retention metrics with a denominator restricted to the lapsed segment, and the chatbot metrics guide has the definitions in full.
- Reactivation rate: lapsed customers who bought again within a set window after the campaign, divided by lapsed customers sent to. Measure against a holdout group that received nothing, or the campaign gets credit for customers who would have come back anyway.
- Reply rate: on WhatsApp and Messenger this is the metric that matters first, because a reply is the permission for everything that follows.
- Opt-out and block rate: the cost. On WhatsApp blocks feed the quality rating; on a Messenger List an opt-out removes the permission to send at all.
- Revenue per send: reactivated revenue divided by messages sent, which is what a metered channel makes you compute anyway.
Blip's review captured a 24-hour recurrence rate (contacts who interacted twice or more in 24 hours) that our Manychat and Tidio reviews did not find in those platforms' default dashboards; it is a re-engagement measure, not a win-back one.
What our fifteen reviews record about win-backs
Nothing under that name. Searched 12 September 2026, case-insensitively, across the fifteen files matched by sample-reviews/*-review.md: win-back|winback|win back appears in 0, and the nearest matches (re-engag in 4 files, churn in 2) mean the bot resuming after a human handoff, Blip's recurrence metric, or Intercom's "churn risk" workflow event rather than a lapsed-customer send; the retention playbook prints the full tally. None of the fifteen protocols sent a marketing template to a lapsed contact and measured the result; that is a gap in the protocol, recorded here, not a finding that the platforms lack the feature. Corrections to editorial@chatbotscape.com.
Related terms
- Drip campaign — the timed sequence a win-back usually runs as, and why chat drips differ from email.
- Abandoned cart recovery — the short-window cousin, with its own channel rules.
- Chatbot broadcast — the one-to-many send that a win-back should not be.
- WhatsApp message template — the artefact a WhatsApp win-back has to be.
- Lead nurturing — the pre-purchase sequence, as distinct from the post-lapse one.
- Net Promoter Score — the survey that often tells you who is about to lapse.
FAQ
What is a win-back campaign?
A message or short sequence sent to a customer who used to buy or subscribe and has stopped for longer than their normal cycle, with the aim of bringing them back. It differs from a re-engagement campaign (aimed at anyone who stopped reading, whether or not they bought), a drip (any timed sequence) and abandoned-cart recovery (a shopper who did not pay in the last hours).
Can a chatbot send a win-back message on WhatsApp?
Only as an approved marketing template, because the customer has not written in the last 24 hours. Meta rations marketing templates per recipient with a limit that adapts to how much marketing the person reads, returns error 131049 when a send is withheld, and does not deliver marketing templates to US phone numbers (all read 12 September 2026; Meta's page does not address the case of an open service window). A customer's reply opens a 24-hour window inside which the rest of the sequence is free of those rules.
Can a chatbot send a win-back message on Messenger?
Through Marketing Messages, which per Manychat's 27 August 2026 article is a paid product billed to an ad account, in beta in a limited number of countries (20 markets including the US, excluding the EU, UK and Canada, per our Messenger tutorial), and requires the contact to have opted in to a Messenger List. Message tags were never allowed to carry promotion and three of them stopped working in 2026; Recurring Notifications, the free predecessor, was retired in early 2026 except for existing integrations in the EU, UK, Australia, Japan and Korea.
How many win-back messages should I send?
Our editorial rule is two business-initiated attempts at most, a fortnight or more apart, then nothing until the customer moves. Every unanswered message on a metered channel is a block risk, and on WhatsApp a withheld send is a signal to stop, not to retry.
How do I measure a win-back campaign?
Reactivation rate against a holdout group, reply rate (the permission metric on chat channels), opt-out and block rate (the cost), and revenue per send. The lapsed segment is the denominator for all four.
Sources
- Meta for Developers, WhatsApp Business Platform, Per-user marketing template message limits (developers.facebook.com/documentation/business-messaging/whatsapp/templates/marketing-templates/per-user-limits, undated on the page), read 12 September 2026: "WhatsApp may limit the number of marketing template messages a WhatsApp user receives from any business in a given period of time when they are less likely to be receptive and engage with those messages"; "The per-user marketing limit adapts automatically over time based on a person's recent engagement levels"; "WhatsApp does not currently deliver marketing template messages to WhatsApp users with United States phone numbers"; the exclusion for "a business phone number in the European Economic Area, United Kingdom, Japan, or South Korea, or to a WhatsApp user in these countries"; "If a WhatsApp user responds to a marketing message, it starts a 24-hour customer service window. Marketing messages sent within this window do not count towards the limit"; "wait at least 24 hours before attempting to resend"; error code 131049.
- Manychat Help, Marketing Messages on Messenger (article 24351480518684, updated 27 August 2026), read 12 September 2026: "Unlike Recurring Notifications, which Meta will begin sunsetting globally on January 12, 2026, Marketing Messages on Messenger is a paid solution. Meta charges for its usage through the business's credit card connected to the Ad account(s)"; "currently in beta and has been rolled out by Meta in a limited number of countries. The rollout will continue throughout 2026"; daily or lifetime budget, "Both options apply to campaigns that run for 30 days"; "After approval, there is currently a 10-minute waiting period before messages can be sent to end users."
- Manychat Help, How to send messages outside the 24-hour and 7-day windows in Messenger and Instagram (article 14281199732892, updated 27 August 2026), read 12 September 2026: "Meta is deprecating the Message Tags feature on Messenger on Monday, February 9, 2026"; "Message tags cannot be used for promotional content"; "starting August 10, 2023, notification tokens no longer expire"; "in February 2024, Meta paused allowlisting for the Instagram DM List Beta"; the Human Agent tag "works on both Instagram and Messenger" and "Automated messages are not allowed during the 7-day window." The article's future-tense 9 February 2026 sentence was still on the page under its 27 August 2026 stamp when read. Our Messenger chatbot tutorial follows Meta's own changelog, which dates the error-code-100 cutoff for the three tags to 27 April 2026; the two sources disagree and this entry does not reconcile them. The tutorial is also the source for the Marketing Messages market list (20 markets, excluding the EU, UK and Canada), Meta's per-user and frequency caps, the Recurring Notifications carve-out for existing integrations in the EU, UK, Australia, Japan and Korea, and the observation that Meta's Marketing Messages FAQ dates the Recurring Notifications shutdown two ways (12 January and 10 February 2026), which is why this entry gives no single date of its own. Manychat's 9 February 2026 note covers the Message Tags feature as a whole, not three named tags.
- Tidio Help Center, Flow editor: Triggers (article 5453654525212, dated 19 November 2025), read 12 September 2026: "Visitor returns to the site: The flow starts when the visitor returns to your site (is not a new visitor)"; "The visitor hasn't contacted you for some time: The flow starts when the visitor hasn't contacted you back for a specified time (counted in days). The flow will work only if the visitor has left you an email address"; "Some triggers may be repetitive, so you can also find an option to limit them and decide how many times they should be fired per person."
- Intercom Help, Series explained (article 4425207; the page carries a relative stamp, "Updated today," so its revision date is 12 September 2026), read 12 September 2026: Entry Rules as "the set of filters a customer must match to enter the series"; the wait-block example "Send an email → Wait for 3 days → Send a follow up chat message"; "If a customer's data is updated to match the filters in this exit rule they will exit the series completely, and cannot re-enter"; "If a customer matches the filters for your goal after the set time period, they won't be counted"; "Customers can also exit a Series if they reach the end of a path, hit the series goal or don't engage with messages for a set time."
- Chatbotscape review corpus (the fifteen platform reviews listed at /reviews), searched 12 September 2026 from the repository root. Denominator:
ls sample-reviews/*-review.md | wc -lreturns 15.grep -liE 'win-back|winback|win back' sample-reviews/*-review.mdreturns 0;grep -liE 're-?engag' sample-reviews/*-review.mdreturns 4 (aisensy, blip, intercom, landbot);grep -liE '\bretention\b' sample-reviews/*-review.mdreturns 3 (aisensy, botpress, tars);grep -liE '\bchurn' sample-reviews/*-review.mdreturns 2 (chatfuel, intercom). Passages cited:intercom-review.mdlines 633 and 195;blip-review.mdline 646. - Ahrefs Keywords Explorer, US overview, queried 12 September 2026 — the demand, difficulty, CPC, global-volume and parent-topic figures in this entry's keyword note.
- Chatbotscape evaluation methodology. /methodology (continuously updated).