> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dispoiq.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Importing and exporting contacts

> Map CSV records, preserve restrictions and request eligible exports.

Last updated: October 8, 2026.

Prepare the file, check the column mapping, then review the import results before using the list. An imported phone number is a contact detail, not proof that it belongs to the intended person or that you may text them.

This guide covers the Contacts CSV workflow and its rejected-row download where available. Other exports require confirmation of their scope and your rights. It does not promise a full-workspace download, expand a data license or change accepted charges or refund rights.

## 1. Check your authority and keep the source file

Upload only information you are entitled to provide and process for the intended business use. Keep the original file and the source, license and permission records you need. A list supplied by another business can carry restrictions even when you upload it yourself.

Your own contact records and notes differ from sourced discovery or enrichment results. A mixed record can contain both. Saving, paying for or exporting a sourced phone number does not transfer ownership or give unrestricted onward-use rights. See the [Buyer Data & Permitted Use Policy](https://docs.dispoiq.app/policies/buyer-data).

## 2. Prepare a CSV and map its columns

In an activated workspace with authorized owner or admin access, open **Contacts → Upload file**. Use a CSV with a header row and distinct column names. Convert a spreadsheet workbook to CSV before selecting it. Keep phone numbers and ZIP codes as text so the spreadsheet does not alter the values.

The mapping step offers these fields:

| Contact information | Available mapping |
| - | - |
| Person | First name, Last name |
| Contact details | Phone, Email |
| Business description | Entity name, Buyer type |
| Investment property | Investment property address, Property city, Property county, Property state, Property zip |

Map **exactly one column to Phone**. Review suggested mappings and sample values, including any saved mapping reused with a new file. A column left on **Ignore** is not imported into the mapped contact record. These fields do not describe every kind of record stored elsewhere in your workspace.

Use the supported phone format: a 10-digit number or `+1` followed by 10 digits. Review the resulting number, especially if the source includes extensions or other text. Recognized formatting does not verify the number's owner, destination country, line type or ability to receive messages. Messaging remains limited to the US and Canada through eligible routes actually available to your workspace.

Choose **Continue**, check **New group name** and the mapping, then choose **Start import**. A preview shows sample rows; it does not validate the entire file. If you save a mapping, check it again whenever source headers or meanings change.

If **Upload file**, a mapping option or the saved import report is unavailable, ask your workspace administrator or **[support@dispoiq.app](mailto:support@dispoiq.app)** to check your access and the workflow offered to your workspace. Follow any file, row, header or cell limits actually shown. If a limit or error is unclear, ask support before trying a larger file or repeating a submission; this guide promises no particular capacity.

For an import problem, provide the workspace, filename, approximate submission time, any saved import reference and the displayed error. Describe the intended mapping without emailing the full list. Support will check the available access, mapping and saved processing evidence with authorized staff, explain the confirmed result or remaining uncertainty, and identify the next supported step. A preview, successful submission or processed count does not prove every row is correct or newly created. Check the existing saved import before starting another; this process guarantees neither completion nor automatic rollback of records already processed.

## 3. Read the outcome, including duplicate matches

Use **Contacts → Imports** to review the saved import and its report. “Rows processed” includes outcomes other than newly created contacts. Counts can change while an import is still running.

| Report outcome | What to review |
| - | - |
| Imported | A new contact was created; check its identity and mapped values |
| Duplicate in file | Another row has the same normalized phone; review both rows rather than assuming they represent different people |
| Already a contact / Already a buyer | The number matched an existing record; check that the association is correct |
| Suppressed | A number-level restriction was detected; do not re-upload it to evade the restriction |
| No phone / Invalid phone number | Correct missing or unrecognized phone data if you have a reliable authorized source |
| Processing failed / Still processing | Check the saved import's current state and relevant error before starting again |

Phone-based matching is not proof of identity. When several contacts share a number, the import can attach to one existing contact without merging all of them. Existing records can receive missing details from an import; it is not a general overwrite tool. Previously deleted records can still affect duplicate matching.

Review data-quality warnings even when a row was imported or matched. An invalid email can be flagged separately from the phone-based outcome. Correct the source and verify the intended record; do not assume every imported field was independently validated.

If progress stops refreshing, check the saved import before re-uploading. Closing the dialog or losing the browser connection does not by itself establish that processing stopped. Send support the import reference and error if the state remains unclear.

## 4. Correct rejected rows without bypassing restrictions

Where available, open the import report and choose **Download rejected rows**. This CSV covers the report's missing-phone, invalid-phone, duplicate-in-file and processing-failed outcomes. It excludes successfully resolved rows and suppressed rows from that default download. While processing continues, it is a snapshot of the applicable outcomes recorded so far.

The file contains stored mapped fields, row numbers and reasons. It does not reconstruct ignored columns or the original CSV's exact formatting, and it is not a complete contacts backup. Keep your original source file.

Correct only substantiated errors and review the mapping before a new import. A duplicate may require reviewing or consolidating your source rows rather than changing the number to force another record. Do not remove suppression evidence or re-import a withdrawn number under another record, group or workspace.

If you request a separate paid lookup to recover contact details, check the accepted price and chargeable outcome first. Finding a number does not establish permission to message it. This guide sets no new import or lookup fee.

## 5. Keep consent and opt-outs separate from contact fields

The listed CSV mapping fields do not include written-consent evidence or opt-out settings. Do not assume an “opted in,” “do not contact” or similar column updates messaging permission or suppression. Keep original disclosures, affirmative actions, dates, sender/program scope and withdrawals, and use a verified supported process to apply the relevant restrictions before sending.

The [Messaging & Communications Policy](https://docs.dispoiq.app/policies/messaging) requires prior express written permission for customer-initiated SMS/MMS. Its narrow exception for a directly relevant response to a recipient-initiated text in the same conversation does not authorize a campaign. An import status, group membership, phone match or registration approval is not consent.

Honor existing opt-outs and external withdrawal evidence. A clean import outcome does not prove that every applicable restriction was checked. See the [consent guide](/help/messaging-consent) and [STOP, HELP & Suppression Lists](/help/stop-help-suppression).

Before sending to imported contacts, keep the original permission and withdrawal evidence associated with the correct number, business sender and message program. Use an appropriate secure record location and a supported review process; the CSV fields above do not attach signed permission, import an outside opt-out or turn a default phone flag into evidence.

If your source list includes a withdrawal, wrong-number report or restriction that the mapping cannot apply, pause the affected sending and contact **[support@dispoiq.app](mailto:support@dispoiq.app)** before using those records for messages. Provide the import or contact reference and the restriction's scope; ask for a secure way to supply sensitive evidence. Support records the issue, checks relevant authority proportionately and coordinates authorized handling of the affected contact, number, campaign, queue and other sending paths where necessary. An imported or apparently sendable record does not confirm that a withdrawal has been honored. If the relevant permission or restriction remains uncertain, keep the potentially affected communications paused until it is resolved. Do not send a promotional test, change a record flag or reimport a number to bypass that review.

This process does not promise an automatic consent-file attachment, bulk opt-out importer, universal cross-channel enforcement or guaranteed restoration. A request for review is not approval to send; applicable opt-outs and mandatory handling deadlines remain controlling.

## 6. Request an eligible export and protect the copy

Ask **[support@dispoiq.app](mailto:support@dispoiq.app)** about exports beyond the specific rejected-row download. Identify your workspace, authority and requested record categories. Confirm what is included, the available format and delivery method. Protect exported personal information and keep its source restrictions and opt-out evidence with the records you use.

After paid subscription access ends, you have **90 days from that end date** to request export of Customer Content and Recipient Submissions you are entitled to receive. This does not extend normal paid app access or grant unrestricted export or retention of Licensed Data.

A request received within the 90-day request window is not canceled merely because that window expires. DispoIQ will preserve the information it is authorized to provide and needs to fulfill that request until the request is fulfilled or otherwise lawfully resolved, except to the extent an earlier deletion obligation requires a different result. Routine deletion after 180 days will not by itself defeat such a timely request.

DispoIQ may delete eligible records **after 180 days from the end of paid access**; this is not a promise that every copy is erased on day 180. These account-closure intervals do not postpone valid individual privacy requests or expire retained purchased wallet funds. See the [Data Retention, Export & Deletion Policy](https://docs.dispoiq.app/policies/data-retention) and [Terms of Service §14.4](https://docs.dispoiq.app/policies/terms).

Support records export requests, checks identity or workspace authority proportionately, and confirms the record categories you are entitled to receive. We will coordinate the available retrieval and an appropriate secure delivery method with authorized staff, including requests made after paid access ends. A paid-app access restriction is not a reason to discard a timely eligible request. We will explain the records supplied and any lawful exclusions, remaining retention or further action, while protecting other people's confidential information. This process creates no particular file format, full-workspace backup, instant download or fixed completion time; applicable rights and deadlines remain controlling.

Source permissions and required downstream terms must be established before affected sourced fields are delivered or reused. An export control or paid lookup does not clear those requirements. Information subject to an earlier no-sale or incompatible disclosure commitment must remain restricted until the proposed use is consistent with that commitment and the required lawful basis, notices, permissions and rights controls exist. Exporting or combining a record does not erase its restrictions, withdrawal history or the customer-provided information and future-use protections in the [Privacy Policy](https://docs.dispoiq.app/policies/privacy). A source restriction does not remove a non-excludable individual privacy right. This guide does not certify that every source permission, historical disclosure or export tool has already been verified.

For help, email [support@dispoiq.app](mailto:support@dispoiq.app) with the import or record reference and a short description. Avoid passwords, full lists and unnecessary personal information; ask how to submit sensitive evidence securely. This help article does not replace your accepted agreement or itself incorporate another document. Referenced policies apply as binding supplements only when their identified versions are expressly agreed.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.