# OPS-150 — Send only the message types the subscriber agreed to

> Message types the subscriber did not consent to must not be sent — a survey to an OTP-only list, marketing to a transactional opt-in.

- **Rule ID:** OPS-150
- **Layer:** Operational (`OPERATIONAL`)
- **Checks:** `message type against the consent record scope`
- **Severity:** BLOCKING — Breaking this rule gets the submission rejected outright.
- **When it bites:** Falls due after approval, once you are live and sending
- **How it is detected:** Not knowable before submission — reported with its deadline
- **Fix type:** Wait on an external system or a required interval
- **Required by:** AWS, CTIA
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/operational/ops-150/

## Why this rule exists

Consent has a scope, and the scope is the category described at opt-in, not the sending platform's idea of a contact list. Sending outside it is unconsented messaging however carefully the original opt-in was collected, and it is the failure that turns a well-run programme into a complaint source, because the recipients did opt in — to something else.

## How to fix it

Store the consent scope on the record and check it before a send rather than segmenting by list membership. Done when a marketing send cannot include numbers whose consent was transactional.

## Check this yourself

**Is the consent scope stored on each record — or is consent a boolean?**

1. Look at the consent record itself. Where consent is a boolean, this rule cannot be satisfied by any amount of care at send time.
2. Check the scope before a send rather than segmenting by list membership.
3. Done when a marketing send cannot include numbers whose consent was transactional.

*What wrong looks like:* A survey to an OTP-only list. The recipients did opt in — to something else — which is what turns a carefully run programme into a complaint source.

## Notes

A comparison between a send and a stored scope. What the user has to check is whether the scope is stored at all — where consent is a boolean, this rule cannot be satisfied by any amount of care at send time. OPS-209 and OPS-199 cover recording it.