# BRD-210 — A low trust score blocks or narrows campaign registration

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

- **Rule ID:** BRD-210
- **Layer:** Brand (`BRAND`)
- **Checks:** `brand.trust_score`
- **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:** External record we cannot query — reported as a warning to verify
- **Fix type:** Wait on an external system or a required interval
- **Required by:** Twilio, AT&T
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/brand/brd-210/

## Why this rule exists

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 it

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 yourself

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

1. Ask 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.
2. Where 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.

## Notes

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.