Run a drip journey
Run a drip journey.
4 stages · 1 approval
Roles and responsibilities
-
Step 1Approve campaign
Campaign NumberNamePrepared ByTarget List
-
Step 2Run drip journey
Enrollment NumberJourneySubscriberNext Step
-
Step 3Honor preferences
Consent NumberSubscriberPurposeDecisionRestricted
-
Step 4Reconcile provider state
SendSubscriberQueued AtProvider Accepted At
Process steps
Follow the process from start to finish. Select a step to see who acts and what changes.
Approval required
Approve campaign
Email Marketing Manager submits the audience rules, purpose, approved template and schedule. Campaign Approver independently approves that Revision and the AudienceRevision. Changed content, audience or purpose requires fresh review. The scheduled command is rejected if approval no longer matches.
Run drip journey
Submit the journey version and exit policy for Campaign Approver approval. Enroll each subscriber once per admission occurrence. Before each due step, check current permission, exit events and journey state; reserve that step once. A verified reply or configured CRM conversion can exit the journey without fabricating a sales outcome.
Honor preferences
Apply a preference change to its explicit list or global scope and stop unsent queued work that is no longer eligible. The dispatch-time check closes the race with an earlier audience snapshot. A request cannot recall a message already accepted by the provider. Suppression removal requires an independent approved review and never restores a withdrawn purpose by itself. A ListSpecific unsubscribe updates only its named list and purpose and creates no global suppression; unrelated still-permitted lists remain eligible. Global unsubscribe blocks all lists in its stated scope.
Reconcile provider state
Investigate Unknown dispatches with the original provider idempotency key and message reference. Confirm acceptance or failure before releasing any retry. Revoked credentials stop new dispatch, while configured inbound reconciliation can record verified outcomes for prior messages. Keep unmatched events visible for scoped investigation.
Approvals and exception handling
1 approval required in this process
-
Approve campaign
Campaign Approver signs · run drip journey waits
Campaigns, EmailTemplates, Lists - Record ownershipKeep every reference and attachment in the authorized workspace and the acting person’s permitted scope. A copied link cannot grant access to another customer’s record.
- Current decisionsReview the latest saved state before changing work. If someone changes protected facts after approval, send the revised record through its required review again.
- Repeated actionsA retry returns the original result when the same action has already been accepted. Keep an uncertain external outcome visible until its original request is reconciled.
- CorrectionsRetain the earlier decision and the reason for correcting it. A report or automation should not hide a reversal by deleting the original evidence.
When the process needs attention
-
reject
Approve campaign
The scheduled command is rejected if approval no longer matches.
-
reject
Reconcile provider state
Confirm acceptance or failure before releasing any retry.
Follow the outcome
The receiving team needs the current owner, the next action and a traceable result. Use the linked operating records when investigating a delay rather than treating a status label as the complete explanation. If a required person is unavailable, route the decision through an authorized replacement who remains independent of its preparer. Resolve missing evidence before closing the handoff. A locally completed action may still require a confirmed response from its configured destination.
Email campaigns. An approved unchanged campaign creates one delivery intent. Reject self-approval or a changed audience using a stale approval.
Email templates. The campaign uses the exact approved content and footer. Reject edits to approved content without a new version and review.
Audience segmentation. The approved segment resolves to the eligible intended audience. Reject arbitrary query execution and foreign-workspace recipients.
Records and postings
| Stage | Records | Effect |
|---|---|---|
| 1 Approve campaign | CampaignsEmailTemplatesLists | Record an independent decision on the submitted revision |
| 2 Run drip journey | JourneysJourneyStepsJourneyEnrollmentsSends | Retain the stated outcome and its source evidence |
| 3 Honor preferences | UnsubscribesConsentEventsListMembershipsSuppressions | Retain the stated outcome and its source evidence |
| 4 Reconcile provider state | IntegrationEventsSendsSendRecipients | Retain the stated outcome and its source evidence |
Process reports
All reportsCampaign Performance
Campaign and send outcomes reconciled to unique accepted, delivered, bounced, suppressed and unknown recipients.
Engagement Signals
Unique engagement events with human-candidate, proxy, bot and unknown classifications.
Journey Progress
Due, completed, paused and exited journey steps with their version and delivery intent.
Contact Policy Audit
Purpose evidence, list/global preferences and blocked delivery outcomes for policy review.
Suppression Decisions
Suppression causes, removal requests, independent decisions and remaining contact restrictions.
Run by an agent
Agent support
An agent acts within the current user or service scope. It cannot provide its own independent human approval, restore a withdrawn contact purpose or turn an unknown external response into a confirmed result.
# Example after configuration
$ curl -fsSL https://www.erp.ai/skill.md | paste into your agent
› run a drip journey · approve campaign on Campaigns, EmailTemplates, Lists
⏸ approval · waiting for the campaign approver
# 3 more stages after approval: run drip journey, honor preferences, reconcile provider state
Other processes
4 moreHonor preferences and manage suppression
Honor preferences and manage suppression.
3 stages · 0 approvals