# CMP-038 — Campaign fields must reference one company, not several

> No campaign field may reference a second company, subsidiary, franchise or client brand alongside the registered one.

- **Rule ID:** CMP-038
- **Layer:** Campaign (`CAMPAIGN`)
- **Checks:** `campaign.description + campaign.message_flow + campaign.sample[]`
- **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
- **Fix type:** Fix the field — a better value in the form clears it
- **Required by:** AWS, Twilio
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/campaign/cmp-038/

## Why this rule exists

One campaign carries one brand's traffic, and a reviewer reading two company names cannot tell which one holds the consent or which one a complaint would be attributed to. Groups run into this honestly — the parent is the legal entity, the trading name is on the website, and a third name is on the app — so the description names all three in an effort to be complete and reads as pooled traffic.

## How to fix it

Pick the entity whose consent record backs this traffic and write every field in that name alone, registering a separate campaign for each other entity. Where the programme genuinely spans franchisees, AGENTS_FRANCHISES is the use case that lets sub-entities be disclosed rather than concealed.

## Example of a compliant value

```text
Every field names Acme Coffee — not "Acme Coffee, part of the Northstar group, on behalf of Acme Roasting Co".
```

## Common mistakes

- The legal suffix and the trading name are one company: "Acme Coffee Co, LLC" and "Acme Coffee" are not two brands, and neither is a location suffix.

## Provider rejection codes

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