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.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:
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 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.
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.