The campaign must not duplicate another campaign on the account
The requirementstatement
A campaign whose description, name, website, message flow and samples all match an existing campaign is a snowshoeing signal.
- Severityseverity
- HighHIGHRejected by at least one carrier or provider, and a common cause of failure at the rest.
- When it bitesphase
- Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
- What is checkedobject
- campaign fields across the account
- 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-MobileTwilio
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
How to fix itremediation
Consolidate duplicates into one campaign, or differentiate them by genuine audience and content. Where you need more numbers for volume, request a number pool on one campaign rather than cloning it.
A compliant exampleexample
One MARKETING campaign with a number pool, rather than four identical MARKETING campaigns.
Notesnotes
Rules you will hit next
Other operational rules at the same severity. A registration is judged as a whole, not rule by rule.
OPS-136 is one of 139 operational rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.