Suppression list
What is Suppression list?
A suppression list is the set of addresses — phone numbers, email addresses, or channel-specific IDs — a business has resolved should never receive another message from it, whether because the recipient opted out (STOP), the address landed on a do-not-call registry, or a per-tenant policy gate applies regardless of the recipient's own opt-in. The platform treats the list as a hard send-gate: any suppressed destination in a campaign, contact import, or API dispatch drops before delivery.
More detail
Suppression lists are distinct from DNC registries: the registry is a public central list a recipient joins once and every sender then has to respect; the suppression list is tenant-specific — it's the opt-outs your business itself captured (via STOP, unsubscribe, or complaint) plus any lists you uploaded. A sender enforces both layers independently, and a public DNC registry never substitutes for the opt-outs the platform itself rescues.
Orbit's suppression pipeline treats the list as the destination drop: a number marked suppressed is removed from every outgoing campaign or API call before dispatch, and bulk-import accepts CSV with per-row validation and dedup so internal lists can be managed without API-integration work. The gate is tenant-owned — the tenant controls the list as its own; Orbit only enforces suppression once the tenant has declared it.
Frequently asked
- What's the difference between a suppression list and a DNC registry?
- The DNC registry is a public central list the recipient joins once; the suppression list is a tenant-owned filtered list it uploads or aggregates (typically captured STOP opt-outs from the platform itself). Both are enforced independently at send-time and neither substitutes for the other — a compliant sender reads both, does not infer one from the other.
- Does a suppressed address stay suppressed forever?
- Generally yes — the tenant's own list persists until it explicitly re-permits the address (a re-enabled number after a re-verified opt-in). Public registry entries refresh on their defined cycle, but the tenant-specific suppression list holds longer; the gate only honours a re-permit once.
- Why does suppression become a send-gate instead of an upstream filter?
- Because the delivery path must be dropped at dispatch, not just listed for exclusion: a destination the tenant suppressed must never reach wires even if a subsequent campaign or address-call mistakenly targets it. Orbit's send-time suppression enforces that at dispatch regardless of how the campaign or API was invoked.
See also
Build it on Orbit
Voice, messaging, email, video, and AI agents on one platform and one pay-as-you-go bill. Start free — no credit card required.