# BRD-218 — Import the same token into every instance of the same brand

> Where the same brand is registered by more than one CSP, the same vetting token must be imported into each instance.

- **Rule ID:** BRD-218
- **Layer:** Brand (`BRAND`)
- **Checks:** `the vet token across brand instances`
- **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:** Deterministic (settled in code from the submitted values)
- **Fix type:** Fix the field — a better value in the form clears it
- **Required by:** TCR
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/brand/brd-218/

## Why this rule exists

Throughput follows the vet, and the vet is attached to a brand instance rather than to the business — so a brand registered through two CSPs with the token imported into only one of them sends fast on one route and slowly on the other, for no visible reason. Only the Aegis standard token can be reused this way; every other partner issues single-use tokens.

## How to fix it

Import the same Aegis standard token into each duplicate brand instance, rather than ordering a fresh vet per CSP. Done when every instance of the brand reports the same vetting score.

## Example of a compliant value

```text
vetting token: the same Aegis certificate imported into both the Twilio and the Telnyx brand instances
```

## Common mistakes

- Political tokens are single-use (BRD-246) and cannot be spread this way — the reuse rule is specific to the Aegis standard class.