- Owner or Admin access to privacy and communication controls
- The customer's verified identity, channel, and latest consent request
- Documented consent source, purpose, and applicable suppression state
- The organization's approved privacy escalation process
Permission is channel- and purpose-specific
Open Settings → Privacy & consent. The summary counts WhatsApp opted-in contacts, email-marketing opted-in contacts, cross-channel conflicts, and opted-in records with missing evidence. It also reports email suppressions and recent contact imports when those data sources are available.
A contact record, previous purchase, or WhatsApp permission does not automatically authorize email marketing. Transactional, relationship, and marketing email use different eligibility rules.
Communication eligibility
- 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.
Review records that need attention
- Open Privacy & consent and note the Last checked time.
- If the banner says records need review, separate cross-channel conflicts from missing evidence.
- Open the relevant contact and inspect channel-specific consent state, source, and time.
- Compare the record with authorized source evidence, such as the captured form or customer request.
- Correct only from trustworthy evidence. If permission cannot be proved, leave the contact ineligible for that purpose.
- Review recent imports for a batch that may have introduced the pattern.
- Reopen Privacy & consent and confirm the requiring-review count changes as expected.
Understand suppression
| State | Meaning | Operating rule |
|---|---|---|
| Opted in with evidence | Permission is recorded for a channel/purpose with supportable provenance | Still check message purpose and current suppression |
| Missing evidence | An opted-in state lacks complete provenance | Do not infer permission; repair from an authorized source |
| Cross-channel conflict | Channel states disagree or do not support the intended use | Resolve each channel independently |
| Unsubscribed suppression | Recipient exercised an opt-out | Compliance protected; do not remove merely to resend |
| Complained suppression | Provider or recipient complaint is recorded | Compliance protected; investigate source and stop marketing |
| Operational bounce/block | Delivery protection may apply | Fix address/provider issue without overriding consent policy |
The Privacy page reports how many suppressions are compliance protected. Detailed email recovery controls live in Message delivery. Administrative convenience is not a valid reason to remove an unsubscribe or complaint suppression.
Imports and campaigns
Before importing, map consent fields only when the source file carries trustworthy provenance. After import, review results and Privacy summary before launching a campaign. Campaign audience membership never overrides consent or suppression.
Retention and deletion
Use the archive, retention, export, and deletion controls that are visible for the relevant record type and follow the policy shown in the product. If a required export or erasure action is not available, preserve the request and contact WRKZY Support or the organization's approved privacy route. Do not delete unrelated records as a workaround.
Recovery
If consent counts are unavailable, retry before changing records. If a campaign reached ineligible recipients, pause it, preserve the campaign and recipient evidence, and review the import/source process. Escalate with workspace, contact ID, channel/purpose, consent state and provenance fields, suppression reason, import/campaign ID, and safe timestamps.
- Channel and communication purpose identified
- Opt-in evidence—not assumption—verified
- Conflicts and missing evidence resolved conservatively
- Complaint and unsubscribe suppressions preserved
- Import source and campaign dependency checked
- Sensitive customer content excluded from evidence