A low trust score blocks or narrows campaign registration

The requirementstatement

A provider trust score at or below the gate blocks campaign registration entirely, and one just above it restricts which use cases are available.

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.trust_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: TwilioAT&T
When it appliesapplicabilityText: Applies to every 10DLC registration.

Why this rule existsrationale

This is a second score, computed by the provider rather than by the vetting partner, and it gates the use cases a brand may register at all — so a brand can be verified, vetted, and still unable to register the campaign it exists for. The rejection names the carrier rather than the score, which sends teams to look at their campaign copy.

How to fix itremediation

Where campaign registration is blocked with a carrier-qualification message, check the trust score before editing the campaign. Raising it means improving the brand data and, usually, buying a standard vet — the campaign is not the thing that failed.

Check this yourselfattestation

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

When a campaign is refused on carrier qualification, have you asked your provider for the brand's trust score before editing the campaign?

1Ask the provider directly for the trust score — it is theirs, computed separately from the vetting score, and it is not on the brand record you can see.
2Where the score is the cause, raise it by improving brand data and usually by buying a standard vet. The campaign is not the thing that failed.

What wrong looks like: The rejection names the carrier rather than the score, so the team rewrites campaign copy for a week. A brand can be verified, vetted, and still barred from the use case it exists for.

Notesnotes

The trust score is the provider's own and is not exposed on the brand record we see. What the user has to do is ask their provider for the score when a campaign is refused on carrier qualification, because that one number explains a rejection that otherwise reads as a content problem.

Rules you will hit next

Other brand rules at the same severity. A registration is judged as a whole, not rule by rule.

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 BRD-034Validate a non-US identifier against its home register before submittingHighHIGH

All brand rules

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