Scope
This guide covers daily operation for Unattended Messaging Controls. Availability depends on your tenant package, role and configured providers.
Purpose
Operate event-triggered messaging with recovery and kill switches.
Monitor active patterns and disable unsafe sending quickly.
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.
- Monitor active patterns and disable unsafe sending quickly.
- Inspect the current status and supporting context before changing anything.
- Account for system behaviour: Execute approved WhatsApp or messaging recovery sequences.
- Resolve failures, missing data or approval requirements before continuing.
- Close the loop: Inspect attempts, delivery, failure and recovery outcomes.
Verify the result
Inspect attempts, delivery, failure and recovery outcomes. 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
Enforce global stops, caps, consent and incident ownership. Predictive, attribution and recommendation outputs support operator judgement; provider and data limitations remain relevant.