The site should describe the SMS programme
The requirementstatement
The website should carry information about what the messaging programme sends, to whom, and why.
- 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
- brand website
- Where it liveslayer
- WebsiteWEBSITE
- How Ekas settles itdetectability
- AI · crawlCRAWL
- Needs your live site or policy page fetched and read. Ekas crawls it the way a reviewer would.
- What the fix involvesfailureClass
- Fix the websiteTERMINAL_WEBSITE
- The fix lives on your site. No amount of rewording the form clears it.
- Who requires itauthorities
- CTIATCRTwilio
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
A programme described only inside the registration exists only for the reviewer. Documenting it publicly is both a CTIA expectation and the thing that lets a consumer verify the messages they receive are legitimate.
How to fix itremediation
Add a short SMS programme section to the site or the SMS terms page: what you send, how often, who it is for, and how to stop.
Rules you will hit next
6 other rules read brand website. Fixing one field to satisfy a single rule is how a resubmission trades one rejection for another, so read these before you change anything.
WEB-012A parked or for-sale domain is not a websiteBlockingBLOCKINGWEB-013A pre-launch placeholder is not a websiteBlockingBLOCKINGWEB-016The website must be machine-crawlableBlockingBLOCKINGWEB-017The site must not be gated by geo, bot challenge or app wallBlockingBLOCKINGWEB-021The site must not be behind a login or access wallBlockingBLOCKINGWEB-022A login-gated product needs a public description pageBlockingBLOCKING
WEB-055 is one of 93 website rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.