Make suppression a campaign release condition
A tuition centre may keep parent records in a CRM, prepare newsletters in a campaign tool and give an agency an exported audience list. In this illustrative setup, changing one subscription field does not prove that the next message will be blocked. The practical decision is whether the campaign owner has evidence of exclusion at every relevant sending point. If an address cannot be excluded reliably, hold the affected campaign while the gap is resolved.
OFCA FAQ Q2.5 says further commercial electronic messages to the address concerned should stop within ten working days from the day the unsubscribe request is sent. Do not start that period at the next CRM sync. Suppress promptly as an operational rule; this article does not calculate a holiday-dependent deadline.
UEMO sending rules do not establish permission to use personal data for direct marketing under the PDPO. The Government’s explanation of the PDPO addresses consent requirements, subject to exemptions, and the right to require that use to cease. Do not treat the UEMO period as permission to continue personal-data-based marketing after withdrawal. Escalate uncertain scope to the person responsible for privacy.
Use one case record across the tools
Give each request a case identifier and one accountable owner, even when different colleagues operate the tools. Keep the original request accessible to authorised staff and separate the time sent from the time received. Record the exact affected address and what the customer asked to stop. A broad request to stop marketing must not silently become a newsletter-only preference. Where identity or scope needs clarification, apply a provisional block to the known affected address while the owner resolves the ambiguity.
| Receipt | Case ID, original request, sent time where available, received timestamp and timezone | Intake record linked to the original message or submission |
|---|---|---|
| Affected address and scope | Exact email or number; sender and marketing scope covered by the request | Owner confirms scope; unresolved questions remain open |
| Accountable sender | Organisation authorising the campaign, named owner and agency contact if applicable | Owner accepts responsibility for all relevant sending routes |
| Queued campaign check | Inspect scheduled sends, automated follow-ups and previously exported lists | Exclusion confirmed or affected send paused before release |
| Propagation proof | Check suppression in CRM, campaign tool and agency-held audience | Timestamped destination checks and campaign audience evidence |
| Exception escalation | Assign failed syncs, inaccessible tools or uncertain scope to a named person | Hold remains until owner verifies resolution and records closure |
A successful export or integration job is only evidence that a process ran. Check the destination state and the actual campaign audience as well. Ask the agency to confirm which list version it will use and how it applies the exclusion. Keep proof restricted to people who need it; avoid circulating a complete parent database merely to show that one address was removed.
Choose controls your team can operate
A shared register with manual checks can be workable when campaigns are infrequent and one person controls release. Its constraint is staff availability: assign a deputy and check new requests again immediately before sending. Automated propagation is more appropriate when several tools send continuously, but it needs failure alerts, retries and a person who can stop dispatch. Neither option is complete if an old spreadsheet import can restore a withdrawn address to the audience.
In a rehearsal, use an address controlled by the centre. Add it to a test audience, queue a campaign without releasing it, then submit an unsubscribe through the real intake route. Verify each destination, check the queued audience and repeat an old import. The expected outcome is continued exclusion. Also simulate a failed sync: the owner should receive an exception and the affected send should remain held. These are acceptance tests to request from your operator, not assumed features of any product.
Related guide: connecting business systems without duplicate recordsOFCA resource: sending rules and unsubscribe requirementsReview the statement, then rehearse the next send
OFCA Q2.6 generally requires sender information and the unsubscribe statement in Chinese and English, with recipient language-preference and specified name/address exceptions. Q2.1 also requires sender identification, contact information and an unsubscribe route. Review both editions against the actual mechanism.
Have a Chinese-speaking reviewer and an English-speaking reviewer each follow the instructions from a received test message. Confirm that both routes reach the same case workflow and that neither version promises a narrower or faster outcome than the team can deliver. Do not label promotional course offers as service notices to bypass suppression. If necessary operational messages share a sending tool, review their purpose and routing separately with the privacy owner.
Before the next campaign, name its release owner and fill in the checklist for one controlled test request. In the tuition-centre example, the owner closes the case only after the CRM, campaign audience and agency list all show the intended exclusion. If the agency cannot confirm its queued list, keep that send paused and escalate. The next action is a demonstrated stop across the real workflow, followed by a recorded decision to release or hold.
Before you proceed
- Can the owner trace the request’s sent and received times without restarting the clock at a sync?
- Does each sending destination exclude the affected address, including queued and agency campaigns?
- Will failed propagation hold the affected send and reach a named person?
- Have both language versions and the old-import scenario been tested?
