# OPS-057 — Log the sends you did not make

> Every send attempt suppressed because the number was opted out must be logged.

- **Rule ID:** OPS-057
- **Layer:** Operational (`OPERATIONAL`)
- **Checks:** `suppressed-send log`
- **Severity:** MEDIUM — Usually survives review, but lowers your trust score or invites manual review.
- **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:** Supply evidence only you hold
- **Required by:** T-Mobile
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/operational/ops-057/

## Why this rule exists

The suppression list proves what you intended; the suppressed-send log proves it worked. Without it there is no evidence that the check ran at all — an empty complaint file and a suppression list with a million entries are consistent with a suppression check that has been silently failing since a deploy, and an audit asks for exactly this.

## How to fix it

Log the number, the campaign and the timestamp each time a send is dropped for suppression, and retain it for the same period as the consent records. Done when you can show how many sends the list stopped last month.

## Example of a compliant value

```text
suppressed_send: msisdn +14155550134, campaign acme-marketing, at 2026-03-04T14:22Z, reason=opted_out.
```

## Check this yourself

**Can you say how many sends your suppression list stopped last month?**

1. Check whether your platform exposes suppression events at all — several drop them silently, and where that is true the evidence has to come from a pre-send check you run yourself.
2. Log the number, the campaign and the timestamp on every dropped send.
3. Retain it for the same period as the consent records.

*What wrong looks like:* An empty complaint file and a suppression list with a million entries are equally consistent with a check that has been silently failing since a deploy. Without the log there is no evidence it ever ran.

## Notes

A log inside the sending platform. What the user has to check is whether their platform exposes suppression events at all — several drop them silently, and where that is true the evidence has to come from a pre-send check they run themselves.