Yes. A property team can use the DripTell contact import guide to move a prepared CSV into its contact workspace without sending a WhatsApp message. The import creates or prepares contact records. It does not turn an old spreadsheet into permission to contact every person on it.
That distinction matters when an agency moves buyer enquiries, landlord relationships or valuation requests. The useful outcome is a reviewable contact base, with unclear rows held back from communication.
What the import does
The live DripTell flow supports a CSV upload, mapping each source column to its intended field, checking sample records and reviewing duplicates or invalid values. These are native contact controls reflected in the current CRM product page.
An import does not send a message. Public evidence does not establish that it imports old conversations, creates property objects, connects a portal or validates old consent. Those are separate implementation questions. The benefit is less retyping and a consistent record the team can review.
Prepare the property CSV
Start with a copy of the source file, not the only operational copy. Keep one row per person where practical and choose a stable identifier such as an international-format mobile number. Remove formula columns, private staff notes and fields nobody can explain. Do not upload purchased lists or people who would not reasonably expect contact from the agency.
Property exports often mix durable customer facts with temporary listing details. A preferred area may help later. A note about one unit belongs with that conversation or opportunity, not as a permanent buyer description. Decide the boundary before upload.
Map stable contact fields
Use the contact fields guide to map only columns with a defined owner and meaning. Preview several records, including sparse and unusual rows, before accepting the mapping.
- 1Clean the sourceKeep a stable identifier and remove columns that have no clear destination.
- 2Map each fieldMatch names, phones and useful stable preferences to the intended DripTell fields.
- 3Review exceptionsCheck samples, duplicates and invalid values before accepting the batch.
- 4Decide messaging separatelyVerify consent, suppression and campaign eligibility before any outreach.
| Source column | DripTell destination | Handling decision |
|---|---|---|
| Mobile number | Phone | Normalize to international format and use as a matching signal |
| Full name | Name | Keep the customer supplied spelling where available |
| Relationship type | Contact field | Use a controlled value such as buyer, landlord or tenant |
| Preferred area | Contact field | Import only when it remains useful beyond one listing |
| Listing note | Do not map blindly | Keep property-specific context with the relevant conversation |
A clean omission is safer than a field whose meaning changes between agents.
Review duplicates and invalid rows
Treat sample and exception review as a release gate. Check phone formats, required identifiers and field destinations. Review duplicates rather than assuming two similar records are one person. Use the merge contacts guide only after a genuine duplicate is confirmed.
Keep rejected rows on an exception list with a reason, owner and next action. A missing country code may be repairable; a shared family number needs human review. Keep malformed rows out until identity is clear.
Keep permission separate from the record
A contact record says who the team knows. Consent says whether and why the team may contact that person. Keep the evidence distinct with the consent records guide.
The current WhatsApp Business Messaging Policy requires a phone number or username and opt-in before a business contacts someone, and it requires opt-out requests to be respected. An old CRM flag can be useful evidence, but it should carry its source, date and scope. If those are unclear, do not translate “imported successfully” into “ready for campaign.”
Run a controlled first import
Use a privacy-safe sample with one clean buyer, one missing optional field, one likely duplicate and one invalid phone value. Confirm mapping and exceptions before an operations owner approves the larger batch.
After import, inspect records inside DripTell and document what the team will do with rejected rows. Keep messaging disabled until consent and suppression checks are complete. For a wider property workflow, review the real-estate page, but do not assume it proves a native portal integration.
To test the approach, bring a small sanitized CSV to a DripTell walkthrough and verify the fields and limits in your workspace.
Frequently asked questions
Does importing contacts send a WhatsApp message
No. The import prepares contact records. A later message is a separate action with its own consent, eligibility, template and timing requirements.
Which property details should be mapped
Map stable customer facts that have a defined future use. Keep listing-specific questions, viewing outcomes and negotiation notes with the relevant conversation or property process.
What happens when DripTell finds a duplicate
Review it before merging or updating anything. Similar names are not proof of one identity, and shared household numbers need human judgment.
Does an old opt in move with the CSV
Not automatically as a trustworthy permission. Preserve the source, date, channel and scope of the evidence, then check whether it remains valid for the message you plan to send.
Want help applying this guide?Ask the DripTell team
From reading to action
Want help applying this to your business?
Share your details. We will read the article you are on and start with a useful answer for your team.
DripTell Editorial
Practical guidance reviewed by the DripTell product and customer workflow team.
See how DripTell checks product claims, uses primary sources and handles corrections.
Editorial and source policy
