Suppression across clients
ForgeSend's baseline suppression list (see Compliance & suppression) is workspace-scoped by design — suppressing an address in one workspace has zero effect on any other. Agency Groups add two deliberate exceptions that cross that boundary, at two genuinely different scopes: one stays inside a single agency, the other reaches every workspace on ForgeSend.
On this page
Agency-wide bounce suppression
When an email address hard-bounces in one client's workspace, ForgeSend automatically blocks sending to that same address in every other client workspace under the same Agency Group.
Only hard bounces trigger this — a contact who unsubscribed or opted out in one client's workspace is not automatically suppressed anywhere else, that stays entirely workspace-local. A workspace with no Agency Group at all has no siblings to check against, so this check is a no-op for it.
Which specific sibling workspace the bounce happened in is surfaced only in the server log line, never in anything client-facing — the skip reason shown on the blocked send job just reads "Skipped: contact hard bounced elsewhere in this agency."
Platform-wide spam-complaint suppression
If the same email address is manually flagged as a spam complaint by 2 or more different senders anywhere on ForgeSend, sending to that address is blocked everywhere — not limited to one agency, and not limited to workspaces that belong to an Agency Group at all.
This is genuinely unscoped — unlike the bounce check above, there's no agency boundary here at all. A complaint from a completely unrelated agency's client counts exactly the same as one from a sibling workspace under your own agency.
Spam complaints are recorded manually, and the rule they enforce is "once 2+ different senders have flagged the same address, block it everywhere." Which sender(s) flagged the address is never shown or logged anywhere the block itself is visible — the skip reason just reads "Skipped: this contact has been flagged for spam complaints," with no workspace identity attached to it, by design.
Where each check runs
Both checks are enforced live, immediately before a send actually goes out. Agency-wide bounce suppression is additionally checked earlier — when leads are enrolled into a campaign, and in the pre-enrollment preflight count — so a blocked contact shows up as a "skipped" count before you ever launch, not only silently at send time. Platform-wide spam-complaint suppression is enforced only at send dispatch, not at enrollment.