- Permission to review consent and privacy controls
- The customer's identity, channel, consent source, and latest request
- The organization's approved unsubscribe and suppression policy
- A safe audit trail for any manual change
Four controls answer different questions
| Control | Question |
|---|---|
| Consent | Did the person authorize this channel and purpose with supportable evidence? |
| Unsubscribe | Did the email recipient withdraw future marketing permission through the provided path? |
| Suppression | Has the organization or delivery system blocked this address or identity from bulk email? |
| Contact pressure | Is another eligible message still too frequent or poorly timed? |
| Audience exclusion | Does this campaign deliberately omit an otherwise eligible governed group? |
One control cannot substitute for another. A tag named Opted in is not consent evidence. Removing a suppression is not permission. WhatsApp permission does not transfer to email, and email permission does not transfer to WhatsApp.
Record consent at the contact method
On the contact, review each phone and email method. WhatsApp and email marketing status can be Opted in, Opted out, or Unknown. For an opt-in, retain the source, timestamp, and available consent text, version, and categories. Unknown is the correct state when evidence is absent.
Bulk imports that claim opt-in require evidence columns and an explicit attestation. Do not attest based on assumptions or a vendor’s generic “clean list” label.
Email unsubscribe and suppression
Email campaign launch is blocked when unsubscribe setup is not ready. Recipient preflight excludes unsubscribed, suppressed, invalid, and otherwise ineligible addresses. A completed campaign records unsubscribe activity for future eligibility.
Do not manually change a contact to eligible merely to increase sendable count. Investigate why they are suppressed, follow the organization’s remediation policy, and preserve the decision trail.
WhatsApp audience eligibility
The WhatsApp preview checks a valid normalized phone, opt-in state, deduplication, exclusions, sender and template readiness, plus campaign pressure. Skipped counts and reasons must be reviewed before launch.
Communication eligibility is evaluated at use time
- 01ProofPermission evidence
Record why, when, and for which channel contact is permitted.
- 02GateChannel eligibility
Recipient identity and provider rules allow this communication.
- 03StopSuppression check
Unsubscribe, block, retention, and policy exclusions are applied.
- 04SendApproved communication
Only the intended, governed message may proceed.
- 05UpdatePreference or retention event
Future eligibility changes when the customer opts out or data expires.
Respond to a withdrawal
- Confirm the customer and channel.
- Record Opted out or allow the governed unsubscribe event to update eligibility.
- Stop pending manual or automated marketing follow-up on that channel.
- Review scheduled campaigns and automations that may already contain a snapshot.
- Preserve only the minimum evidence required by policy.
Verify the control
Reopen the contact method and confirm the new channel status and evidence. Preview the contact in a marked test audience or affected scheduled workflow and verify WRKZY excludes it for the relevant reason. Do not send a live message to test an opt-out.
Escalate a suspected failure
If an opted-out or suppressed recipient received a campaign, stop related launches. Preserve campaign ID, recipient-safe identifier, channel, timestamps, consent state, and delivery evidence. Do not ask the recipient for authentication codes or expose other audience members in a screenshot.
- Consent checked on the actual channel method
- Unknown was not converted without evidence
- Unsubscribe and suppression setup passes
- Campaign exclusions and pressure reviewed
- Scheduled or automated sends considered after opt-out
- Incident evidence is redacted and scoped