An undeclared additional use case must be surfaced

The requirementstatement

Where the website or description implies a message category the campaign has not declared, it must be flagged.

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 + campaign.description
Where it liveslayer
WebsiteWEBSITE
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
TCRTwilioSinch
When it appliesapplicabilityText
Applies to every 10DLC registration.

Why this rule existsrationale

Live traffic must match the registered use case, and an undeclared category is a violation waiting to happen the first time that content is sent. Catching it at registration is the difference between adding a use case and being filtered later.

How to fix itremediation

Declare every category you will send, or remove the undeclared one from your plans. MIXED covers promotional plus transactional.

A compliant exampleexample

Site shows cart-abandonment flows → declare MARKETING (or MIXED), not ACCOUNT_NOTIFICATION alone.

Rules you will hit next

Other website rules at the same severity. A registration is judged as a whole, not rule by rule.

All website rules

WEB-062 is one of 93 website rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.

Reading the rules is the easy part.

Ekas runs every rule that gates approval, 823 of these 915, against your registration before it reaches the carrier. It reads your site, your policy pages and your opt-in the way a reviewer would, and hands you the fix, not just the verdict.