The programme described in the terms must match the registered use case
The requirementstatement
The programme description in the SMS terms must relate to the use case the campaign is registered under.
- Severityseverity
- BlockingBLOCKINGBreaking this rule gets the submission rejected. There is no partial credit.
- When it bitesphase
- Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
- What is checkedobject
- SMS terms body vs campaign.usecase
- 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
- AWSTwilioTCR
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
The terms are the public description of the programme and the use case is the private one, so a disagreement means one of them is wrong about what will be sent — and the reviewer resolves it by refusing the campaign. It happens most often when a terms page written for the whole business is attached to a narrower campaign.
How to fix itremediation
Make the terms describe the categories the campaign is registered for, or register the use case the terms describe. Done when the two describe one programme.
A compliant exampleexample
Use case MARKETING · terms describe promotional offers and rewards updates — the same programme.
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 | 30893 | 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-001A privacy policy URL is required on the campaignBlockingBLOCKINGPOL-002A terms and conditions URL is required on the campaignBlockingBLOCKINGPOL-003An uploaded policy document must fit the provider file constraintsBlockingBLOCKINGPOL-005The terms and conditions attestation must be setBlockingBLOCKINGPOL-010Both policy URLs must resolve and return content anonymouslyBlockingBLOCKINGPOL-015The policy host must serve a valid certificate of its ownBlockingBLOCKING
POL-193 is one of 157 policy pages rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.