Contact details on the site must match the brand record
The requirementstatement
The support phone and contact shown on the website should match the brand registration.
- 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
- brand website + brand.phone + brand.email
- Where it liveslayer
- WebsiteWEBSITE
- How Ekas settles itdetectability
- AI · crawlCRAWL
- Needs your live site or policy page fetched and read. Ekas crawls it the way a reviewer would.
- What the fix involvesfailureClass
- Fix the websiteTERMINAL_WEBSITE
- The fix lives on your site. No amount of rewording the form clears it.
- Who requires itauthorities
- TCRTwilioBandwidth
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
Corroboration between site and registration is what turns two weak signals into one strong one. Divergent contact details are a common sign that the registration was assembled from someone else's business information.
How to fix itremediation
Make the contact details on the site and on the registration the same, or explain the difference (for example a separate support line) somewhere visible.
Rules you will hit next
Other website rules at the same severity. A registration is judged as a whole, not rule by rule.
WEB-018The site must be readable in EnglishHighHIGHWEB-019The site must stay live for the whole vetting window, not just at submissionHighHIGHWEB-026The site must look established rather than erected for the registrationHighHIGHWEB-028A campaign landing page is not the brand websiteHighHIGHWEB-030E-commerce brands need a published catalogHighHIGHWEB-032The business name must be visible on the page, not only in the markupHighHIGH
WEB-039 is one of 93 website rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.