# BRD-279 — Third-party job boards are not carried

> A brand whose business is a third-party job board or staffing aggregator must not be registered for A2P messaging.

- **Rule ID:** BRD-279
- **Layer:** Brand (`BRAND`)
- **Checks:** `brand.vertical + brand fields + website content`
- **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:** AI judgement over the submitted form; AI judgement over the crawled website or policy page
- **Fix type:** Hard stop — not remediable, resubmission will not help
- **Required by:** AWS, Infobip, Sinch
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/brand/brd-279/

## Why this rule exists

Job messaging is permitted from the employer that is actually hiring and refused from intermediaries, because recruitment texts from a company the recipient never applied to are the classic shape of an employment scam. Genuine job boards are caught by a rule aimed at the fraudulent ones, and the distinction the carriers draw is first-party hiring rather than legitimacy.

## How to fix it

Job messaging must come from the hiring brand itself. Where you operate a board, the employer registers its own brand and messages its own candidates; where you place workers, message the workers you employ about their own engagements.

## Provider rejection codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| Bandwidth | `7001` | no |
| Sinch | `CR2006` | no |

## Notes

Absorbs WEB-132, which states the same brand-level rejection decided from the site business model rather than from the form.