> For the complete documentation index, see [llms.txt](https://help.recart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.recart.com/compliance-protections/required-compliance/do-not-call-dnc-registry-sms-compliance.md).

# Do Not Call (DNC) Registry & SMS Compliance

Explains what the Do Not Call Registry covers and why it does not apply to SMS marketing the way it does to calls.

***

### What is the Do Not Call (DNC) Registry?

The Do Not Call (DNC) Registry is a national database managed by the Federal Trade Commission (FTC) in the United States. It allows individuals to opt out of receiving telemarketing calls from businesses, protecting consumers from unwanted sales calls.

***

### Does the DNC Registry Apply to SMS Marketing?

No, the DNC Registry does not apply to SMS marketing in the same way it applies to phone calls. Here’s why:

* The DNC list only regulates voice calls, not text messages.
* SMS marketing is governed by different regulations, including:
  * Telephone Consumer Protection Act (TCPA)
  * CTIA Messaging Principles & Best Practices
  * Carrier-Specific SMS Rules

***

### How Does SMS Marketing Stay Compliant?

Even though the DNC list doesn’t apply, businesses must still comply with **strict SMS marketing rules** to ensure they are messaging consumers legally. Key compliance requirements include:

#### 1. Obtaining Proper Consent (Opt-In Rules)

* **Explicit opt-in is required** before sending marketing texts.
* Consent must be **clear, documented, and verifiable**.
* Opt-ins can be obtained via:
  * Website popups
  * Keyword-based SMS opt-ins
  * Checkout forms

#### 2. Providing Clear Opt-Out Instructions

* Every marketing SMS must include a **clear way to opt out**, such as:
  * *Reply STOP to unsubscribe.*
* Opt-out requests must be **honored immediately**.

#### 3. Following Sending Restrictions

* **Quiet Hours:** Some states restrict SMS marketing during certain times (e.g., Florida and Oklahoma require no messaging between 8 PM – 8 AM local time). Default Quiet Hours are set from **8PM - 9AM** (Subscriber Timezone) in all Recart accounts.
* **Message Frequency & Transparency:** Clearly disclose how often messages will be sent.

***

### Best Practices for SMS Compliance

To stay compliant with U.S. SMS marketing laws, follow these **best practices**:

To ensure your SMS marketing is fully compliant:

✔ **Collect & store proper opt-in records** for every subscriber.

✔ **Include opt-out instructions in every message**.

✔ **Respect time-based restrictions** where applicable.

✔ **Use compliant messaging platforms** that enforce TCPA and carrier guidelines.

If you have any questions, do not hesitate to [contact the Recart Support team.](/contact-recart-support.md)  We'd be happy to help!


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.recart.com/compliance-protections/required-compliance/do-not-call-dnc-registry-sms-compliance.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.