Samples must be consistent with the brand website

The requirementstatement

Sample messages must describe a business consistent with what the brand website shows.

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.sample[] + brand website
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
TCRTwilioAWSBandwidth
When it appliesapplicabilityText
Applies to every 10DLC registration.

Why this rule existsrationale

Reviewers read the samples with the website open, and a mismatch is the signature of a registration assembled from someone else's business. It is also how an undeclared use case gets discovered.

How to fix itremediation

Rewrite the samples to describe the products, services and locations the website actually shows.

A compliant exampleexample

Website sells coffee subscriptions → samples reference orders, roasts and store events.

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-046 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.