Scope
This guide covers setup & configuration for Unattended Messaging Controls. Availability depends on your tenant package, role and configured providers.
Purpose
Operate event-triggered messaging with recovery and kill switches.
Define eligible triggers, provider, template and recovery ladder.
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
- Open the correct tenant and confirm the project or workspace that owns this capability.
- Define eligible triggers, provider, template and recovery ladder.
- Connect or select the required source records and owners.
- Create a safe test configuration before using live customer or campaign data.
- Inspect attempts, delivery, failure and recovery outcomes.
- Enforce global stops, caps, consent and incident ownership.
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.