Docs
OverviewPlatformPlatform APIA2P Messaging API
AI & MCP
Open dashboard
OverviewPlatformPlatform APIA2P Messaging API
AI & MCP
Getting started
  • Overview
  • Start guide
  • Project status
  • Concepts
AI
  • Iris
  • AI writing
  • Connect your AI (MCP)
Channels
    • Countries & coverage
    • Senders & registration
    • Essentials
    • Countries & availability
    • What is RCS
    • Senders & verification
    • Agent profile
    • Best practices
    • Acceptable use
    • SMS fallback
  • WhatsAppSoon
  • Compliance
  • Countries
    • Austria
    • Brazil
    • Canada
    • Colombia
    • France
    • Germany
    • India
    • Indonesia
    • Mexico
    • Netherlands
    • Peru
    • Singapore
    • Spain
      • Authorise the alias
      • Register directly
      • Without a certificate
      • Rejected alias
    • Ukraine
    • United Kingdom
    • United States
    • Other countries
Marketing
  • Campaigns
    • Creating a campaign
    • Targeting
    • Test sends
    • Delivery
    • Compliance
    • Managing campaigns
    • Campaign analytics
  • Flows
    • Building a flow
    • Templates
    • Triggers & entry
    • Sending messages
    • Waits
    • Branches
    • Contact updates
    • Goals & exits
    • Versions & publishing
    • Managing flows
    • Monitoring
    • Analytics
    • Limits
  • Sequences (legacy)
    • Managing sequences
    • Sequence analytics
Data
  • Audience
    • Contacts
    • Audience table
    • Segments
    • Attributes & events
  • Integrations & data sources
    • Managing sources
    • CSV import
    • API & webhooks
    • Event best practices
    • Integrations
      • Shopify
      • Klaviyo
      • WooCommerce
      • PrestaShop
      • Magento
      • HighLevel
      • Hotmart
      • ActiveCampaign
      • Zoom
      • Facebook Leads
      • Google Sheets
      • Google Contacts
      • MailChimp
      • MailerLite
      • Intercom
      • Make
      • Zapier
      • Activepieces
      • n8n
      • Pabbly Connect
      • OptiMonk
      • Paperform
      • StockAgile
      • Typeform
  • Consent
    • How consent works
    • Subscription attributes
    • Shared consent
    • Opt-outs
    • Manage via API
Analytics
  • Audience
  • Messages
  • Sales
  • Reports
Settings
  • Project settings
    • Brand profile
    • Senders
    • Short links
    • Unsubscribe links
    • Test numbers
    • Attribution
    • Project memory
  • Developers & Apps
    • API tokens
    • Third-party apps
    • Data access
    • Connected apps
  • Organization
    • General
    • Legal profiles
    • Team
    • Localization
  • Billing
    • Plans
    • Cost calculator
    • Balance
    • Invoices
    • Pricing
    • Account
    • Theme
    • Security
    • Notifications
    • Language & currency
DashboardSupportinstasent.com

Data · Consent

Opt-outs & reactivation

How contacts opt out — STOP in markets with inbound SMS, an unsubscribe link elsewhere — how a repeated opt-out escalates to suppression, who can bring a contact back, and how to set up your unsubscribe links.

On this page▾
  • How a contact opts out
  • Importing a list of opt-outs
  • From opt-out to suppression
  • Reactivation: who can bring a contact back
  • Setting up your unsubscribe links

A contact has two ways to stop receiving marketing, depending on the market: by replying STOP where inbound SMS is available, or by clicking an unsubscribe link where it isn't. The good news is that the first opt-out isn't final — it can be reversed, and only when the person insists, with a second opt-out, does it become full suppression. This page covers how contacts opt out, how that opt-out escalates, who can reactivate a contact, and how to set up your unsubscribe links.

How a contact opts out

