Importing contacts

Turn an authorized file into clean, reviewable customer records without uncontrolled duplication.

Expected outcome: Valid rows create or update the intended contacts, exceptions remain reviewable, and a sample proves identity and consent fields.

1. Treat import as a controlled data change
The goal is trustworthy customer context, not the largest possible row count.

2. Decide which records and fields belong in WRKZY
Remove unnecessary columns, confirm lawful use, and identify the fields teams actually need for segmentation and service.
Review point: Import only authorized and operationally useful data

3. Use the template and normalize identity fields
Keep one header row. Standardize phone and email values, dates, consent evidence, owner names, tags, and custom-field formats.
Review point: A phone or email is required for identity resolution

4. Upload CSV or Excel once
Wait for parsing to finish. Do not submit the same file again because the page appears slow.
Review point: Upload → Map → Review → Results

5. Map identity, consent, ownership, and custom fields deliberately
Do not force ambiguous columns into convenient fields. Leave a column unmapped when its meaning is unclear.
Review point: Correct mapping matters more than complete mapping

6. Resolve validation and duplicate warnings before the run
Understand whether a row creates, updates, conflicts, or is quarantined. Export exceptions when a source correction is safer.
Review point: Never merge uncertain identities just to clear a warning

7. Start the import and wait for one terminal result
Review created, updated, skipped, and failed counts. Preserve the job reference and exception file before retrying anything.
Review point: Retry only failed rows after correcting the cause

8. Sample records across every result type
Open new and updated contacts. Verify identity, timeline, owner, tags, custom fields, consent, and list membership.

This silent visual walkthrough was screen-recorded from the sanitized Acme Retail demo workspace. Follow the linked written guide for exact prerequisites, role boundaries, edge cases, and recovery.