# CMP-PHONE-DECL — embeddedPhone must match whether samples contain phone numbers

> The embeddedPhone attribute must be true when any sample contains a phone number, and vice versa.

- **Rule ID:** CMP-PHONE-DECL
- **Layer:** Campaign (`CAMPAIGN`)
- **Checks:** `campaign.embedded_phone + campaign.sample[]`
- **Severity:** HIGH — Rejected by at least one carrier or provider, and a common cause of failure at the rest.
- **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:** TCR, Twilio, AWS
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/campaign/cmp-phone-decl/

## Why this rule exists

Phone numbers inside message bodies are a filtering signal because they are a common redirection tactic, so the declaration must match reality. Several providers carve out a support number in the HELP reply, which is why this is graded below the link rule.

## How to fix it

Set the "messages contain phone numbers" flag to match your sample messages.

## Example of a compliant value

```text
Samples contain 415-555-0134 → set "messages contain phone numbers" to true.
```

## Notes

A HELP-reply support number is an accepted exception at several providers; that carve-out is not yet modelled here.