Scope
This guide covers daily operation for Email Campaigns. Availability depends on your tenant package, role and configured providers.
Purpose
Create, deliver and report permission-aware email programmes.
Build campaigns, audiences, tests and scheduled delivery.
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.
- Build campaigns, audiences, tests and scheduled delivery.
- Inspect the current status and supporting context before changing anything.
- Account for system behaviour: Trigger email from journeys, workflows and recurring programmes.
- Resolve failures, missing data or approval requirements before continuing.
- Close the loop: Inspect delivery, opens, clicks, bounces and conversions.
Verify the result
Inspect delivery, opens, clicks, bounces and conversions. 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
Apply consent, suppression, unsubscribe and frequency controls. Predictive, attribution and recommendation outputs support operator judgement; provider and data limitations remain relevant.