The representative's phone number may back only one brand

The requirementstatement

An authorised representative's phone number already used on another brand cannot be used again.

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.authorized_rep.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 to every 10DLC registration.

Why this rule existsrationale

Reusing a contact number across brands is the signature of one operator registering many businesses, which is the pattern brand-level accountability exists to prevent. Agencies trip it honestly by putting their own account manager on every client brand, and the collision is reported against the newest registration rather than against the practice.

How to fix itremediation

Name a representative who works for the business being registered and use their number. Your own staff belong on the CSP record, which is where a platform's contact details are supposed to live.

Provider rejection codescodes

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

ProviderCodeResubmit
Twilio30703Yes

Check this yourselfattestation

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

Is the representative on this brand an employee of the business being registered, with a number used on no other brand?

  1. 1Check who is named. An agency account manager on every client brand is the usual cause, and it is reported against the newest registration rather than against the practice.
  2. 2Your own staff belong on the CSP record, which is where a platform's contact details are meant to live.

What wrong looks like: One number spread across six client brands. The seventh registration is refused for a collision the earlier six caused.

Notesnotes

The collision is against every brand in the registry, which we cannot see. What the user has to do is use a different, genuine representative per brand — and if an agency has already spread one number across several brands, expect the next registration to be the one that is refused rather than the earlier ones.

Rules you will hit next

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

All brand rules

BRD-107 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.