# OPS-128 — Registering and vetting a brand does not raise the platform rate limit

> Brand registration and vetting alone do not raise the sending platform's own default per-number rate; a separate increase must be requested.

- **Rule ID:** OPS-128
- **Layer:** Operational (`OPERATIONAL`)
- **Checks:** `platform account sending rate`
- **Severity:** MEDIUM — Usually survives review, but lowers your trust score or invites manual review.
- **When it bites:** Falls due after approval, once you are live and sending
- **How it is detected:** Not knowable before submission — reported with its deadline
- **Fix type:** Wait on an external system or a required interval
- **Required by:** AWS
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/operational/ops-128/

## Why this rule exists

There are two ceilings — the carrier's and the platform's — and vetting moves only the first. Teams complete an expensive vet, see no change in throughput, and conclude the vet failed or the carrier is ignoring it, when the constraint is a default on their own account that nobody has asked to change.

## How to fix it

Raise a rate-increase request with the platform as a separate task from vetting, and check the account limit before diagnosing a throughput problem as a carrier one. Done when the platform limit is above the throughput the campaign was granted.

## Check this yourself

**Have you checked your platform's own per-number rate limit before blaming the carrier — or before buying a vet for throughput?**

1. Look up the account limit at your provider. There are two ceilings, the carrier's and the platform's, and vetting moves only the first.
2. Raise a rate-increase request with the platform as a separate task from vetting.
3. Done when the platform limit is above the throughput the campaign was granted.

*What wrong looks like:* An expensive vet completes, throughput does not move, and the team concludes the vet failed — when the binding constraint was a default on their own account that nobody asked to change.

## Notes

An account limit at the provider. What the user has to do is look it up before spending on a vet for throughput reasons — the platform default is frequently the binding constraint and much cheaper to move.