# BRD-233 — Some providers require vetting for every use case above the lowest tier

> At least one provider requires standard or enhanced brand vetting for any use case beyond the lowest-volume mixed tier.

- **Rule ID:** BRD-233
- **Layer:** Brand (`BRAND`)
- **Checks:** `the vet record + campaign.use_case`
- **Severity:** BLOCKING — Breaking this rule gets the submission rejected outright.
- **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:** Vonage
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/brand/brd-233/

## Why this rule exists

Where this applies, vetting stops being an upgrade and becomes a precondition for the use case itself — a marketing campaign simply cannot be registered without it. It is not visible in any field validation, so a team that budgeted for registration and not for vetting discovers the gap at the point the campaign is refused.

## How to fix it

Check whether your provider gates use cases on vetting before quoting a customer, and order the vet as part of onboarding rather than as a later upgrade. Done when a vet is held before the campaign is submitted on a provider that requires one.

## Check this yourself

**Have you checked whether your provider gates use cases on vetting, before quoting the customer?**

1. Read the provider's onboarding terms for a vetting precondition on anything above the lowest-volume mixed tier — it produces no field validation error.
2. Where it applies, order the vet as part of onboarding rather than as a later upgrade.

*What wrong looks like:* A team budgets for registration and not for vetting, and finds the gap when the marketing campaign is refused — with the schedule, not the fee, as the thing that is lost.

## Notes

Conditional on the submission target and stated by Vonage explicitly. What the user has to establish is whether their own provider imposes it — the answer is in the onboarding terms rather than in an error code, and finding it out afterwards costs the campaign schedule rather than the fee.