# MSG-116 — embeddedPhone must ignore the HELP support number

> The embeddedPhone attribute should be set when a sample contains a phone number other than the support number given in the HELP reply.

- **Rule ID:** MSG-116
- **Layer:** Message content (`MESSAGE_CONTENT`)
- **Checks:** `campaign.embedded_phone + campaign.sample[]`
- **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:** TCR, Twilio, AWS
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/message-content/msg-116/

## Why this rule exists

Publishing a support number in a HELP response is required, so counting it as an embedded phone number forces a true declaration that misrepresents the campaign. The attribute is meant to flag numbers inside marketing content, which is a redirection signal, not a support contact.

## How to fix it

Set the embedded-phone attribute based on numbers in campaign content, excluding the support number you publish in the HELP reply.

## Example of a compliant value

```text
Samples contain no numbers other than the HELP support line → leave "messages contain phone numbers" false.
```