Opt-out
Qu'est-ce que Opt-out?
Cette entrée n'est actuellement disponible qu'en anglais.
An opt-out is a recipient's withdrawal of consent to further communications — typically a reply of STOP (or a standard alternative keyword) to a message, but also an unsubscribe from email, a preference-center toggle, or an opt-out the sender records itself through the Consent API. Once recorded, the opt-out binds the sender: the recipient is added to the sender's suppression list and every subsequent send attempt to that address on the enforced channels is dropped before dispatch.
More detail
Orbit records each opt-out as an entry on the organization-level suppression list with a channel scope. The full scope set is `all`, `sms`, `voice`, `whatsapp`, `email`, `push`, `telegram`, `messenger`, and `rcs`: scope `all` means the recipient is suppressed on every channel reachable at that address, while a narrower scope suppresses only the named channel — so a reply of STOP to one SMS campaign does not have to block the sender's WhatsApp or email traffic to the same contact.
The scope an opt-out carries depends on how it was captured. A bulk CSV import infers scope per row — phone and WhatsApp addresses default to `all`, unless a `channel` column overrides it — while opt-outs recorded through the Consent API or the Preference Center always write scope `all`. Phone rows in a CSV import are additionally mirrored onto the DNC list; the other entry points suppress with scope `all` without writing a separate DNC row, and the voice and dialer gates still honor them.
Orbit enforces the opt-out as a send-time gate, not a list-management convention: campaigns skip suppressed recipients, and API dispatches to a suppressed address are rejected before the message leaves the platform. The suppression list and its scopes are tenant-owned controls — the tenant decides what qualifies as an opt-out and manages its own records; the platform enforces the suppression the tenant declares.
Questions fréquentes
- What's the difference between an opt-out and a suppression list?
- The opt-out is the recipient's action — the STOP reply, unsubscribe, or consent withdrawal. The suppression list is where that action is stored: the tenant-owned set of addresses that must not be messaged again. An opt-out creates an entry on the suppression list; the list is what the send-time gate reads to drop the next send.
- Does an opt-out on one channel block the other channels?
- It can — scope `all` suppresses every channel, and phone-number opt-outs recorded with scope `all` also stop voice calls to that number. A narrowly-scoped opt-out (for example scope `sms`) blocks only that channel. The scope depends on the entry point: bulk CSV import infers scope per address type, while the Consent API and the Preference Center always write scope `all`.
- Can a recipient who opted out opt back in?
- Yes, but only through an explicit new consent signal from the recipient — a reply of START on a messaging channel, a re-subscription in the Preference Center, or an opt-in recorded through the Consent API. The sender cannot unilaterally un-suppress a recipient; re-permission requires the recipient's own fresh consent, which removes the suppression entry.
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.