The mechanism depends on whether the destination market supports inbound SMS:

  • Markets with inbound SMS (for example the United States and France) — the contact replies STOP to opt out, and START to opt back in. Keywords are configurable per channel (see Compliance).
  • Markets without inbound SMS — there's no reply channel, so each send must carry an unsubscribe link instead. Clicking it opts the contact out.

Every marketing send needs to include the opt-out mechanism that actually works in its market — a STOP instruction where inbound SMS exists, an unsubscribe link where it doesn't.

Importing a list of opt-outs

Opt-outs you collected outside Instasent, for example people who complained or asked you by email, can be brought in with a CSV. Each one is imported as a marketing opt-out (the preference set to declined), not as a suppression, so it counts as an opt-out under the No opt-out and Opt-in policies. How to prepare the file and which policy respects it is in Importing consent.

From opt-out to suppression

An opt-out doesn't suppress a contact on the first request. What it does depends on the campaign's consent policy:

  • Under No opt-out or Opt-in, the first STOP (or unsubscribe-link click) leaves the contact as declined marketing (opted out) — they stop receiving marketing but stay subscribed. A second opt-out, from a contact who had already declined, escalates to suppression.
  • Under Basic, a STOP goes straight to suppression in a single step, because Basic ignores the marketing preference and suppression is the only way to honour the request.

This escalation is the same whether the contact replied STOP or clicked an unsubscribe link. The full policy-by-policy breakdown is in Compliance policies — this page describes the escalation; that page owns the policy table.

Clicking an unsubscribe link does not suppress the contact outright. It records an opt-out (marketing preference set to declined), following the same escalation as a STOP reply. Suppression only happens on a repeated request — or immediately under a Basic campaign.

stateDiagram-v2
    state "Opted out" as OptedOut
    [*] --> Active
    Active --> OptedOut: STOP / unsubscribe (No opt-out or Opt-in policy)
    Active --> Suppressed: STOP under a Basic send
    OptedOut --> Suppressed: STOP / unsubscribe again
    OptedOut --> Active: START / opt-in (contact or your team)
    Suppressed --> Active: reactivate (your team or API only)

    class Suppressed destructive

Reactivation: who can bring a contact back

Reactivation depends on the contact's current state and on who is doing it:

  • A contact who declined marketing can be brought back to it — by the contact (replying START, or through a re-subscription flow) or by your team/the API.
  • A suppressed contact can only be reactivated by your team or via the API. A contact can't lift their own suppression — START reverses an opt-out, not a suppression.
  • A contact who is subscribed and accepts marketing — reactivating has no effect.

In the panel, you reactivate a contact from the Subscribed / Accepts marketing checkboxes on their profile; programmatically, with the reactivate operation (see Manage via API).

Reactivating a contact who opted out or was suppressed only makes sense when you have a genuine basis to message them again — a new opt-in, an explicit request. Reactivating to message someone who asked not to be contacted defeats the purpose of the model.

Setting up your unsubscribe links

Unsubscribe links are configured under Settings › Project, in the Tools group, on the Unsubscribe-links page. The campaign editor inserts the link with the unsubscribe tag.

Two things you control there:

  • Tracking domain — the domain the unsubscribe link uses. The default is System default; you can switch to a branded domain so the link carries your own domain instead of Instasent's. The catalog of domains is shared project-wide.
  • Opt-out prefix — the keyword shown before the unsubscribe URL.
Unsubscribe links: choosing the tracking domain and the opt-out prefix.

For SMS and RCS, an opt-out applies to both channels — they share consent. Whether an opt-out stays on its channel or propagates to every channel is the per-channel vs global scope setting, in Compliance.

Last updated October 14, 2026

PreviousShared consentNextManage via API
  • How a contact opts out
  • Importing a list of opt-outs
  • From opt-out to suppression
  • Reactivation: who can bring a contact back
  • Setting up your unsubscribe links

© 2026 Instasent

Privacy PolicyTerms & ConditionsCookie PolicyLegal Notice
All systems operational