Scope
This guide covers daily operation for Push Notifications. Availability depends on your tenant package, role and configured providers.
Purpose
Reach opted-in web or app audiences with timely notifications.
Create notification content, audience and delivery timing.
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.
- Create notification content, audience and delivery timing.
- Inspect the current status and supporting context before changing anything.
- Account for system behaviour: Trigger push from behaviour, lifecycle and recovery workflows.
- Resolve failures, missing data or approval requirements before continuing.
- Close the loop: Review sends, delivery, clicks and re-engagement.
Verify the result
Review sends, delivery, clicks and re-engagement. 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
Respect permission state, caps and channel eligibility. Predictive, attribution and recommendation outputs support operator judgement; provider and data limitations remain relevant.