Good contact organization starts before import
The planned Cadensy contact workflow treats data quality, commercial status and permission to email as separate concerns.
Prepare the source file
Keep one person per row and use a clear header for each field. Normalize email addresses, dates and country codes before importing. Decide which column is the unique identifier and how an existing contact should be updated. Preview the mapping and resolve duplicates before committing changes.
Separate the record from permission
A customer, prospect or subscriber label describes a relationship; it does not establish permission for every type of message. Store the source and purpose of permission separately from commercial status. Lists and tags should have documented meaning and an owner. Restrict access to fields that are not needed for a campaign.
CSV and Excel import, duplicate resolution, lists and segmentation are planned Cadensy capabilities. No contact upload is performed by this public page.
Have a question about the Cadensy project?
Talk with us about current scope and product availability.