A cart-reminder programme must be reflected in the terms

The requirementstatement

Where the programme sends shopping-cart reminders, the SMS terms must describe them.

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
SMS terms body
Where it liveslayer
Policy pagesPOLICY_PAGE
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 policyTERMINAL_POLICY
The fix lives in your privacy policy or SMS terms. Ekas can generate the missing clauses.
Who requires itauthorities
T-MobileCTIATCR
When it appliesapplicabilityText
Applies to every 10DLC registration.

Why this rule existsrationale

T-Mobile requires the terms to reflect the cart programme, and the reason is the same one behind the privacy-policy rule: a message triggered by watching what somebody did is not what "promotional offers" prepared them for. A retailer switching the flow on inside a platform changes what the programme sends without touching any document.

How to fix itremediation

Add cart reminders to the message types the terms describe, and say how the number is linked to the basket. Done when the terms name them alongside whatever else the programme sends.

A compliant exampleexample

Acme Coffee Rewards sends promotional offers, rewards updates, and reminders when you leave something in your basket.

Common mistakespitfalls

  • The privacy policy owes the detection mechanism (POL-109) and the opt-in disclosure owes the message type (WEB-068). Fixing the terms alone leaves two of the three.

Notesnotes

Conditional on cart-reminder traffic being in scope, which no applicability dimension expresses. The check reads the campaign copy for the signal and passes where it finds none.

Rules you will hit next

6 other rules read SMS terms body. 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 policy pages rules

POL-110 is one of 157 policy pages 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.