embeddedPhone must ignore the HELP support number
The requirementstatement
The embeddedPhone attribute should be set when a sample contains a phone number other than the support number given in the HELP reply.
- Severityseverity
- MediumMEDIUMUsually survives review, but lowers your trust score or invites a manual look you would rather avoid.
- 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
- Message contentMESSAGE_CONTENT
- 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
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 itremediation
Set the embedded-phone attribute based on numbers in campaign content, excluding the support number you publish in the HELP reply.
A compliant exampleexample
Samples contain no numbers other than the HELP support line → leave "messages contain phone numbers" false.
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.
CMP-PHONE-DECLembeddedPhone must match whether samples contain phone numbersHighHIGHMSG-117A sample must contain a phone number when embeddedPhone is declaredHighHIGHMSG-015A message must not render as ten or more segmentsMediumMEDIUMMSG-026Samples must not contain mustache or curly-brace template tokensMediumMEDIUMMSG-038A registered domain can substitute for the brand name in a sampleMediumMEDIUMMSG-075HELP reply support contact must be on the brand domainMediumMEDIUM
MSG-116 is one of 122 message content rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.