The description must not contain personal data
The requirementstatement
The campaign description must not contain individual names, account numbers or other personal data.
- 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
- CampaignCAMPAIGN
- 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
- Twilio
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
The description is stored and read across several organisations — the CSP, the registry, the carriers — and none of them is the right custodian for a customer's name or account number. It gets there through a well-meant example: someone illustrates the programme with a real message they sent, and the illustration carries a real person in it.
How to fix itremediation
Replace any real person, account number or order reference with a category or a bracketed placeholder. Done when nothing in the field identifies an individual.
A compliant exampleexample
Acme Coffee texts customers their order status — not "we text customers like Maria Alvarez about order 4471 on card ending 8891".
Provider rejection codescodes
The code you get back when this rule is what failed, and whether that provider lets you resubmit.
| Provider | Code | Resubmit |
|---|---|---|
| Twilio | 30886 | Yes |
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
CMP-050 is one of 94 campaign rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.