# BRD-107 — The representative's phone number may back only one brand

> An authorised representative's phone number already used on another brand cannot be used again.

- **Rule ID:** BRD-107
- **Layer:** Brand (`BRAND`)
- **Checks:** `brand.authorized_rep.phone`
- **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:** Twilio, TCR
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/brand/brd-107/

## Why this rule exists

Reusing a contact number across brands is the signature of one operator registering many businesses, which is the pattern brand-level accountability exists to prevent. Agencies trip it honestly by putting their own account manager on every client brand, and the collision is reported against the newest registration rather than against the practice.

## How to fix it

Name a representative who works for the business being registered and use their number. Your own staff belong on the CSP record, which is where a platform's contact details are supposed to live.

## Provider rejection codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| Twilio | `30703` | yes |

## Check this yourself

**Is the representative on this brand an employee of the business being registered, with a number used on no other brand?**

1. Check who is named. An agency account manager on every client brand is the usual cause, and it is reported against the newest registration rather than against the practice.
2. Your own staff belong on the CSP record, which is where a platform's contact details are meant to live.

*What wrong looks like:* One number spread across six client brands. The seventh registration is refused for a collision the earlier six caused.

## Notes

The collision is against every brand in the registry, which we cannot see. What the user has to do is use a different, genuine representative per brand — and if an agency has already spread one number across several brands, expect the next registration to be the one that is refused rather than the earlier ones.