embeddedPhone must match whether samples contain phone numbers

The requirementstatement

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

Severityseverity
HighHIGHRejected by at least one carrier or provider, and a common cause of failure at the rest.
When it bitesphase
Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
What is checkedobject
campaign.embedded_phone + campaign.sample[]
Where it liveslayer
CampaignCAMPAIGN
How Ekas settles itdetectability
DeterministicDETERMINISTIC
Settled in code from the values you submitted. No model involved, no judgement call, same answer every time.
What the fix involvesfailureClass
Fix the fieldRETRY_FIELD
A better value in the form fixes it. Ekas can rewrite it and re-check.
Who requires itauthorities
TCRTwilioAWS
When it appliesapplicabilityText
Applies to every 10DLC registration.

Why this rule existsrationale

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 itremediation

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

A compliant exampleexample

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

Notesnotes

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

Rules you will hit next

2 other rules read campaign.embedded_phone + campaign.sample[]. Fixing one field to satisfy a single rule is how a resubmission trades one rejection for another, so read these before you change anything.

All campaign rules

CMP-PHONE-DECL is one of 94 campaign rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.

Reading the rules is the easy part.

Ekas runs every rule that gates approval, 823 of these 915, against your registration before it reaches the carrier. It reads your site, your policy pages and your opt-in the way a reviewer would, and hands you the fix, not just the verdict.