# OPS-058 — Re-read the inbound log for opt-outs the handler missed

> Inbound message logs must be reviewed on a schedule for revocations the keyword handler did not catch, and those subscriptions terminated.

- **Rule ID:** OPS-058
- **Layer:** Operational (`OPERATIONAL`)
- **Checks:** `inbound log review`
- **Severity:** HIGH — Rejected by at least one carrier or provider, and a common cause of failure at the rest.
- **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:** CTIA
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/operational/ops-058/

## Why this rule exists

No intent classifier catches everything, so the question is not whether some revocations are missed but whether anybody ever finds out. A scheduled sweep converts a silent miss into a caught one — and finding three a month is a working programme, while finding none usually means nobody is looking rather than that the handler is perfect.

## How to fix it

Schedule a review of inbound messages that produced no keyword match, suppress anything that reads as a revocation, and record when the review ran. Done when the review has a date, an owner and a finding count each time.

## Example of a compliant value

```text
Weekly: export unmatched inbound messages, review, suppress, record "reviewed 2026-03-06, 4 revocations found".
```

## Check this yourself

**Does the review of unmatched inbound messages have a date, an owner and a finding count each time it runs?**

1. Schedule the sweep over inbound messages that produced no keyword match.
2. Suppress anything that reads as a revocation, and record when the review ran and what it found.
3. Finding three a month is a working programme. Finding none usually means nobody is looking.

*What wrong looks like:* No classifier catches everything, so the question is whether anybody ever finds out. Without the review record, a missed revocation looks like the norm rather than an exception.

## Notes

A recurring job over data we never see. What the user has to do is own the schedule and keep its output — the review record is what shows a missed revocation was an exception rather than the norm.