What does opted out mean? Difference from Suppressed contact

Opted out

The phrase sounds simple, but the important question is: opted out of what? A customer can be opted out of promotional SMS while remaining subscribed to marketing email, eligible for an order-status notification, or active as a customer account. Treating “opted out” as a universal profile label creates both compliance mistakes and bad customer experiences.

A status with scope

An opt-out record should answer 4 things:

1. Channel: SMS, email, WhatsApp, RCS, or another channel
2. Purpose/program: marketing, a particular alert program, or another defined message class
3. Sender/brand: which business the instruction applies to
4. Effective time and source: when the instruction arrived and how it was captured

Depending on the applicable rule and platform policy, an instruction can have broader effect than the exact message thread in which it arrived. That is one reason a system should normalize inbound opt-out intent centrally instead of letting each campaign keep its own private list.

Inactive

Inactive usually describes behavior: the person has not purchased, opened, clicked, visited, or otherwise engaged recently. It says nothing by itself about permission.

Unreachable

A number can be unreachable because it is invalid, deactivated, unsupported, or temporarily failing. That is a delivery state, not a preference.

Deleted

Deleting a profile is not a safe substitute for suppressing it. If the same phone number is imported again tomorrow, the business can accidentally lose the evidence that the person told it to stop.

Unsubscribed on another channel

An SMS opt-out does not automatically describe email preference, and vice versa. Broader legal or platform rules may affect how an instruction must be honored. The database should still preserve the channel and source rather than flattening every preference into one boolean.

Preserve the event that caused the state

Useful fields include the normalized address/number, channel, brand, scope, timestamp, raw inbound text or source event where appropriate, normalized intent, provider message/event ID, and the resulting suppression action.

For SMS, FCC rules now recognize several standardized reply words as per se reasonable revocation methods. They also prohibit a caller from treating its designated mechanism as the only possible reasonable method. Operationally, an inbound parser should recognize obvious intent rather than only one magic keyword.

What does this page teach beyond a generic glossary definition?

It teaches that opted out is a scoped, high-precedence permission state, not a synonym for inactive or deleted. Good systems retain the instruction, preserve its history, and apply it at the final send gate. We recommend that you treat every later opt-in as a new permission event.

Worked example

A person may satisfy every marketing segment rule and still be ineligible to receive a message.

• For example:

• customer bought running shoes
• segment says “purchased shoes in the last 90 days”
• campaign targets that segment
• customer replied STOP yesterday

• The correct evaluation is not “segment membership means send.” It is “segment membership makes the person a candidate, then permission and suppression gates decide whether the send may happen.”

This precedence should be enforced close to dispatch so queued messages do not escape after a late opt-out.

When an opt-out arrives while a campaign is being prepared, segment membership and an earlier eligibility snapshot are no longer enough. The dispatch worker should re-read the current permission and suppression state for the recipient, channel, sender, and program before releasing the message. If the incoming instruction has an uncertain scope, keep the original text and provider event in the record rather than assuming that an old campaign flag expresses the person's intent. A reviewable state should show which rule interpreted the instruction, when the change became effective, and which queued messages were held. That makes a late opt-out explainable during a support investigation and reduces the chance that a retry sends using stale permission. If several channels share one customer profile, evaluate each message against its own scope; a valid email preference must not override an SMS stop.

What passes and what does not

• If the customer later signs up again through a valid opt-in path, create a new permission event. The current status can return to subscribed where permitted, but the earlier opt-out should remain in history
• A new opt-in should identify the channel, sender, purpose, disclosure, and time rather than merely flipping the old opt-out record to false. That separation lets the system explain which permission event made a later message eligible
• That distinction makes audits and support tickets intelligible:
• “Why did this person start receiving texts again?”
• The answer should be reconstructable as a sequence: opted in, opted out, opted in again under a new disclosure