A customer who opted out and keeps receiving messages on another channel experiences one business ignoring them. How to build a single opt-out record every channel checks.
Key takeaways
- Every tool maintains its own opt-out list, and that is exactly the problem.
- The identity key must be shared - normalised phone and email - or the opt-out will not match.
- Separate opting out of marketing from operational messages, and explain the difference.
- The check at send time is the only component that genuinely prevents the fault.
The customer does not see channels - they see one business. When they unsubscribe from email and keep receiving SMS, as far as they are concerned the business ignored the request. The fix is a single opt-out record every channel checks before sending, rather than a separate list in each tool.
How the fault appears
| Situation | What happens | What the customer experiences |
|---|---|---|
| Opted out of email only | The CRM still sends SMS | "I asked to be removed and it doesn't work" |
| Opted out on WhatsApp | The email platform never knew | The same thing, on another channel |
| A number in a different format | The opt-out does not match the record | Sent again by mistake |
| Two addresses for one person | The opt-out applies to one only | Sent again to the second address |
| An old list imported | Previous opt-outs are overwritten | Back on the list after two years |
The last row is the worst and it is common: importing an old file that restores people who opted out long ago.
What the opt-out record must hold
- An identity key - normalised phone, email, and ideally a customer id.
- What kind of opt-out it is - marketing, a specific channel, or everything.
- When and where the request came from.
- Who recorded it - the customer, a rep, or a system.
- Status - active, or reversed by the customer themselves.
The second field is what lets you preserve service: a customer who asked to stop receiving promotions usually still wants order confirmations and appointment reminders, and you cannot infer that without a field that distinguishes them.
Building it without a big project
- Pick one place to hold the record - usually the CRM or invoicing software.
- Normalise the keys - phone in one format, email lowercased.
- Import existing opt-outs from every tool and merge them.
- Add a check before sending on every channel, even a manual one at first.
- Block imports that overwrite existing opt-outs.
Step 5 is what prevents the return: every future import must check against the record rather than the reverse. The same single-identity-key logic appears in duplicate customer records between systems, and here it matters especially because an error causes a send that should never have happened.
What happens when the opt-out arrives in conversation
A large share of opt-outs in Israel are spoken on the phone or typed into WhatsApp - "take me off the list" - rather than clicked on a button. Those are the ones that disappear, because no system captured them.
The fix is a simple practice: every rep has one way to record an opt-out, and it takes seconds. When it takes longer than that, it does not get recorded - and the customer receives the next message, gets annoyed, and this time blocks as well.
What to tell the customer
One confirmation message after an opt-out saves enquiries: exactly what was removed, what will still arrive (confirmations, delivery updates), and how to come back if they want to. It is also the only opportunity to ask gently why - one question, not a survey.
What not to do: make opting out difficult, require a login, or send "are you sure?" twice. Friction does not reduce opt-outs; it converts them into complaints and blocks, and a block is far worse than an orderly opt-out - because after it even the operational messages stop arriving.
What to measure
- Opt-out rate per message type, not in aggregate.
- How many opt-outs reps recorded manually - a measure of how usable the practice is.
- How many times a message went to someone who opted out - the one metric that must be zero.
- How many blocks on WhatsApp, because they are the sign the opt-out did not work.
The third is worth checking after every send for the first two months. When it is not zero, the cause is nearly always the identity key - a number stored in a different format - rather than anyone's intent.
Why does this break in well-organised businesses?
A business using several good tools falls into this more often than one running everything in a single spreadsheet. The email platform is excellent at managing opt-outs - its own. The SMS platform is excellent at managing opt-outs - its own. WhatsApp keeps its own opt-out state. Each does its job correctly, and none of them knows about the others.
So the fix is not replacing a tool but adding a thin layer above them: one place that consolidates, and a rule that no send goes out without checking against it. In a small business that can be a spreadsheet; in a larger one it is a table in the CRM with an automated check. What does not change is the principle: the tool that sends is not the tool that decides who may be sent to.
What to do when you discover you sent by mistake
It happens, and what you do afterwards decides whether it is an incident or a complaint. What works: identify immediately who was contacted in error, record them in the central registry, and send a short apology only to anyone who has already complained - rather than a wave of apologies that produces another message to people who asked not to receive any.
More important is finding the cause: an import that overwrote, a number format that did not match, or a rep sending from an old list they kept. Those three cover nearly every case, and each has a structural fix that prevents the next one.
Sources
Frequently asked questions
How quickly must an opt-out be honoured?
Operationally, as fast as possible - and above all before the next send. The common failure is a campaign already queued that goes out after the opt-out was recorded, which is why the check belongs at send time rather than at list-building time.
What about a customer who opted out and bought again?
A purchase is not consent to marketing, so the opt-out stands until they re-consent. What you can send is anything tied to the transaction itself - confirmation, receipt, delivery update - which is precisely why the record separates message types.
Can we send one message to check whether they changed their mind?
Not on the channel they left. If they opted out of email, you can ask on another occasion - in conversation or through a form on the site - but an extra send "just to check" is exactly what they asked not to happen.
How do you manage opt-outs with no CRM?
One spreadsheet with two columns - normalised phone and email - plus a date is entirely sufficient. What matters is that there is only one, that everyone who sends opens it first, and that list imports are checked against it.
Keep reading
Related service
WhatsApp Cloud API
Templates, a two-way inbox and reminders on the official Meta API.
About the author
Yehonatan Saadia
Freelance automation, web & MVP developer
I'm Yehonatan Saadia, a senior developer who builds business automation, custom websites, and MVPs for small and mid-sized companies across the US, Europe, and Israel. These guides come from real client work, not theory.
Work with meHave a project like this?
Tell me what you're trying to automate or build and I'll tell you the fastest reliable way to ship it.