Use case must be available to the brand entity type

The requirementstatement

Restricted use cases must only be selected by the entity types eligible for them.

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
campaign.usecase + brand.entity_type
Where it liveslayer
CampaignCAMPAIGN
How Ekas settles itdetectability
DeterministicDETERMINISTIC
Settled in code from the values you submitted. No model involved, no judgement call, same answer every time.
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
TCRTwilioInfobip
When it appliesapplicabilityText
Applies to every 10DLC registration.

Why this rule existsrationale

Several use cases are gated on entity type — charity to non-profits, sole-proprietor to individuals, emergency to registered organisations. Selecting one the brand cannot hold produces a rejection that reads as a campaign problem while the real fix is on the brand.

How to fix itremediation

Either choose a use case your entity type can hold, or re-register the brand under the entity type the use case requires.

A compliant exampleexample

CHARITY requires entity type NON_PROFIT.

Rules you will hit next

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

All campaign rules

CMP-142 is one of 94 campaign 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.