Spreadsheets often contain mixed phone formats, empty required fields, duplicate rows, old consent states, and columns whose meaning is clear only to the person who exported them. Sending directly from that file turns data ambiguity into delivery risk.
IntelliSend treats contact import as a workflow. A group is created, the file is uploaded, source columns are mapped, records are processed, and the resulting contacts can be previewed by validation status.
Identify the phone field first and confirm how country codes are represented. Map names and custom fields only when their source is consistent. Unused columns do not need to enter the messaging system.
If a required value cannot be derived safely, mark the record for correction instead of guessing. A smaller valid audience is more useful than a larger audience with uncertain destinations.
The import status and preview separate valid records from records that need attention. Use that point to correct individual contacts, remove bad rows, and confirm that the group count matches expectations.
Opted-out contacts require special care. Importing a newer file should not silently erase an existing marketing opt-out state.
Document who supplies the file, who approves field mapping, and who resolves invalid records. For recurring imports, keep the source format stable and review changes before uploading.
The safest import is repeatable: known schema, clear mapping, visible validation, preserved consent state, and an audience owner who signs off before the campaign starts.
