Zintara suppression integration: preserve the exclusion across systems

Define the decision

The current general webhook subscription choices are reply.received and bounce.detected. There is no general unsubscribe subscription in that interface. Slack’s unsubscribe alert is a different notification channel and is not a structured durable synchronization feed.

Work through the procedure

1. Identify every system capable of sending to the contact.
2. Choose an approved source of truth for exclusions.
3. Map the supported API and manual controls without inventing a blocklist API-key scope.
4. Make destination exclusion updates repeat-safe.
5. Reconcile missed or ambiguous changes before allowing future enrollment.

Worked example

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

Bounce event received → destination suppression reviewed and applied
Unsubscribe event requirement → current general webhook does not provide it
Design action: explicit reconciliation or operator handoff, not a guessed event subscription

Read the result

The gap is a design constraint, not a reason to treat missing notifications as consent to continue. Pausing one campaign also does not necessarily exclude the address from every future workflow.

Check before moving on

1. Test re-import of an excluded address.
2. Keep exclusion reason and source visible to reviewers.

Limits and next action

Do not remove an exclusion just because a later lead import says new. If complete automated propagation is mandatory, the current contract needs additional capability before adoption.

Source: Zintara implementation and product context