Attributes that do not apply to the registration type must be empty
The requirementstatement
Conditionally-allowed fields must not be populated when they do not apply to the chosen registration type.
- 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 attributes
- Where it liveslayer
- CampaignCAMPAIGN
- How Ekas settles itdetectability
- DeterministicDETERMINISTIC
- Settled in code from the values you submitted. No model involved, no judgement call, same answer every time.
- 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
- TCRTwilio
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
How to fix itremediation
Clear attributes that do not apply to this registration type before submitting — notably number pooling on a sole proprietor campaign, which is limited to a single number.
A compliant exampleexample
Sole proprietor campaign: number pool false, single number only.
Rules you will hit next
One other rule reads campaign attributes. 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-018 is one of 94 campaign rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.