SMS consent data is not stored as a regular database field — it lives in a dedicated system table tied to specific SMS Programs and Text Codes. This means standard data exports and imports will not capture or restore it correctly. This article explains how to extract, preserve, and re-import SMS consent data accurately.

What you need to know first

SMS consent is linked to a specific SMS Program and Text Code (Long Code or Short Code). The unique identifiers for SMS contacts are the Mobile Number and Country Code — not just the email address. Any export or import must include these fields to be valid.

Critical: Importing a "Yes" value into a custom text field called "SMS Consent" in your database will not enable the system to send SMS to those contacts. Consent data must reside in the system's Shared Channel Consent table to be recognized.

How to export SMS consent data

Option A: Database export with SMS consent included (recommended for bulk preservation)

1. Go to Data > Databases > Managed and select your database.
2. Click Export.
3. In the field selector, check the box for SMS Consent Data.
4. Run the export. The resulting CSV will include: Mobile Number, Consent Status, Consent Date, and the specific SMS Program Name for each record.

This generates a column for each SMS program and code, showing the current opt-in or opt-out status and the date of the last change.

Option B: Raw Recipient Data Export (most comprehensive)

The most comprehensive way to extract SMS consent is by using the Export Private/Shared Folder or Raw Recipient Data Export (RRDE). Because SMS consent is stored in a dedicated system table, the RRDE provides the most complete and reliable extraction, capturing consent data that may not surface through standard database exports.

Option C: Query method (for targeted consent lists)

You do not need to create a separate query for every consent type. Instead, create a single query using OR logic — for example, "Contact has opted in to Program A OR Program B" — and export that single list. The export file will contain columns for all programs, allowing you to review the status of each in one spreadsheet.

Option D: API retrieval (for programmatic or automated extraction)

For programmatic retrieval, use the Shared Channel Consent API. For bulk database maintenance tasks, the Export Mailing List API with the EXPORT_SMS_CONSENT parameter is more efficient than the REST message endpoints.

How to re-import SMS consent data after maintenance

To restore SMS consent data, you must use the SMS Consent Import tool — not a standard data import. This tool maps consent status back to the system's compliance tables correctly.

1. Prepare your CSV file with the required columns: Mobile Number, Country Code, Consent Status, Consent Date, and SMS Program Name.
2. Navigate to the SMS Consent Import tool in Acoustic Campaign.
3. Upload your file and map the columns to the corresponding consent fields.
4. Submit the import and verify that consent statuses have been restored in the Shared Channel Consent table.

Note: A standard database import will not write data to the Shared Channel Consent table, even if the column is named "SMS Consent." Always use the dedicated SMS Consent Import tool for this purpose.

Common mistakes to avoid

• Using a standard data import to restore consent: This will not work. Consent data must be imported via the SMS Consent Import tool to be recognized by the system.
• Excluding Mobile Number or Country Code from exports: These are the unique identifiers for SMS consent records. Without them, the data cannot be mapped back correctly on re-import.
• Creating separate queries for each consent type: This is unnecessary. A single query with OR logic across programs is more efficient and produces a complete picture in one export file.