One approved number is controlled by one party
The requirementstatement
Sub-aggregation is prohibited: no more than one party may control the content sent from, or the numbers receiving on, a single approved number.
- Severityseverity
- BlockingBLOCKINGBreaking this rule gets the submission rejected. There is no partial credit.
- When it bitesphase
- After you are livepostFalls due once you are sending: STOP handling, quiet hours, suppression, record retention.
- What is checkedobject
- number to content-provider mapping
- Where it liveslayer
- OperationalOPERATIONAL
- How Ekas settles itdetectability
- AI · formAI_FORM
- A semantic question about what you wrote: whether a description matches a use case, whether a name looks like a filed entity. Judged by a model against written criteria.
- What the fix involvesfailureClass
- Hard stopHARD_STOP
- Not remediable. Resubmitting will not help, and anyone offering to fix it is selling you a rejection.
- Who requires itauthorities
- T-MobileAT&TVerizonCTIABirdVonage
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
The registration says who is behind a number, and sub-aggregation makes that untrue — the consumer receives messages from an entity that was never vetted, and a complaint traces back to a brand that did not send it. It also breaks the one-opt-in-per-message-sender rule underneath, because consent given to one party is being used by another. Agencies and franchise groups arrive here honestly, by provisioning centrally and letting each client send.
How to fix itremediation
Register a separate brand and campaign for each party whose content goes out, and give each its own numbers. Where a shared arrangement is genuinely needed, get it approved and keep the sender register OPS-142 describes rather than operating it informally.
Notesnotes
Absorbs OPS-266 and MSG-140, which state the same prohibition from the shared-number and message-content sides. Partly visible in what a submission describes and not settleable from it — the arrangement lives in an operating model rather than in a field. What the user has to establish is who can send from each number today, and register a separate brand per party where the answer is more than one. OPS-367 is the ISV form of the same requirement.
Rules you will hit next
Other operational rules at the same severity. A registration is judged as a whole, not rule by rule.
OPS-026The universal opt-out keyword set must be declaredBlockingBLOCKINGOPS-027Opt-out keyword handling must be declared, not assumedBlockingBLOCKINGOPS-029A revocation must survive punctuation, case and surrounding wordsBlockingBLOCKINGOPS-031A plainly-worded opt-out counts even with no keyword in itBlockingBLOCKINGOPS-033STOP must never come back as an errorBlockingBLOCKINGOPS-037On a shared address, STOP must stop everythingBlockingBLOCKING
OPS-141 is one of 139 operational rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.