Skip to content
allanninal.dev/build
Collaborate

Part 3 of 7 · Win-back campaigner series ~6 min read

How the suppression check works

This is the post that matters. Everything else is a scheduling problem; this is the part that determines whether the campaign is a modest revenue improvement or the reason somebody tells the story about your company at a dinner party.

Key takeaways

  • Five categories: unresolved complaint, recent refund, withdrawal, closed, bereaved.
  • The check runs before segmentation, so a suppressed customer is never scored or targeted.
  • An unresolved complaint is a task for a person, not a suppression and nothing else.
  • Bereavement and business closure markers are permanent and never expire.
  • Every suppression is recorded with its reason, because the reason is the useful part.

The five categories

The five checks that decide whether a lapsed customer may be contactedA vertical chain of five steps entered by a box labelled A lapsed customer, past their interval. Step one asks whether there is an open complaint or one that closed badly; if so it exits to To a person, not to a campaign. Step two asks whether there was a refund or delivery failure in the last two orders; if so it exits to Suppress, and fix that first. Step three asks whether they have withdrawn contact, checking the consent record from Day 105; if so it exits to Suppress permanently. Step four asks whether the account is marked closed or bereaved, a permanent marker; if so it exits to Suppress forever, quietly. Step five marks them contactable and moves on to choosing an offer. A note says the first exit is not a suppression but a task, and somebody has to do it.AWS ACCOUNTA lapsed customerpast their intervalOpen complaint?or one closed badlyTo a personnot to a campaignyesRefund or failure?in the last 2 ordersSuppressfix that firstyesWithdrawn contact?ask the consent recordConsent recordfrom Day 105SuppresspermanentlyyesClosed or bereaved?a permanent markerSuppressforever, quietlyyesContactablechoose an offerThe first exit is not a suppression. It is a task, and somebody has to do it.
Fig 1. The suppression gates in order. The first one produces work rather than silence, which is the distinction most implementations miss.
  • App integration
  • Machine learning
  • Security & identity
  • Management
  • People

The complaint case produces work

A customer who lapsed after a complaint is the most valuable name on the list and the one that must never receive an automated message. They stopped for a reason you already know, it is written down, and a marketing email that ignores it confirms every assumption they made when they left.

So that exit creates a task with the complaint attached: here is who, here is what happened, here is when. Somebody calls or writes personally. The conversion rate on that is far higher than any campaign and the volume is small enough that it is genuinely possible, which is the argument that gets it done.

The permanent markers

Never expire, never override, never explain themselves

  • Deceased. Recorded when a family member tells you, or a delivery is returned with that reason. No campaign of any kind, ever.
  • Business closed. Same treatment. A win-back to a dissolved company reaches whoever is winding it up.
  • Withdrawn. They asked not to be contacted. This is the whole of it.
  • Do not build an override. Not for a special campaign, not for a big customer, not for a one-off. The absence of the mechanism is the protection.
  • Do not report the reason anywhere it will be read casually. The suppression list shows counts by category and the detail only to whoever needs it.

The bereavement case is worth being specific about because it is the one that produces the genuinely awful outcomes, and it is entirely preventable. The marker usually arrives informally — a phone call, a reply to a message, a returned parcel — and the system’s only job is to make recording it easy and make honouring it automatic.

Making it easy matters more than it sounds. If setting the marker requires a database change or a support ticket, it will not happen consistently, and the campaign will find the customer six weeks later. One field, one click, from wherever the person heard.

Before segmentation, not after

Why suppression runs before segmentation in a win-back campaignA horizontal row of five boxes. Lapsed list: six hundred and twelve customers. Suppression first: minus one hundred and ninety-eight. Contactable: four hundred and fourteen. Then segment, and choose offers. Send: one each. A note says suppressed customers are never scored, never segmented and never in a target list.THE ORDER MATTERSLapsed list612 customersSuppression first-198Contactable414Then segmentand choose offersSendone eachSuppressed customers are never scored, never segmented, never in a target list.
Fig 2. Why suppression runs first. A suppressed customer that reaches the segmentation stage exists in a targeting list somewhere, and lists get exported.
  • App integration
  • Security & identity
  • Analytics
  • People

Running the check last is the obvious implementation and it leaves suppressed customers sitting in intermediate lists that get exported, copied into spreadsheets, and used for something else six months later. Running it first means they never enter the pipeline at all.

Recording the reason

Every suppression stores which gate stopped it and when. That record does two jobs: it answers “why did we not contact this customer” instantly, and its distribution is a genuinely useful business signal.

A campaign where a hundred and ninety-eight of six hundred and twelve are suppressed and seventy of those are unresolved complaints is not primarily telling you about win-backs. It is telling you there are seventy open complaints, which is a more important finding than anything the campaign will produce.

Next: what to actually offer.

All posts