> 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/sms/subscribers-and-lists/import-sms-subscribers.md).

# Import SMS Subscribers

Shows how to import an existing SMS subscriber list into Recart, including CSV file requirements and consent rules.

Use this guide to import your existing SMS subscriber list into Recart so you can start sending them campaigns right away.

### Before You Begin

To comply with SMS marketing regulations, you can only message subscribers who gave explicit consent to receive promotional texts. Make sure every contact in your import has proper opt-in records before proceeding.

### CSV File Requirements

Your file must meet these criteria:

* **Format:** CSV only
* **Header row:** Required
* **Phone number column:** Required
* **File size:** Maximum 50MB

**Important Note:** Always include the **country code** - e.g., +12025550123, not 2025550123. A missing country code is the most common reason an import is not successful.

**Optional columns you can include:**

* First name
* Last name
* Date of birth
* Country
* Region
* City
* ZIP code
* Timezone
* Locale

**Note:** If your CSV contains columns beyond those listed above (such as email), you can still upload the file, Recart will simply skip those fields during import.

#### Formatting requirements

A few fields must follow a specific format, or they won't import correctly:

**Country:** Use the 2-letter ISO country code — e.g., US, not United States. If the country code is missing or incorrect, that contact's region, city, and ZIP won't import. See the [full list of 2-letter ISO country codes](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2#Officially_assigned_code_elements).

**Timezone:** Use the IANA timezone format — e.g., America/Los\_Angeles, not PST or Pacific Time.

**Locale:** Use the language\_COUNTRY format — e.g., en\_US, en\_GB, fr\_FR. See the [language tag reference](https://www.w3.org/International/articles/language-tags/) for more options.

**Date of birth:** Use the YYYY-MM-DD format — e.g., 1990-05-14.

### How to Import Subscribers

1. Go to **Subscribers** in the left-hand menu.
2. Click **Import CSV** in the upper right corner.

![Subscribers\_Add](https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2FqyFQZqvifNELGuWrsXMC%2Fimport-sms-subscribers-1.png?alt=media)

3. Choose whether to add subscribers to an existing list or create a new list.
4. If creating a new list, **enter a name** for it.

![Subscribers\_Choose+Add List](https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2FmuRGMpbQRTGvebsIo5wB%2Fimport-sms-subscribers-2.png?alt=media)

5. Click or drag your CSV file into the upload area.
6. Match your CSV columns to the correct Recart fields using the dropdown menus. Leave any unsupported columns unmatched.
7. A compliance declaration appears. Enter your name and email address to confirm you have proper consent to message these subscribers and click **Continue.**

![Subscribers\_Declaration](https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2FDCTfl08qTJMSJXmPCWhq%2Fimport-sms-subscribers-3.png?alt=media)

8. Review the import summary on the **Import Review** screen.
9. Click **Import** to finalize.

**Note:** Recart does not store your CSV file. It is deleted after the upload completes.

### Understanding Import Statuses

Your imports appear on the **Subscribers** page. Each import displays one of these statuses:

* **Uploading** – Import is in progress
* **Uploaded** – Import is complete

Once uploaded, you'll see a breakdown of:

* **New subscribers** – Contacts added to your list for the first time
* **Updated subscribers** – Existing contacts whose information was refreshed
* **Failed imports** – Contacts that did not meet the criteria

**Note:** The import name matches your CSV file name. This cannot be edited in Recart.

### What Happens to Existing Subscribers

When you import a contact that already exists in your Recart list, here's what happens:

| Scenario                                             | Result                                         |
| ---------------------------------------------------- | ---------------------------------------------- |
| Phone number is new                                  | New subscriber created                         |
| Phone number matches an existing subscriber          | Existing subscriber updated                    |
| Phone number matches but subscriber has unsubscribed | Subscriber is **not** updated or re-subscribed |

### Best Practices

* **Required:** Only import contacts with documented opt-in consent.
* **Recommended:** Clean your CSV before uploading - remove duplicates, incomplete numbers, and landlines.
* **Recommended:** If your file exceeds 50MB, split it into multiple CSVs and upload separately.
* **Avoid:** Uploading purchased lists or contacts who haven't explicitly opted in.

Recart is keeping your Subscriber list compliant with our Automated List Cleaning.

### Troubleshooting

**If some subscribers weren't imported:** Check that all phone numbers are valid and correctly formatted. Common issues include:

* Missing country code (e.g., 2025550123 instead of +12025550123) — this is the most common reason an import fails
* Toll-free numbers with extensions
* Landlines (not mobile numbers)
* Incomplete or incorrectly formatted numbers

**If a contact's region, city, or ZIP didn't import:** Check that the Country column uses the 2-letter ISO code (US, not United States). If the country code is missing or incorrect, the region, city, and ZIP for that contact won't import.

**If you need to delete an import:** There is no self-serve option to delete imported contacts. Contact os to request removal or unsubscription of an imported list.

**Example CSV:**

![](https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2FKm6igtNEDGpTufVC3V0X%2Fimport-sms-subscribers-4.png?alt=media)

You can also download our example CSV file for reference in your [Subscribers import page](https://app.recart.com/subscribers/import).

![](https://2167119381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2I45aTZ733MBi8Vps3Ib%2Fuploads%2FQ4S8ikSSI2SfEPpU6ITK%2Fimport-sms-subscribers-5.png?alt=media)

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/sms/subscribers-and-lists/import-sms-subscribers.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.