Contact, email, address and URL must each stand up on their own

The requirementstatement

The representative, the email, the address and the website must each independently resolve or validate.

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.authorized_rep + brand.email + address + brand.website
Where it liveslayer
BrandBRAND
How Ekas settles itdetectability
AI · crawlCRAWLExternal recordEXTERNAL_DATA
Needs your live site or policy page fetched and read. Ekas crawls it the way a reviewer would. The fact that settles it lives in a register we cannot query, such as the IRS file, a postal database, or another provider’s tenant. Reported as a warning with the evidence to check, not as a pass.
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
Bandwidth
When it appliesapplicabilityText
Applies to every 10DLC registration.

Why this rule existsrationale

Verification does not average across the record: each identity component is checked separately, and one that cannot be resolved drags the whole submission rather than being outweighed by the four that could. Registrations assembled from several internal systems are where this bites, because each field is correct in its own system and one of them is stale.

How to fix itremediation

Check each component against its own source before submitting: the representative against the company's own staff list, the email by sending a test, the address against the postal authority, the website by opening it in a private window. Done when all four resolve independently.

A compliant exampleexample

rep: Jane Doe, CEO · email: jane.doe@acmecoffee.com · address: 1240 Mission St, Suite 400, San Francisco, CA 94103 · website: https://acmecoffee.com

Check this yourselfattestation

Ekas flags this from what you submit, but the fact that settles it sits somewhere only you can reach.

Have you checked all four identity components against their own sources — representative, email, address, website — rather than assuming the record is right because most of it is?

  1. 1Representative: against the company's own staff list.
  2. 2Email: by sending a test message from outside.
  3. 3Address: against the postal authority's standardised form.
  4. 4Website: by opening it in a private window, logged out.

What wrong looks like: A registration assembled from four internal systems, each correct in its own system and one of them stale. Verification does not average — the stale one drags the whole submission, silently, as a lowered score.

Notesnotes

The crawl settles the website and, where the site publishes them, the address and the contact details. Whether the mailbox accepts mail and whether the address is deliverable are BRD-115 and BRD-095 and are external. What the user has to do is the four-step check in the remediation, because a component that fails here fails silently as a lowered score rather than as a named finding.

Rules you will hit next

Other brand rules at the same severity. A registration is judged as a whole, not rule by rule.

All brand rules

BRD-273 is one of 196 brand 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.