Owner, trigger and scope
Marketing operations runs the procedure from log to close and owns the suppression listA list of addresses or contacts excluded from every send, such as unsubscribes, hard bounces and spam complaints.. The data protection owner handles any request to delete data and anything beyond marketing. The customer service lead makes sure requests that arrive through service channels, by phone, chat, email or in person, are logged and passed on rather than answered and forgotten.
The trigger is any person asking, by any route, to stop receiving marketing, objecting to marketing or withdrawing a permission; or a request to delete their data that arrives with the marketing team. The person does not have to use the right words. "Please stop sending me these" on a social message is an opt-out, and so is a parent saying it at a reception desk. The site's consent guides follow the regulators' general direction: withdrawing consent should be as easy as giving it, the right to object to direct marketing is absolute, as the GDPR entry states, and opt-outs are honoured promptly and kept on a suppression list so the person is not contacted again.
The scope is marketing in every channel the business uses: email, texts and messaging, post, calls and customer lists uploaded for advertising. Neighbouring work belongs elsewhere:
| Situation | Where it is handled |
|---|---|
| Unsubscribes, bounces and complaints from a send | Email list hygiene SOP |
| Designing how a withdrawal travels between tools | Mapping consent across the stack |
| How long data is kept and how deletion reaches every copy | Data retention across marketing tools |
| A request to see a copy of personal data, or anything beyond marketing | The data protection owner, outside this procedure |
| A sudden rise in unsubscribes after one send | Unsubscribe spike diagnosis |
| Ending a subscription or account | Designing the cancellation experience |
The SOP library routes the other recurring list and send tasks.
Before you start: inputs and access
| Input | Owner | Notes |
|---|---|---|
| The request as received, with the date and the channel | Whoever received it | The person's own words, not a summary |
| The consent map | Marketing operations | Which tools hold the person and how withdrawals travel |
| Access to the CRM, email and text tools and the suppression list | Marketing operations | Enough to search, edit consent fields and add suppression entries |
| The list of uploaded customer audiences and of suppliers holding marketing lists | Marketing operations | Agencies, partners and any service sending on the business's behalf |
| A marked test record that has opted out | Marketing operations | Unmistakable name and domain, as the consent map's tests use |
The consent map is the most important input. It lists every purpose, the system that holds each record and the route a withdrawal takes. If the map is missing or out of date, run the procedure from the best list of tools you have and record the gap for the map's owner; do not wait for the map before honouring a request. A gap found this way is a missing row or reader on the consent mapOne table with a row per purpose the stack uses personal data for: where permission is captured, which system holds it and how a withdrawal reaches each tool., and fixing it there protects the next request as well. Cookie and tag choices are a separate purpose on the same map, and the privacy and consent guide covers them; this procedure handles marketing messages and audiences. Who does what is easiest to see in a short RACI matrix agreed with customer service and the data protection owner.
The procedure
Log the request with the date, the channel and the scope
Create a log entry the moment the request reaches marketing: the date it was received, the channel, the person's words and the scope. Scope is one channel, all marketing, or deletion. The consent map treats an objection to direct marketing as covering every channel it names, so when the person's words are broad, record the broad scope. When the scope is genuinely unclear, ask them once, and suppress for everything in the meantime.
Find the person in every tool the consent map lists
Search each tool on the map for the person, by every identifier the request gives: email address, phone number, name and postcode. People often appear twice, under a work and a personal address or as a customer and a lead. The consent map's route column shows which tools read from the system of record and which hold a copy someone built by hand; the hand-built copies, spreadsheets and exported files are where people are usually missed. Note every place the person was found in the log.
Record the opt-out in the system of record and on the suppression list
Change the consent field for the scope in the system that holds the record, with the date and the source, and add a suppression entry with only what is needed to recognise the person and honour the choice, as the retention guide describes. The suppression list entry explains what belongs on the list. Do not delete the person to make them go away: the suppression entry is what stops an import or a sync bringing them back. The CRMThe system that stores an organisation's contacts, companies, deals and interactions, and the processes built around it. or the email platform usually holds the record; the map says which.
Check the change reached the email, text and CRM tools
Open each sending tool and confirm the person now shows as opted out or suppressed for the right channels. The guide to syncing the CRM and marketing platform sets the rule that matters here: for consent fields the most restrictive value wins, so an older permission never overwrites the new opt-out. Check scheduled sends and automations too, including text journeys built as the SMS and WhatsApp automation guide describes, since a person already inside a journey can be missed by a check made only at entry.
Remove the person from uploaded ad audiences at the next refresh or sooner
A customer listAn ad audience built from the advertiser's own sources: customer lists, site visitors or engagers. uploaded for advertising is a copy made before the opt-out. The playbook for customer lists across ad platforms asks that people who asked not to be marketed to are removed before any file leaves the CRM, so the next file built from the CRM carries the change. When the request covers all marketing, replace the affected lists sooner rather than waiting for the routine refresh; the Meta customer list tutorial shows how a list is rebuilt and replaced on that platform.
Tell agencies and partners that hold marketing lists
Send each supplier on the list a short instruction naming the person by identifier only, the scope, and a request for written confirmation of removal. The consent map should already list them as tools that do not learn the consent state automatically, which is exactly why they need telling. Record who was told and when, and chase anyone who has not confirmed.
Pass a deletion request to the data protection owner
If the person asked for their data to be deleted, or asked for anything beyond stopping marketing, pass it to the data protection owner with the log entry. The retention guide explains how deletion has to reach every copy in an order that stops a sync restoring what was removed, and why the suppression entry is kept so the person stays stopped. The owner decides what is deleted and when; marketing operations does not delete on its own initiative.
Confirm to the person and close the log entry
Confirm in writing, by the channel the person used where possible, that they will not receive marketing in the scope they asked for, and say briefly that account and service messages are separate, as the list building and consent guide separates them. Do not use the confirmation to ask them to reconsider. Then check the marked test record is still excluded after the latest sync, complete the log and close the entry.
A language school's phone opt-out (illustrative)
An opt-out at reception that reached an old ad list and an agency file
Tazzebrin Language School, an invented school running evening and holiday courses, took a call at reception on a Tuesday from a parent who asked to stop all marketing messages. The receptionist logged the words "please take me off everything" with the date and the phone channel, and passed it to marketing operations that afternoon. The search found the parent in 4 places: the CRM as the payer for a child's course, the email platform, a customer list uploaded for ads 11 weeks earlier, and a prospect file an agency had been given for a summer campaign. The opt-out was recorded in the CRM with the scope "all marketing", a suppression entry was added, and the email platform showed the parent suppressed after the next sync, with 1 scheduled newsletter no longer including them. The ad list was rebuilt from the CRM and replaced the same week instead of at the routine refresh, and the agency confirmed removal in writing 2 days later. The school's confirmation letter said marketing had stopped and that course messages about the child's classes would continue. The marked test record was still excluded after the latest sync, and the entry was closed.
QA checks
Before the log entry is closed, marketing operations confirms each check below. A check that fails keeps the entry open and goes to the owner of the route that failed.
- The person is suppressed in every tool the consent map lists for their channels.
- No scheduled send, automation or audience upload still includes them.
- Suppliers holding lists confirmed the removal.
- A deletion request reached the data protection owner and a suppression entry was kept as the retention guide describes.
- The marked test record is still excluded after the latest sync.
Hand-offs and records
Customer service hands requests that arrive at its channels to marketing operations with the person's words and the date. Marketing operations hands deletion requests and anything beyond marketing to the data protection owner, and route failures, such as a tool the opt-out did not reach, to the owner of that row on the consent map, who fixes the route rather than the single record. When a person is mailed again after their opt-out was closed, the diagnosis for unsubscribed contacts still receiving email works back from the message to the route that failed. The email campaign send SOP checks suppression before each campaign goes out, and each send then picks up the suppression through the email list hygiene SOP, which keeps the global list synced across sending tools. When the message says the person never signed up for the email at all, the diagnosis of subscribers saying they never signed up works back from the consent record to the route the address took.
The record is a log entry per request: date received, channel, scope (one channel, all marketing or deletion), tools updated, audiences and suppliers notified, confirmation sent and the date closed. The log is also evidence: it shows the business honoured each request across every tool, and a run of requests from one channel or one campaign is worth passing to whoever owns that programme.
Common mistakes
Each of these leaves a person who asked to stop still receiving marketing from somewhere.
- Treating only the unsubscribe link as an opt-out. A reply, a call or a social message counts just as much.
- Narrowing the scope. A person who says "stop contacting me" has not asked to stop only one newsletter.
- Deleting instead of suppressing. The next import or sync brings the person straight back.
- Fixing one tool. A change made in the email platform but not the CRM can be overwritten by the next sync.
- Forgetting uploaded audiences. An ad list built before the request keeps the person until it is replaced.
- Not telling suppliers. An agency's file is a copy nobody else can see or update.
- Handling deletion in marketing. Deletion and requests beyond marketing go to the data protection owner.
