Schedule and reconcile delivery
Schedule and reconcile delivery.
4 stages · 0 approvals
Roles and responsibilities
-
Step 1Schedule delivery
Campaign NumberNameStart TimeEnd Time
-
Step 2Dispatch eligible recipients
SendSubscriberQueued AtProvider Accepted At
-
Step 3Process delivery events
Send NumberCampaignRecipient Count SentRecipient Count Failed
-
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.
Schedule delivery
Create a durable DispatchKey for the approved campaign version and audience. Preserve the selected delivery window with EndTime after StartTime and reconcile it with ScheduledAt. Scheduling reserves work without claiming that a provider accepted or delivered any message.
Dispatch eligible recipients
Immediately before each provider submission, recheck the subscriber, purpose, list status, global suppression and domain limit under the same dispatch claim. Atomically claim one recipient DispatchKey. Provider acceptance records Sent and the provider message ID; it is separate from Delivered. Unknown outcomes remain reserved for reconciliation instead of blind resend.
Process delivery events
Authenticate and deduplicate each provider event by its event ID. Several opens or clicks may refer to one message without replacing each other. Preserve out-of-order event history and reconcile terminal delivery facts without moving a failed recipient back to Queued. Label proxy/bot/unknown engagement so open rates do not claim verified human attention.
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
0 approvals required in this process
- 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
Process delivery events
Preserve out-of-order event history and reconcile terminal delivery facts without moving a failed recipient back to Queued.
-
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.
Engagement tracking. Distinct clicks on one message remain distinct events without replay inflation. Duplicate callbacks do not inflate counts and proxy opens are not labeled verified human activity.
Campaign analytics. Reported totals reconcile to unique recipient and provider event records. Do not equate provider acceptance with delivery or claim inbox placement from opens.
Records and postings
| Stage | Records | Effect |
|---|---|---|
| 1 Schedule delivery | CampaignsSends | Retain the stated outcome and its source evidence |
| 2 Dispatch eligible recipients | SendsSendRecipientsSuppressions | Retain the stated outcome and its source evidence |
| 3 Process delivery events | OpenEventsClickEventsBouncesSpamReportsUnsubscribesIntegrationEvents | 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.
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
› schedule and reconcile delivery · schedule delivery on Campaigns, Sends
✓ Create a durable DispatchKey for the approved campaign version and audience.
› schedule and reconcile delivery · dispatch eligible recipients on Sends, SendRecipients, Suppressions
✓ Immediately before each provider submission, recheck the subscriber, purpose, list status, global suppression and domain limit under the same dispatch claim.
› schedule and reconcile delivery · process delivery events on OpenEvents, ClickEvents, Bounces, SpamReports, Unsubscribes, IntegrationEvents
✓ Authenticate and deduplicate each provider event by its event ID.
› schedule and reconcile delivery · reconcile provider state on IntegrationEvents, Sends, SendRecipients
✓ Investigate Unknown dispatches with the original provider idempotency key and message reference.
Other processes
4 moreHonor preferences and manage suppression
Honor preferences and manage suppression.
3 stages · 0 approvals