Scope
This guide covers daily operation for WhatsApp Campaigns. Availability depends on your tenant package, role and configured providers.
Purpose
Run template-led WhatsApp campaigns and lifecycle messages.
Select audience, template variables, media and schedule.
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.
- Select audience, template variables, media and schedule.
- Inspect the current status and supporting context before changing anything.
- Account for system behaviour: Trigger approved templates from journeys and unattended patterns.
- Resolve failures, missing data or approval requirements before continuing.
- Close the loop: Inspect delivery, read, reply, failure and conversation context.
Verify the result
Inspect delivery, read, reply, failure and conversation context. 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
Use consent, approved templates, caps and kill switches. Predictive, attribution and recommendation outputs support operator judgement; provider and data limitations remain relevant.