# OPS-068 — STOP and HELP volumes are a standing report

> STOP and HELP response volumes must be monitored per campaign as an ongoing obligation.

- **Rule ID:** OPS-068
- **Layer:** Operational (`OPERATIONAL`)
- **Checks:** `per-campaign keyword response metrics`
- **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:** T-Mobile
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/operational/ops-068/

## Why this rule exists

Aggregate rates hide the campaign that is going wrong. A brand running six programmes sees a healthy overall opt-out rate while one of them is generating almost all of it, and the per-campaign view is what makes that visible early enough to fix. It is also what the connectivity partner is expected to hold, so being unable to produce it is itself a finding.

## How to fix it

Break STOP and HELP counts out per campaign rather than per account, and keep the series long enough to see a trend. Done when you can answer "which campaign is driving this" without an export.

## Example of a compliant value

```text
Monthly: acme-marketing 0.4% STOP / 0.1% HELP; acme-orders 0.05% STOP / 0.3% HELP.
```

## Check this yourself

**Can you answer "which campaign is driving this" without an export?**

1. Break STOP and HELP counts out per campaign rather than per account, and keep the series long enough to see a trend.
2. Confirm the platform attributes inbound keywords to a campaign at all — where several campaigns share a number, many do not.

*What wrong looks like:* A brand running six programmes sees a healthy overall opt-out rate while one programme generates almost all of it. Being unable to produce the per-campaign view is itself a finding.

## Notes

Metrics from live traffic. What the user has to confirm is that their platform attributes inbound keywords to a campaign at all — where several campaigns share a number, many do not, and the attribution has to be rebuilt from the outbound history.