The services in the terms must match the campaign description
The requirementstatement
The services or products described in the terms must be consistent with what the campaign description says the business does.
- 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
- ToS services section vs campaign.description
- Where it liveslayer
- Policy pagesPOLICY_PAGE
- 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 policyTERMINAL_POLICY
- The fix lives in your privacy policy or SMS terms. Ekas can generate the missing clauses.
- Who requires itauthorities
- Twilio
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
The two documents describe the same business to two different audiences, and a reviewer reads them together — terms describing a software subscription behind a campaign describing a coffee shop is the shape of a registration assembled from someone else's material. It also happens innocently when a business pivots and the terms are the last thing updated.
How to fix itremediation
Bring the services section into line with what the business actually sells, and check it against the campaign description before submitting. Done when both describe the same business.
A compliant exampleexample
Terms: "Acme Coffee sells roasted coffee, subscriptions and brewing equipment." Campaign description names the same business.
Provider rejection codescodes
The code you get back when this rule is what failed, and whether that provider lets you resubmit.
| Provider | Code | Resubmit |
|---|---|---|
| Twiliogen1 | 30886 | Yes |
Rules you will hit next
Other policy pages rules at the same severity. A registration is judged as a whole, not rule by rule.
POL-020A non-English site needs an English policyMediumMEDIUMPOL-027The policy URLs must stay live after approvalMediumMEDIUMPOL-028Keep a dated copy of both documents as submittedMediumMEDIUMPOL-058A service-provider carve-back is required, not prohibitedMediumMEDIUMPOL-076The privacy policy must describe data handling, not sell the programmeMediumMEDIUMPOL-104The policy must say how message content is handledMediumMEDIUM
POL-204 is one of 157 policy pages rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.