# OPS-114 — A programme relying on the delivery exemption still owes an opt-out

> A campaign relying on the package-delivery exemption must offer an opt-out and honour it within six business days.

- **Rule ID:** OPS-114
- **Layer:** Operational (`OPERATIONAL`)
- **Checks:** `campaign.sample[] + campaign.message_flow`
- **Severity:** HIGH — Rejected by at least one carrier or provider, and a common cause of failure at the rest.
- **When it bites:** Gates approval — get this wrong and registration is refused
- **How it is detected:** AI judgement over the submitted form
- **Fix type:** Fix the field — a better value in the form clears it
- **Required by:** FCC
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/operational/ops-114/

## Why this rule exists

The exemption removes the need for prior express consent, and brands read that as removing the consumer's ability to refuse — which is the one thing it does not do. The FCC attached conditions to every exemption it granted, and the opt-out is the condition that gets dropped, because a delivery notification feels like something nobody would want to stop.

## How to fix it

Carry opt-out instructions in the exempt messages themselves and state the honouring window in the flow. Done when a delivery notification tells the recipient how to stop and the flow says how quickly that takes effect.

## Example of a compliant value

```text
Acme Coffee: your order #4471 ships today, track at acmecoffee.com/t/4471. Reply STOP to stop delivery texts.
```

## Notes

Applies only where a campaign claims one of the FCC's exempted categories, which the registration has no attribute for. The condition sits in the criteria, and the note records that: a campaign that never invokes an exemption is not failed by this rule.