Sole proprietor mobile number has a reuse limit

The requirementstatement

A mobile number used for sole proprietor OTP verification may back at most three brand registrations, and must not be a CPaaS-issued number.

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.phone
Where it liveslayer
BrandBRAND
How Ekas settles itdetectability
External recordEXTERNAL_DATA
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.
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
TwilioTCR
When it appliesapplicabilityText
Applies when the brand is a sole proprietor.

Why this rule existsrationale

The verified mobile number is the only real identity check the sole proprietor tier has, so its reuse is capped and CPaaS-issued numbers are refused — otherwise one operator could mint unlimited "individuals". The 24-hour reply window is short and unforgiving.

How to fix itremediation

Use a personal mobile number that can receive the verification text, is not issued by a CPaaS provider, and has not already backed three registrations. The owner must reply YES within 24 hours.

Provider rejection codescodes

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

ProviderCodeResubmit
Twilio30750Yes
Twilio30751Yes
Twilio30752Yes

Check this yourselfattestation

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

Is the verification number a personal handset the owner will have with them, not issued by a messaging provider, and used on fewer than three brands already?

  1. 1Confirm the number is on a consumer mobile carrier — not one bought from Twilio, Telnyx, Bandwidth or any messaging platform, including the console you are registering in.
  2. 2Ask the owner how many sole proprietor brands they have registered on this number. Three is the ceiling across the whole registry.
  3. 3Make sure the owner is expecting the verification text and can reply YES within 24 hours of submission.

What wrong looks like: The number was provisioned in the same console being used to register, so it verifies as CPaaS-issued and is refused; or it is a fourth registration, which fails against a count nobody outside TCR can see.

Notesnotes

Off-platform: the reuse count and the CPaaS origin of a number both live in TCR, which we cannot query, so this rule can only ever warn. The user has to confirm for themselves that the number is a real personal handset and has not already backed three brands, and then be holding it when the OTP arrives — the 24-hour window starts at submission and cannot be restarted without a new registration.

Rules you will hit next

4 other rules read brand.phone. 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-072 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.