Honor preferences and manage suppression
Honor preferences and manage suppression.
3 stages · 0 approvals
Roles and responsibilities
-
Step 1Build permitted audience
Subscriber NumberEmailFirst NameLast Name
-
Step 2Honor preferences
Consent NumberSubscriberPurposeDecisionRestricted
-
Step 3Reconcile 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.
Build permitted audience
Import subscribers with source and purpose evidence, deduplicate normalized addresses and preserve withdrawals. Validate any required confirmation using a hashed single-use token with expiry. A source CRM connector maps explicit contact identifiers and allowed fields; it cannot infer marketing permission from a sales record. Confirmation consumes the hashed token atomically after expiry and purpose checks; a used or expired token cannot restore permission.
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 controls
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.
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.
Audience segmentation. The approved segment resolves to the eligible intended audience. Reject arbitrary query execution and foreign-workspace recipients.
Consent and suppression. List A withdrawal blocks A while still-permitted list B remains eligible; global withdrawal blocks both at dispatch. Reject converting ListSpecific withdrawal into global suppression; withdrawal after snapshot blocks its unsent scope and suppression removal cannot restore consent.
CRM contact sync. A repeated contact update reconciles to the same subscriber. Sales-record existence cannot grant email permission or expose unrelated contacts.
Records and postings
| Stage | Records | Effect |
|---|---|---|
| 1 Build permitted audience | SubscribersListsListMembershipsListImportsConsentEvents | Retain the stated outcome and its source evidence |
| 2 Honor preferences | UnsubscribesConsentEventsListMembershipsSuppressions | Retain the stated outcome and its source evidence |
| 3 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.
Audience Growth
Acquisition and withdrawal movements by list and source, without double counting subscribers.
Engagement Signals
Unique engagement events with human-candidate, proxy, bot and unknown classifications.
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
› honor preferences and manage suppression · build permitted audience on Subscribers, Lists, ListMemberships, ListImports, ConsentEvents
✓ Import subscribers with source and purpose evidence, deduplicate normalized addresses and preserve withdrawals.
› honor preferences and manage suppression · honor preferences on Unsubscribes, ConsentEvents, ListMemberships, Suppressions
✓ Apply a preference change to its explicit list or global scope and stop unsent queued work that is no longer eligible.
› honor preferences and manage suppression · reconcile provider state on IntegrationEvents, Sends, SendRecipients
✓ Investigate Unknown dispatches with the original provider idempotency key and message reference.