- A cleaned source file with one contact per row
- Approved mappings for identity, consent, owner, tags, and custom fields
- A duplicate-handling decision and expected row count
- Authority to create or update the represented customer records
Upload and check automatic mapping
- Open Contacts → Import contacts and select the approved CSV or XLSX file.
- Confirm WRKZY detected the intended header row. At least Phone or Email must be mapped.
- Open Review field mapping. A source column can map to only one destination.
- Review Identity, Core profile, Relationship and segmentation, Consent, and Custom-field groups.
- Inspect ignored columns. Map a valid existing field, create a governed text field, or deliberately leave the column out.
Save a reusable import recipe only when future files use the same meaning—not merely the same column names. Recipes preserve mapping, relationship, overwrite, and automation decisions.
Choose execution policy
| Control | Decision |
|---|---|
| Add only | Existing phone or email matches are skipped |
| Update matching and add new | Matching contacts can receive approved mapped changes |
| Default owner | Assign accountability to newly imported contacts, or leave them unowned intentionally |
| Create missing companies or lists | Create referenced records, or skip rows whose relationship target is unknown |
| Overwrite groups | Decide whether mapped file values can replace identity, company, consent, or other current data |
| Automation policy | Run automations or pause them for the import |
Review the row plan
Use the filters for Ready, Updates, Identity conflicts, Invalid identity, Consent gaps, Duplicate, Missing company, Missing list, and Skipped. WRKZY shows an outcome preview for selected rows, including WhatsApp reachability, email reachability, and consent gaps.
- Fix safe source errors inline when the correction is unambiguous.
- Deselect any row whose outcome needs business review.
- Resolve in-file duplicates before execution.
- If selected rows claim consent, confirm the consent attestation only after reviewing the evidence columns.
- For runs above 250 selected rows with automations enabled, reconsider whether downstream volume is intended.
Run and verify
Choose Import selected contacts only when the selected importable count matches expectation. Keep the page open until WRKZY reports Imported, Updated, Skipped, Invalid, Failed, Duplicate, company links, and list memberships.
Open Import history immediately after the run. Confirm the file name, total and selected rows, consent attestation, automation dispatch status, and a sample of created and updated contacts.
Recovery
Do not upload the same file again to repair a partially understood result. Download the relevant exception set, correct only failed or skipped source rows, and use a new controlled run. If the run itself was wrong and the undo window is open, an authorized creator, owner, or admin can undo it. Undo archives new contacts, restores imported changes, and removes imported notes and memberships while preserving later concurrent edits; external automation effects remain.
- Phone or email mapping confirmed
- No source column mapped twice
- Overwrite and relationship policies reviewed
- Only intended rows selected
- Consent attestation supported
- Results opened in Import history