Per-EIN brand counts are capped even where several are allowed

The requirementstatement

Where a provider permits more than one brand per tax ID, the number is still capped and each additional brand needs a documented business reason.

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
brand.ein across the registry
Where it liveslayer
BrandBRAND
How Ekas settles itdetectability
External recordEXTERNAL_DATAHuman checkHUMAN
The fact that settles it lives in a register we cannot query, such as the IRS file, a postal database, or another provider’s tenant. Reported as a warning with the evidence to check, not as a pass. Only someone holding the document or making the call can settle it. Ekas tells you exactly what to look at.
What the fix involvesfailureClass
Wait on someone elseTERMINAL_EXTERNAL
Needs an external system or a waiting period, such as IRS propagation, a vetting result, or a carrier queue.
Who requires itauthorities
Twilio
When it appliesapplicabilityText
Applies to every 10DLC registration.

Why this rule existsrationale

The looser model is not an open door: the cap exists because a single business fragmented across many brands defeats the reputation model the framework runs on. Agencies reach the cap by creating a brand per client campaign rather than per client, and the refusal arrives on the one that mattered.

How to fix itremediation

Keep one brand per legal entity and use campaigns for everything below that. Where several brands on one tax ID are genuinely required, write the business reason down before submitting — you will be asked for it, and after a refusal it is too late.

Provider rejection codescodes

The code you get back when this rule is what failed, and whether that provider lets you resubmit.

ProviderCodeResubmit
Twilio30898Yes

Check this yourselfattestation

No tool can settle this one for you. Here is the check, and what wrong looks like.

Do you keep your own tally of brands registered against each tax ID, across every provider you use?

  1. 1Count them. The registry-wide number is invisible to you and to us.
  2. 2Keep one brand per legal entity and use campaigns for everything below that.
  3. 3Where several are genuinely required, write the business reason down before submitting — you will be asked, and after a refusal it is too late.

What wrong looks like: An agency creates a brand per client campaign rather than per client, hits the cap, and the refusal lands on the one that mattered. A second attempt on the same EIN after a reuse rejection is read as evasion rather than as a retry.

Notesnotes

Absorbs OPS-366, which states the same minimisation duty and adds the warning against resubmitting after an EIN-reuse rejection — a second attempt on the same EIN is read as evasion rather than as a retry. The count is registry-wide and invisible to us; what the user has to do is keep their own tally of brands registered against each EIN, across every provider they use.

Rules you will hit next

One other rule reads brand.ein across the registry. 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-174 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.