Unsubscribe propagation: verify exclusion across pending campaigns

Define the decision

Ask where another message could originate: active sequences, follow-ups, proposed imports or manual handoffs. Preserve the request's scope and evidence so a teammate does not interpret the person as merely inactive. Follow the recipient across campaign containers instead of assuming the inbox thread defines the entire scope.

Work through the procedure

1. Identify the address and request using the recipient's words and context, not only a sentiment label.
2. Confirm the appropriate suppression or unsubscribe state through supported controls. Record source and time without copying unnecessary conversation data.
3. Review other enrollments and proposed lists, especially work resumed after an outage.
4. Investigate any later reported message by comparing event times and attempt evidence. Distinguish already accepted mail from newly initiated work.

Worked example

The following is a synthetic example for this procedure, not a customer result or performance benchmark.

Recipient appears in Campaigns A and B
Opt-out arrives through A
Review: durable exclusion, B's pending step, new import staging
Later message reported: compare provider acceptance with suppression time
Renaming A's status alone is insufficient evidence

Read the result

A message accepted before an exclusion can appear later at its destination. That timing can explain an observation, but it does not justify ignoring subsequent work that should stop. Correlating evidence gives a more useful answer than either dismissing the report or assuming every later arrival proves a new send was initiated.

Check before moving on

1. Compare exact addresses and investigate aliases separately.
2. Preserve exclusions through cleanup and reimport.
3. Include manual outreach owners in the relevant handoff.

Limits and next action

This is an operations procedure, not jurisdiction-specific legal advice. Zintara checks blocklist and unsubscribe state during sending. Verify the affected history; deleting a thread or pausing one campaign does not by itself establish that the recipient's request has been fully recorded.

Source: Zintara product and contact workflow context