The business name on the artifact must match the registered brand

The requirementstatement

The business name visible on the consent artifact must match the registered brand legal name or DBA.

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
consent artifact + brand.company_name
Where it liveslayer
Consent flowCONSENT_FLOW
How Ekas settles itdetectability
AI · visionVISION
Needs the pixels: a screenshot of the opt-in surface, a scanned paper form, an MMS attachment.
What the fix involvesfailureClass
Supply evidenceTERMINAL_EVIDENCE
Needs proof only you hold: a screenshot, a recording, a scan of the form people signed.
Who requires itauthorities
TCRTwilioBandwidth
When it appliesapplicabilityText
Applies to every 10DLC registration.

Why this rule existsrationale

An artifact showing a different business is the clearest possible evidence that the consent was collected by someone other than the registrant, which is the consent-transfer problem the framework exists to prevent. It also catches the honest version — a screenshot borrowed from a sister brand because it looked similar enough.

How to fix itremediation

Supply an artifact from the registered brand's own consent surface. If the site trades under a different name, register that name as the DBA so the two match.

Rules you will hit next

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

All consent flow rules

CON-034 is one of 101 consent flow 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.