Skip to main content
Suppression = identity on the workspace do-not-contact list. It is not a tag or marketing preference. It is the red card that blocks sending before you spend credits or call the provider.

​
What is a suppression?

It is an entry on the global list that says: “do not send a message to this email, phone number, Telegram @, or Instagram @.” The system checks this list before enqueueing and again in the worker. Analogy: imagine a notebook at the front desk with names that cannot receive visitors. No matter which courier (channel) you pick — if the name is in the notebook, the message does not go out.

​
Suppression × tag × topic × unsubscribe

STOP in SMS creates a global phone suppression (SMS, WhatsApp, RCS, and voice). Unsubscribe and one-click email are marketing preferences — they do not block other channels on their own.

​
Types and channels

Each entry has type + value, normalized before saving:

​
Common reasons

Additions are idempotent: the same active identity does not trigger another suppression.added event.

​
How it works in practice

  1. Open Audience → Suppressions (members can view; OWNER/ADMIN add, import, and remove)
  2. Add manually or import CSV/XLSX (type, value, reason, channel)
  3. At send or campaign time, suppressed contacts do not enter the queue
  4. The item ends with RECIPIENT_SUPPRESSED — no credit and no provider call
Removing a suppression re-enables sending immediately. If the address generates bounce or complaint again, it may be suppressed again automatically.

​
In the API

Scopes suppressions:read and suppressions:write. Events: suppression.added, suppression.removed, message.suppressed.

​
Next steps