Importing contacts
Bring in past enquiries and customer lists from Excel; prepare the file, map fields and consent, and tag the import.
3 min read
Enquiry lists built up over the years are one of an agency's most valuable assets: owners who had a valuation and then held off selling, buyers waiting for the right budget, tenants whose lease is about to end. Import brings these lists in at once, with fields and consent mapped correctly so they're ready to use.
Our team usually runs the first import with you during setup. This article is for lists you import yourself later.
Before you start
- Import permission is usually limited to Admin users.
- The file must be CSV (in Excel: Save As → CSV UTF-8). One sheet, with headers in the first row.
- Split very large lists; file size is limited.
1. Preparing the file
| Column | Example | Tip |
|---|---|---|
first_name, last_name | Mert, Özkan | Keep first and last names in separate columns. |
phone | +905•••770512 | Always with +90. A leading 0 causes problems. |
email | mert@mail.com | Remove invalid addresses. |
enquiry_type | Seller | Buyer / Seller / Tenant / Landlord; spell them consistently. |
area, rooms, budget | Ataşehir, 3+1 | Mapped to Property enquiry fields. |
marketing_consent | Yes / No | Only documented consent counts as "Yes". |
Tip
Save the file as UTF-8 so Turkish characters (ş, ğ, ı) don't break. Open it in a text editor to check before uploading.
2. Uploading the file
- On Contacts, click Import and choose what you're importing: Contacts only, or Contacts and Opportunities (to place contacts straight into a pipeline stage; see Importing opportunities).
- Drag and drop your CSV file.
- Choose the import type: Create and update contacts (adds new ones, updates existing ones), new contacts only, or updates only. If unsure, choose Create and update.
3. Mapping fields
- Check which field each column goes to. Headers are matched automatically where possible; fix wrong ones from the drop-down. Set columns you don't want, such as internal notes, to Don't import.
- Map the property columns to the fields in the Property enquiry group, and the consent column to Marketing consent in the Consent group.
- If you're updating existing contacts, tick Don't update empty values so blank cells don't wipe existing data.
4. Tags and final check
- Add a shared import tag to everyone (e.g.
import-2026-10). If something goes wrong you can find, fix or delete these contacts in one go. - Optionally create a smart list for the new contacts.
- Confirm the contacts agreed to be contacted.
- Click Import.
The import runs in the background. Follow progress under Contacts → Bulk Actions; Show Stats shows successful and failed rows and lets you download the error log.
Important
Don't import bought lists or lists of unknown origin. Sending promotional messages or making campaign calls to people without consent breaches İYS and KVKK rules and lowers your WhatsApp number's quality rating. After importing past enquiries, only put contacts with Marketing consent = Yes into promotional lists. See İYS and KVKK.
Reviving past enquiries
Imported past enquiries can be revived with the assistant's outbound call campaigns or with long-term nurture messages: "Last year you were looking for a 3+1 in Ataşehir; are you still looking?" These campaigns only reach consenting contacts within set calling hours; ask your consultant to set one up. See Outbound campaigns and Nurture campaigns.
Duplicates
Existing contacts are matched on phone and email. With Create and update, a matching contact is updated instead of duplicated. See Duplicates and merging.
Common issues
Some rows weren't imported. Download the error log from Bulk Actions; usually it's an invalid phone or email.
Turkish characters are garbled. The file wasn't UTF-8. Re-save it and import again in update-only mode.
Phones are in the wrong format. Numbers were uploaded without +90. Fix the file and re-import with Update existing contacts.
Related articles

Didn't solve your problem?
Ask the assistant or message our support team.
