Deleting a contact feels clean. For agencies running outbound on behalf of clients, clean is often the wrong instinct.
When a prospect opts out, you still need enough of a record to keep them out of future marketing sends. Wipe the row to "respect privacy" without a durable suppression layer, and the next CSV import or enrichment job can put them right back in a sequence. That is how agencies recreate the exact email the person asked you to stop.
US commercial email has a baseline here. This post is operator guidance, not legal advice. Read your counsel and the primary sources before you set policy.
What CAN-SPAM actually requires on opt-outs
The FTC's CAN-SPAM compliance guide covers commercial messages, including B2B. Among the requirements:
- Give recipients a clear way to opt out of future marketing email
- Keep that opt-out mechanism working for at least 30 days after you send the message
- Honor a request within 10 business days
- Do not charge a fee or demand extra personal information as a condition of opting out
- After someone opts out, do not sell or transfer their email address except to a company helping you comply
The Act does not say "delete the contact and hope." It says honor the request promptly and keep the mechanism usable. In practice, honoring means suppressing future commercial mail to that address for the scope of the opt-out, not treating the request as a temporary label that vanishes when you purge CRM clutter.
Agencies also inherit responsibility when they send for a client. CAN-SPAM makes clear you cannot contract away compliance just because another company hits send. Both the company whose product is promoted and the company that sends can be on the hook.
Why purge without suppression fails in multi-client shops
Agency ops produce constant delete pressure:
- Client offboarding wants "all their data gone"
- A teammate cleans bounce-looking rows without checking reply history
- A workspace reset drops contacts before suppressions are exported
- A new list upload uses email as the only key and reintroduces opted-out people
If suppression lives only as a status on the full contact profile, deleting the profile deletes the memory of the opt-out. The next find job looks successful. The next send is the violation.
A durable suppression list is the opposite shape: a minimal, long-lived record that says "do not commercially email this address for this brand/workspace," even when marketing attributes are gone.
What should survive a purge
Keep the smallest set that still blocks resend:
- Email address (or other channel identifier)
- Workspace or client brand scope
- Opt-out timestamp and source (link click, reply text, manual)
- Scope of the request when you support preference menus
- Enough audit metadata to show when and how it was honored
You usually do not need the full enrichment dossier, conversation history, or scraped bio to honor an unsubscribe. You need the stop rule to outlive the profile.
GTM's product stance matches that shape: suppression survives purge, retention is anchored to collection date, and the compliance gate will not send without a verdict plus unsubscribe URL. The gate is useless if the suppression table evaporates during housekeeping.
Operator rules that prevent reintroduction
- Suppress before you delete. Opt-out events write suppression first, then any profile cleanup runs.
- Check suppression on every import and enrichment write. A "new" contact that matches a suppressed email is not new.
- Scope by client workspace. Client A's opt-out does not automatically become Client B's, and Client B should not inherit Client A's marketing history by accident either. Isolation cuts both ways.
- Treat hard nos like opt-outs for send eligibility even when the person did not click the formal link. Route them out of sequences. Log the reason.
- Export suppressions before offboarding a workspace. If a client leaves, agree in writing what suppression artifacts transfer or remain for compliance.
Shared inbox discipline still matters
A working unsubscribe URL fails if humans re-add people from Slack screenshots. Train reply owners: "remove me," "stop emailing," and angry equivalents update suppression the same day. Do not park them in a "maybe later" column.
Honest packaging note
Agencies shopping outbound platforms should ask one blunt question: if we purge a contact, does the unsubscribe still block future commercial sends for that workspace? If the answer is a shrug, you are buying a list tool with a delete button, not a compliance-aware send path.
CTA
If you want client-isolated outbound where suppressions survive purge and sends pass a database compliance gate, join the GTM waitlist at https://trygtm.com/waitlist.
Sources
- FTC: CAN-SPAM Act Compliance Guide for Business
- GTM product notes on suppression surviving purge and the compliance gate