# OPS-POOL-DECLARED — Number pooling must be declared consistently with the campaign scale

> The number-pool attribute must reflect whether the campaign will actually send from multiple numbers.

- **Rule ID:** OPS-POOL-DECLARED
- **Layer:** Operational (`OPERATIONAL`)
- **Checks:** `campaign.number_pool`
- **Severity:** HIGH — Rejected by at least one carrier or provider, and a common cause of failure at the rest.
- **When it bites:** Gates approval — get this wrong and registration is refused
- **How it is detected:** Deterministic (settled in code from the submitted values)
- **Fix type:** Fix the field — a better value in the form clears it
- **Required by:** TCR, T-Mobile, Twilio
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/operational/ops-pool-declared/

## Why this rule exists

Number pooling is a filtering signal: sending similar content across many numbers without declaring a pool is the definition of snowshoeing, which carries a four-figure pass-through fee. Declaring a pool you do not use is harmless by comparison, so the asymmetry favours declaring.

## How to fix it

Set the number-pool attribute true if the campaign will send from more than one number. Never spread similar content across undeclared numbers — that is snowshoeing and it is fined rather than rejected.

## Example of a compliant value

```text
Sending from 5 numbers → number pool: true.
```