The message flow must deep-link the opt-in page, not the homepage

The requirementstatement

The URL given in the message flow must point at the page carrying the consent surface, not at the site root.

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.message_flow
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
TCRTwilioBandwidthAWS
When it appliesapplicabilityText
Applies to every 10DLC registration.

Why this rule existsrationale

A reviewer given a homepage has to hunt for the opt-in, and if they do not find it quickly they reject. Deep-linking converts a search into a single click, and it is one of the cheapest possible improvements to approval odds.

How to fix itremediation

Replace the homepage link in the message flow with the direct URL of the page holding the consent checkbox.

A compliant exampleexample

https://acmecoffee.com/signup rather than https://acmecoffee.com

Rules you will hit next

6 other rules read campaign.message_flow. 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 website rules

WEB-090 is one of 93 website 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.