# BRD-165 — A toll-free contact needs a full first and last name

> The toll-free registration contact must be an authorised representative's full first and last name.

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

## Why this rule exists

The contact name is checked against the business rather than stored, so a department, a role or a single word gives the reviewer nothing to check and the submission is refused. Teams supply "Support" or "Marketing Team" precisely because they are trying to avoid naming an individual, which is the opposite of what the field is for.

## How to fix it

Name a real person who is authorised to act for the business, first and last name in their own fields. Done when both fields hold a person's name rather than a role or a department.

## Example of a compliant value

```text
contact_first_name: Jane · contact_last_name: Doe
```

## Provider rejection codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| Infobip | `10000` | yes |

## Notes

Applies on the toll-free verification path; the check passes immediately for a 10DLC brand submission. Whether the named person is genuinely authorised is BRD-164, which nothing on the form can settle.