# BRD-156 — The representative needs an enum job position and their real title

> job_position must come from Director, GM, VP, CEO, CFO, General Counsel or Other, and the representative's exact business title must be supplied alongside it.

- **Rule ID:** BRD-156
- **Layer:** Brand (`BRAND`)
- **Checks:** `brand.authorized_rep.job_position + .title`
- **Severity:** MEDIUM — Usually survives review, but lowers your trust score or invites manual review.
- **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:** Twilio
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/brand/brd-156/

## Why this rule exists

Two fields describe the same person and only one of them is constrained: the enum is what the API validates, and the free-text title is what a reviewer compares against the company's own website. Submitting the real title in the enum field fails validation, and submitting the enum value in the title field gives the reviewer nothing to corroborate.

## How to fix it

Choose the closest enum value — Other is a legitimate answer for most titles — and put the person's actual title in the title field, spelled as it appears on the company site or their signature block. Done when the enum validates and the title is a real one.

## Example of a compliant value

```text
job_position: CEO · title: Chief Executive Officer — or job_position: Other · title: Head of Customer Operations
```

## Provider rejection codes

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