A registered campaign must expect to carry traffic
The requirementstatement
A campaign should be registered only when it will actually send; sustained inactivity triggers dormancy suspension.
- Severityseverity
- MediumMEDIUMUsually survives review, but lowers your trust score or invites a manual look you would rather avoid.
- When it bitesphase
- Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
- What is checkedobject
- campaign.description
- Where it liveslayer
- OperationalOPERATIONAL
- How Ekas settles itdetectability
- AI · formAI_FORM
- A semantic question about what you wrote: whether a description matches a use case, whether a name looks like a filed entity. Judged by a model against written criteria.
- What the fix involvesfailureClass
- Fix the fieldRETRY_FIELD
- A better value in the form fixes it. Ekas can rewrite it and re-check.
- Who requires itauthorities
- TCRT-Mobile
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
Registering ahead of a programme that does not exist yet wastes a non-refundable vetting fee and risks a dormancy suspension after roughly two weeks of silence. It also produces the empty-shell registrations that make reviewers stricter with everyone.
How to fix itremediation
Register when you have subscribers and a send schedule. If the programme is seasonal, plan at least occasional traffic to avoid dormancy suspension.
A compliant exampleexample
Weekly promotional sends beginning the week of approval.
Rules you will hit next
6 other rules read campaign.description. Fixing one field to satisfy a single rule is how a resubmission trades one rejection for another, so read these before you change anything.
CMP-035The description must describe this programme, not messaging in generalBlockingBLOCKINGCMP-037The description must name the business that sends the messagesBlockingBLOCKINGCMP-DESC-LENCampaign description must be 40–4096 charactersBlockingBLOCKINGMSG-DESC-QUALITYCampaign description must explain who, what, and how they opted inBlockingBLOCKINGCMP-041The description must say how often the messages comeHighHIGHCMP-042A programme that asks for money must say soHighHIGH
OPS-159 is one of 139 operational rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.