The terms must carry a contact block
The requirementstatement
The terms of service must carry a contact block naming the entity, its address, an email address and a phone number.
- 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
- ToS contact block
- Where it liveslayer
- Policy pagesPOLICY_PAGE
- 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 policyTERMINAL_POLICY
- The fix lives in your privacy policy or SMS terms. Ekas can generate the missing clauses.
- Who requires itauthorities
- CTIASinchAWS
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
The contact block doubles as the customer-care route the messaging framework separately requires, so a terms page without one leaves both a contractual and a messaging obligation unmet. It is also the block a reviewer reads to corroborate the brand, which is why a bare contact-form link does not do the job.
How to fix itremediation
Close the terms with a contact block carrying the entity, the postal address, a monitored email and a phone number, matching the brand record. Done when a reader can reach a person without using a form.
A compliant exampleexample
Questions? Acme Coffee Co, LLC, 1240 Mission St, Suite 400, San Francisco, CA 94103 · support@acmecoffee.com · 415-555-0134
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/DCA | 852 | Yes |
Notesnotes
Overlaps deliberately with POL-190, which asks the SMS terms for a support contact: a brand that publishes dedicated SMS terms satisfies both from one block, and a brand that does not still owes the contact here.
Rules you will hit next
Other policy pages rules at the same severity. A registration is judged as a whole, not rule by rule.
POL-021Policy URLs must not redirectHighHIGHPOL-023A social profile is not a policy pageHighHIGHPOL-025Exactly one privacy policy must be discoverableHighHIGHPOL-026The policy on the site and the policy attached to the registration must agreeHighHIGHPOL-030Both documents must be linked from the site footer on every pageHighHIGHPOL-053The clause must say NOT SHARED, not merely "not sold"HighHIGH
POL-219 is one of 157 policy pages rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.