A score below the threshold means fixing the data, not re-vetting

The requirementstatement

Where the vetting score is below the carrier or use-case threshold, the underlying brand data must be corrected before a re-vet.

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: AWSSinchInfobip
When it appliesapplicabilityText: Applies to every 10DLC registration.

Why this rule existsrationale

The score is computed from the brand data and the public record behind it, so re-running the same examination against the same inputs returns the same number — and the cooldown means you only get to find that out every three months. The productive move is unglamorous: correct the address, publish the phone number, fix the website, then re-vet.

How to fix itremediation

Work the inputs the score reads: an exact address match, a phone that answers, a website that names the business, social profiles, a mailbox on the brand domain. Then re-vet once, after the cooldown. Done when the underlying data has changed before the second examination.

Check this yourselfattestation

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

Have you corrected the data the score reads — address, phone, website, mailbox, social profiles — before ordering another vet?

1Treat a low score as a data problem, not a verdict. Most of its inputs are things you control.
2Work them in order: an exact address match, a phone that answers, a website that names the business, social profiles, a mailbox on the brand domain.
3Then re-vet once, after the cooldown.

What wrong looks like: The same examination is re-run against unchanged inputs and returns the same number — and the three-month cooldown means that is the only answer available until spring.

Notesnotes

The score and its threshold are held by the vetting provider. What the user has to do is treat a low score as a data problem rather than a verdict — most of the inputs are things they control, and BRD-211 lists the few that they do not.

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-209The score maps to specific throughput termsHighHIGH 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-208 is one of 196 brand rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.