The score maps to specific throughput terms

The requirementstatement

The vetting score determines the carrier class and daily throughput the brand receives, and 75 or above is the target.

Severityseverity: HighHIGHRejected by at least one carrier or provider, and a common cause of failure at the rest.
When it bitesphase: Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
What is checkedobject: brand.vetting_score
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: TCRAT&TT-Mobile
When it appliesapplicabilityText: Applies to every 10DLC registration.

Why this rule existsrationale

Score bands are the mechanism the whole vetting purchase exists for, and they are steep: 75 and above buys the top class and 200,000 messages a day, while 25 to 49 buys 10,000 and 1 to 24 buys 2,000. Promising a customer volume before the score is known is promising something you do not control, and the gap between bands is a factor of twenty rather than a matter of degree.

How to fix itremediation

Read the throughput off the band rather than off the fee: 75–100 gives AT&T Class A/B and T-Mobile Top at 200,000/day; 50–74 gives C/D and High Mid at 40,000; 25–49 gives Low Mid at 10,000; 1–24 gives Low at 2,000. Size the programme against the band you actually hold.

Check this yourselfattestation

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

Have you avoided committing to a send volume before the vetting band is known?

1Read the throughput off the band, not off the fee: 75–100 is 200,000 a day, 50–74 is 40,000, 25–49 is 10,000, 1–24 is 2,000.
2Where a send date is already fixed, order the vet early enough to re-plan if the band comes in low.

What wrong looks like: A customer is promised a volume before the score exists. The gap between adjacent bands is a factor of twenty, so the shortfall is not a matter of degree.

Notesnotes

Absorbs OPS-129, which states the same mapping and warns against promising terms the score cannot deliver. The score is issued by the vetting provider after the fact, so what the user has to do is avoid committing to a send volume until the band is known — and where a date is fixed, order the vet early enough to re-work the plan if the band comes in low.

Rules you will hit next

One other rule reads brand.vetting_score. Fixing one field to satisfy a single rule is how a resubmission trades one rejection for another, so read these before you change anything.

BRD-208A score below the threshold means fixing the data, not re-vettingHighHIGH BRD-006Submit every name line above the address on a multi-line IRS recordHighHIGH BRD-007TCR takes only the first line of the IRS-registered nameHighHIGH BRD-010Take the legal name from the CP-575 or 147C, never a W-2 or W-9HighHIGH BRD-014An acquired business registers the details it filed taxes underHighHIGH BRD-027EIN must be old enough to have propagated to IRS recordsHighHIGH

All brand rules

BRD-209 is one of 196 brand rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.