Legal name must not carry an appended personal name or role

The requirementstatement

The legal name field must contain only the entity name — not a contact person or role suffix appended to it.

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
brand.company_name
Where it liveslayer
BrandBRAND
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
TCRTwilio
When it appliesapplicabilityText
Applies to every 10DLC registration.

Why this rule existsrationale

Registration forms elsewhere often combine entity and contact, so people paste strings like "ACME LLC Theresa Lopez - MBR" into the legal name. That never matches the IRS record, and because the entity name is present inside the string it looks correct at a glance.

How to fix itremediation

Remove everything after the entity suffix. The contact person belongs in the brand contact fields, not in the legal name.

A compliant exampleexample

Legal name: "Acme Coffee Co, LLC" — not "Acme Coffee Co, LLC Jane Doe - MBR"

Rules you will hit next

6 other rules read brand.company_name. Fixing one field to satisfy a single rule is how a resubmission trades one rejection for another, so read these before you change anything.

All brand rules

BRD-008 is one of 196 brand 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.