# OPS-043 — A revocation crosses media

> A revocation sent by text also stops robocalls to that number, and a revocation given on a call also stops texts.

- **Rule ID:** OPS-043
- **Layer:** Operational (`OPERATIONAL`)
- **Checks:** `suppression list scope across voice and SMS`
- **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:** FCC
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/operational/ops-043/

## Why this rule exists

The consumer revoked consent to be contacted by an automated system, and the FCC does not slice that by medium. Brands slice it anyway because the dialler and the messaging platform are different products with different suppression lists, so a customer who told the agent to stop calling then starts receiving texts — which reads as retaliation and is one of the most reliably complained-about patterns there is.

## How to fix it

Hold one suppression list across voice and messaging, or synchronise the two in both directions on the same day. Done when a STOP text removes the number from the dialler as well as from the campaign.

## Example of a compliant value

```text
One do-not-contact table, consumed by both the dialler and the messaging platform, keyed on the number.
```

## Check this yourself

**Does a STOP text remove the number from the dialler as well as from the campaign — and does a revocation given on a call stop the texts?**

1. Check whether one suppression list covers voice and messaging, or whether two are synchronised in both directions on the same day.
2. Most brands that have a sync built it to feed the dialler and not to be fed by it. Check the direction.

*What wrong looks like:* A customer tells the agent to stop calling and then starts receiving texts. It reads as retaliation and is one of the most reliably complained-about patterns there is.

## Notes

Two systems, neither visible from a registration. What the user has to check is the direction of any existing sync — most brands that have one built it to feed the dialler and not to be fed by it.