STOP and HELP volumes are a standing report

The requirementstatement

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

Severityseverity: HighHIGHRejected by at least one carrier or provider, and a common cause of failure at the rest.
When it bitesphase: After you are livepostFalls due once you are sending: STOP handling, quiet hours, suppression, record retention.
What is checkedobject: per-campaign keyword response metrics
Where it liveslayer: OperationalOPERATIONAL
How Ekas settles itdetectability: Post-submissionUNDETECTABLE_PRE_SUBMISSION; The subject does not exist yet at submission time: a reply window, an expiring PIN, a queue position. Reported with its deadline.
What the fix involvesfailureClass: Wait on someone elseTERMINAL_EXTERNAL; Needs an external system or a waiting period, such as IRS propagation, a vetting result, or a carrier queue.
Who requires itauthorities: T-Mobile
When it appliesapplicabilityText: Applies to every 10DLC registration.

Why this rule existsrationale

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 itremediation

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.

A compliant exampleexample

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

Check this yourselfattestation

No tool can settle this one for you. Here is the check, and what wrong looks like.

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

1Break STOP and HELP counts out per campaign rather than per account, and keep the series long enough to see a trend.
2Confirm 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.

Notesnotes

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.

Rules you will hit next

Other operational rules at the same severity. A registration is judged as a whole, not rule by rule.

OPS-034A programme in another language still owes the English keywordHighHIGH OPS-035The mandatory keywords must work over MMS tooHighHIGH OPS-044Suppression is brand-wide, not per numberHighHIGH OPS-047A state may give you less time than the federal limitHighHIGH OPS-052Silence after a scope question revokes everythingHighHIGH OPS-053A STOP answering a scope question must not be answered with anotherHighHIGH

All operational rules

OPS-068 is one of 139 operational rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.