Approved samples do not license prohibited content

JSONMarkdown

The requirementstatement

Prohibited content must not appear in live traffic regardless of what the approved samples showed.

Severityseverity
BlockingBLOCKINGBreaking this rule gets the submission rejected. There is no partial credit.
When it bitesphase
After you are livepostFalls due once you are sending: STOP handling, quiet hours, suppression, record retention.
What is checkedobject
live message content
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
Hard stopHARD_STOP
Not remediable. Resubmitting will not help, and anyone offering to fix it is selling you a rejection.
Who requires itauthorities
T-MobileAT&TCTIATCR
When it appliesapplicabilityText
Applies to every 10DLC registration.

Why this rule existsrationale

Approval is granted against the samples, and operators read it as approval of the campaign — so a programme whose samples were clean starts sending content the category prohibits, on the basis that the campaign was approved. Carriers scan live traffic, and a violation there is enforced against the account rather than the campaign.

How to fix itremediation

Apply the prohibited-content rules to every template before it goes live, not only to the ones submitted for registration. Treat the registered samples as examples of a standard rather than as the extent of it.

Check this yourselfattestation

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

Is there a review step that applies the prohibited-content rules to new templates, not just to the ones submitted for registration?

  1. 1Find the step. Approval was granted against the samples, and operators read it as approval of the campaign.
  2. 2Apply the MESSAGE_CONTENT prohibited-content categories to every template before it goes live.
  3. 3Treat the registered samples as examples of a standard rather than as the extent of it.

What wrong looks like: A programme whose samples were clean starts sending content the category prohibits, on the basis that the campaign was approved. Carriers scan live traffic and enforce against the account rather than the campaign.

Notesnotes

Live content we never see. What the user has to put in place is a review step on new templates — the MESSAGE_CONTENT prohibited-content family states the categories, and this rule is the reminder that approval did not exempt anything from them.

Rules you will hit next

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

OPS-026The universal opt-out keyword set must be declaredBlockingBLOCKINGOPS-027Opt-out keyword handling must be declared, not assumedBlockingBLOCKINGOPS-029A revocation must survive punctuation, case and surrounding wordsBlockingBLOCKINGOPS-031A plainly-worded opt-out counts even with no keyword in itBlockingBLOCKINGOPS-033STOP must never come back as an errorBlockingBLOCKINGOPS-037On a shared address, STOP must stop everythingBlockingBLOCKING

All operational rules

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

Reading the rules is the easy part.

Ekas runs every rule that gates approval, 823 of these 915, against your registration before it reaches the carrier. It reads your site, your policy pages and your opt-in the way a reviewer would, and hands you the fix, not just the verdict.

Talk to UsHow 10DLC works