Opt-out & compliance
How Servus enforces consent — STOP opt-out, blocked sends to opted-out contacts, and imports that never re-subscribe.
Last updated 18 June 2026
Automatic opt-out
A contact who replies STOP (and equivalents) is opted out automatically. The portal shows the opted-out state on the contact and the conversation.
Sends are blocked at the platform
Sends to an opted-out contact are blocked everywhere — in Compose, in campaigns, and at the API. There is no way to message an opted-out contact until they opt back in. This is enforced centrally, not per-feature, so a new send path can't accidentally bypass it.
Imports never re-subscribe
Importing contacts upserts (matches by phone/email) and merges tags, but it never un-opts-out a contact. Re-uploading a list can't silently re-subscribe people who opted out — consent is sticky.
Why this matters
Honoring consent is a legal and reputational requirement (GDPR / TCPA / Meta policy) and the single biggest factor in keeping your number unblocked. Servus treats opt-out as an invariant, not a setting.