Declared attributes must match sample content generally

The requirementstatement

Every declared campaign attribute must be consistent with what the sample messages actually contain.

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
campaign attributes + campaign.sample[]
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
TCRTwilioAWS
When it appliesapplicabilityText
Applies to every 10DLC registration.

Why this rule existsrationale

Attributes are self-declared and drive filtering, so a mismatch either over-restricts your own traffic or under-declares something carriers screen for. The link and phone pairs are checked individually; this catches the rest as a set.

How to fix itremediation

Walk each attribute against the samples and correct whichever side is wrong.

A compliant exampleexample

Samples mention financing → direct lending: true.

Rules you will hit next

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

All message content rules

MSG-120 is one of 122 message content 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.