A social profile must not stand in for a website the brand has
The requirementstatement
A social-media profile is accepted as the online presence only where the brand genuinely has no website of its own.
- 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 vs brand.social_profile_urls
- Where it liveslayer
- WebsiteWEBSITE
- 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
- TCRBandwidth
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
How to fix itremediation
Put the business website in brand.website and leave the social profiles as supporting links. Done when brand.website holds the domain the business trades on rather than a profile page.
A compliant exampleexample
website: https://acmecoffee.com — with facebook.com/acmecoffee listed as a social profile, not as the website.
Provider rejection codescodes
The code you get back when this rule is what failed, and whether that provider lets you resubmit.
| Provider | Code | Resubmit |
|---|---|---|
| Bandwidth | 1100 | Yes |
Notesnotes
Rules you will hit next
Other website rules at the same severity. A registration is judged as a whole, not rule by rule.
WEB-147 is one of 93 website rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.