> 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/latest-news/introducing-automated-list-cleaning.md).

# Introducing Automated List Cleaning

Announces Automated List Cleaning, which removes unreachable or high-risk numbers from your SMS list automatically.

A Smarter, Safer SMS List — Automatically

Keeping an SMS list healthy is critical — but manually maintaining it is time-consuming and easy to miss.

That’s why Recart now runs **Automated List Cleaning** in the background for every merchant.

This new feature automatically removes unreachable, deactivated, or high-risk phone numbers from your SMS list — helping improve deliverability, reduce wasted SMS costs, and lower compliance risk.

### What gets cleaned automatically

* Deactivated or disconnected phone numbers
* Known TCPA litigators
* Landlines
* Reassigned numbers (where legally required)

![Subscribers chart - cleaned by Recart\_](https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2Fb8MbEmnJxTsUi0rgw6zw%2FSubscribers%2520chart%2520-%2520cleaned%2520by%2520Recart_.jpg?alt=media)

### What you’ll see in your account

* A new **List Cleaning** chart on the Subscribers page
* A **Cleaned by Recart** count
* An **Estimated SMS cost saved** metric
* Clear removal reasons logged in subscriber profiles

There’s nothing to enable — the feature runs automatically and works quietly in the background to protect your account.


---

# 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/latest-news/introducing-automated-list-cleaning.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.