Scope
This guide covers daily operation for Consent, DND & Suppressions. Availability depends on your tenant package, role and configured providers.
Purpose
Keep channel eligibility close to activation decisions.
Review eligibility before campaigns and customer contact.
Before you start
Correct tenant and project selected
Required source or provider is available
An accountable owner is identified
Test data can be separated from live activity
Procedure
- State the operating objective and the record, audience, campaign or project in scope.
- Review eligibility before campaigns and customer contact.
- Inspect the current status and supporting context before changing anything.
- Account for system behaviour: Apply opt-outs and suppression changes to downstream delivery.
- Resolve failures, missing data or approval requirements before continuing.
- Close the loop: Monitor consent state, list health and blocked sends.
Verify the result
Monitor consent state, list health and blocked sends. Confirm that the intended record, state, run or report is visible to another authorised operator and that its next owner is clear.
Completion checkpoint
The capability is in the intended state, evidence is current, exceptions are owned and the next action can be understood without a separate status message.
Controls and limitations
Preserve consent history and regulatory channel rules. Predictive, attribution and recommendation outputs support operator judgement; provider and data limitations remain relevant.