Suppression and Consent Map (Onboarding)

Suppression and Consent Map (Onboarding)

1. 01

   Pull the client's current suppression lists from every sending system before building any new journey

   Unsubscribes, hard bounces, spam complaints, and legal holds often live in three or four places. Reconcile them into one master file so a new flow cannot re-contact someone who opted out six months ago.

2. 02

   Document consent provenance per channel: email, SMS, push, and WhatsApp each carry different rules

   A customer who opted into email at checkout has not consented to SMS. Record where each opt-in was captured, the timestamp, and the exact language shown at capture.

3. 03

   Map regional constraints to the client's actual buyer geography

   GDPR, CASL, and TCPA impose different quiet hours and consent standards. If the client sells into the EU, quiet hours and re-permission rules apply even when the agency and platform sit in the US.

4. 04

   Flag every automation that fires without a human review gate

   Predictive systems increasingly trigger sends autonomously rather than waiting for approval. List each one and mark whether a wrong send would be recoverable or a compliance event.

5. 05

   Set a holdback control group for every recovery and winback sequence

   A 5% holdback lets the agency prove incremental revenue rather than claiming credit for orders that would have happened anyway. Snagr's Polar.sh recovery tooling uses this exact 5% control-group method, and the same discipline applies to any platform.

6. 06

   Write the suppression audit into the client contract as a recurring monthly task

   Consent decays. New unsubscribes arrive weekly, and a list that was clean at onboarding is stale within a quarter. Put the re-audit on the retainer scope so it is billable rather than absorbed.