How to build a suppression list that never emails an unsubscriber

Keep one master list of opt-outs, bounces and complaints, and check it twice: when you freeze the audience and when each email sends.

An admin approves every new account by hand. Nothing is created until then. We reply by email; no newsletter, no sequence.

app.salescrew.io/inbox
The unified reply inbox with classified threads

The short answer

  • A suppression list for cold email holds every unsubscribe, hard bounce, spam complaint and opt-out made through another channel, in one master list.
  • A suppression list only works if it is checked twice: when an audience is frozen for a campaign, and again at the moment each email sends.
  • CAN-SPAM requires you to honour an opt-out within 10 business days and keep the opt-out link working for 30 days after sending, per the FTC's compliance guide.
  • Every sending tool you use must read the same list. Two tools with two lists means an opt-out in one gets ignored by the other.

Why most suppression lists fail at the send, not the build

Almost every sending tool keeps a suppression list. The failures come from timing and from splitting. You freeze a list for a cadence and check suppression once. Then the cadence runs for three weeks. In that window a contact can unsubscribe from another email, or their address can start bouncing. Without a second check, step 3 goes out anyway.

Splitting is the other leak. Your team runs a cold email tool, a CRM sequence and maybe a newsletter, each with its own list. Someone unsubscribes in one, and the other two keep going. From their side, you ignored them. From yours, every tool did its job.

What belongs on a suppression list, and when to add it

EventSuppress?Why
Unsubscribe or opt-out replyYes, at onceCAN-SPAM gives you 10 business days at most; faster is safer
Hard bounce (address does not exist)Yes, at onceHard bounces above 2% get senders throttled
Spam complaintYes, at onceGoogle asks senders to stay below 0.3%; audit the source list too
Soft bounce (temporary failure)After repeatsRetry first; suppress when it keeps failing
Opt-out by phone, chat or ticketYes, at onceThe person's wish is the same on every channel

Legal timings from the FTC's CAN-SPAM compliance guide; Gmail spam rate from Google's email sender guidelines; bounce ceiling from Nadav Shanun, Indie Hackers, May 2026. Checked September 2026.

Build the suppression list in five steps

  1. 1

    Start one master list

    Pick one system as the source of truth for opted-out, bounced and complained addresses. Import every old unsubscribe export you can find from past tools.

  2. 2

    Add entries automatically

    Connect unsubscribes, hard bounces and spam complaints so they land on the list the moment they happen, with no weekly CSV upload.

  3. 3

    Capture other channels

    Give your team a way to add a contact who opted out by phone, chat or a support ticket. One field or one button is enough.

  4. 4

    Check at audience freeze

    Remove suppressed contacts when you freeze an audience for a campaign, so the list you review is the list you send.

  5. 5

    Check again at send

    Re-check every email against the list at the moment it sends, so an opt-out during a multi-week cadence stops the next step.

How SalesCrew enforces suppression

SalesCrew is our product, and it keeps one suppression list for each instance. Suppression is enforced when you freeze an audience and re-checked at the moment each email sends. Unsubscribes and bounces from your connected inboxes feed the list automatically, and the mailbox-pool sender turns every bounce or complaint into a suppression.

Your team can add or remove an entry from the app, and an AI client can do the same through the MCP tools suppression_add and suppression_remove. Every change lands in the audit log with who made it. The data bank and cadences pages show where the check runs, and plans start at $299 a month on the pricing page.

Suppression is how you honour opt-outs, and the duty stays yours

A working list stops the sends. The duty to honour opt-outs under CAN-SPAM, GDPR and similar laws stays with the sender, whichever tool sends the email. This is not legal advice.

Questions

How fast do you have to honour an unsubscribe?
Within 10 business days under CAN-SPAM, per the FTC's compliance guide, and your opt-out link must keep working for at least 30 days after you send. Treat 10 days as the legal maximum, not the target. A suppression list that updates the moment someone opts out removes the question entirely.
What should go on a suppression list besides unsubscribes?
Hard bounces, spam complaints and anyone who asked not to be contacted through another channel, such as a call or a support ticket. Soft bounces, which are temporary failures, get retried first and suppressed only after they repeat on the same address.
Is checking suppression when you build the list enough?
No. A 3-week cadence gives a contact 3 weeks to unsubscribe or start bouncing after the list was frozen. Checking only at build time is the most common way a suppressed contact still gets the next step. Check again at the moment each email sends.
Do all my sending tools need the same suppression list?
Yes. If you send from two tools with two lists, an opt-out in one does nothing in the other. To the person who unsubscribed, that looks exactly like being ignored. Keep one master list and make every tool read from it before it sends.