A sole proprietor gets one campaign and one number
The requirementstatement
A SOLE_PROPRIETOR brand may hold exactly one campaign, and that campaign exactly one telephone 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.entity_type + campaign count + campaign.number_pool
- Where it liveslayer
- Brand ↔ campaignCROSS
- 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
- TCRT-MobileTwilio
- When it appliesapplicabilityText
- Applies when the brand is a sole proprietor.
Why this rule existsrationale
How to fix itremediation
Fold everything the programme sends into the one sole-proprietor campaign, on one number, and turn number pooling off. If the business genuinely needs a second campaign or more throughput, obtain an EIN and re-register as a standard entity — the tier is the limit, not the campaign.
A compliant exampleexample
Sole proprietor: 1 campaign · 1 phone number · numberPool: false
Common mistakespitfalls
- Registering the second campaign under a second sole-proprietor brand does not work either: the tier caps the mobile number behind the brands as well, so the same person cannot hold an unlimited number of them.
Only meaningful once these passdependsOn
- XBC-001Sole proprietor brands may only run the sole proprietor use case
Rules you will hit next
Other brand ↔ campaign rules at the same severity. A registration is judged as a whole, not rule by rule.
XBC-008 is one of 13 brand ↔ campaign rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.