Scope
This guide covers daily operation for Customer Journey Builder. Availability depends on your tenant package, role and configured providers.
Purpose
Coordinate lifecycle branches, waits, actions and exits.
Compose decisions, waits, messages, tasks and handoffs.
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.
- Compose decisions, waits, messages, tasks and handoffs.
- Inspect the current status and supporting context before changing anything.
- Account for system behaviour: Run event-driven journeys across configured channels.
- Resolve failures, missing data or approval requirements before continuing.
- Close the loop: Review entries, progression, delivery and outcome paths.
Verify the result
Review entries, progression, delivery and outcome paths. 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, caps, approvals and observable run history. Predictive, attribution and recommendation outputs support operator judgement; provider and data limitations remain relevant.