Suppression usually lives in the wrong place. It sits in a spreadsheet next to the list, or in a CRM validation rule that fires after a rep has already written the email, or in a marketing automation exclusion that covers campaigns but not manual outbound. Each of those catches the conflict after the work is done.
Applying it at search time means the conflict never enters the list. The rep sees a clean set of accounts and never has to know which ones were removed, which is the only version of this that survives contact with a busy quarter.
It is also the cheapest form of credit control available. A prospecting list built without suppression spends reveal credits on contacts at accounts you already own, and nothing in the output distinguishes those from genuine prospects. The waste is invisible until someone reconciles the list against the CRM, which is usually never.
Data drawn from 290M+ verified contacts, sourced and processed under GDPR, CCPA, SOC 2 Type II, ISO 27001, ISO 27701, and TRUSTe Responsible AI. Full detail in the Trust Center and privacy notice.
FAQ
How do I exclude existing customers from a prospecting list?
Pass their domains as a suppression list alongside your ICP filters, so the exclusion happens at search time rather than as a cleanup step afterwards. The advantage over filtering later is that the contacts never appear, so nobody works them and no reveal credits are spent on them.
Does suppression cost extra credits?
No. You are narrowing a search rather than running a second one, so a suppressed search costs the same as an unsuppressed one — 1 credit per batch of up to 25 records returned. The saving comes from the reveals you no longer make: 380 suppressed contacts would have cost 380 credits to reveal by email, or 2,280 with phone numbers.
What should go on the suppression list?
Four groups, and teams usually remember only the first. Current customers. Open opportunities, including ones another rep owns. Accounts assigned to a different territory or segment. And partners, resellers, and investors, who are frequently the worst accounts to prospect into by mistake.
Why did my suppression list remove nothing?
Almost always a typo or a formatting problem in the input rather than a clean database. Suppression matches exact domains, so a company name instead of a domain, a URL with a protocol prefix, or a misspelling will silently match nothing. A zero removal count on a long customer list should be treated as a failed run, not a good one.
Will it catch subsidiaries and rebrands?
No. Exclusion is exact-domain, so a subsidiary operating under its own domain, a company that rebranded after your list was built, or a regional domain of the same parent will all come back as clean prospects. The prompt flags near-matches for review, but the durable fix is keeping the suppression list current rather than relying on the search to infer relationships.
Where should the suppression list live?
Wherever your account ownership is already recorded, exported fresh each time rather than maintained separately. A suppression list that is a copy of the CRM will drift from the CRM, and the day it drifts is the day a rep emails a customer. If you are running this regularly, pull the domains at run time rather than pasting from a saved file.
