Property leads are not retail orders. One buyer enquires about three units, a couple uses two phone numbers, and the same person arrives through a portal, a Facebook form, a WhatsApp message and a walk-in. The system that wins gives the right agent enough context to call first and leaves a record of what happened.
This buying guide covers the requirements, the five ways to buy, a scorecard, a pilot and the ownership terms that decide whether you control the pipeline or rent it.
What the sales process actually requires
- Multi-source capture. Property portals, Facebook lead forms, WhatsApp, phone calls, walk-ins, referrals and repeat buyers.
- Identity and dedupe. One buyer record across several phone numbers, spellings and enquiry sources.
- Assignment and response rules. Which agent gets which project, what happens after hours, and when a lead escalates.
- Visit and offer tracking. Site visits, follow-ups, negotiation stage and the reason a deal stalled.
- Document collection. NID, booking forms, payment schedule and handover documents, with access control.
- Consent and opt-out. A record of what the buyer agreed to receive, and a working way to stop.
- Handover. What sales passes to legal or handover teams, and what remains visible to the buyer.
- Reporting. Source performance, response time, visits and conversion by project and agent.
Five ways to buy
A real-estate vertical CRM understands projects, units and visits out of the box. Check whether its model matches how you sell, especially if you handle rentals, resale and pre-launch inventory together.
A general CRM plus integration is flexible and familiar to sales teams. The cost moves into integration, custom objects and the discipline of keeping the pipeline stages consistent.
A WhatsApp-first sales tool matches how buyers actually communicate and can shorten response time. It carries the highest compliance and ownership risk if the number or account sits with the vendor.
A marketing agency automation can build capture and follow-up quickly around campaigns. Ask who owns the workflow, the data and the accounts when the retainer ends.
A custom workflow on your own stack fits a distinctive sales process and integrates with your land or finance records. It also needs an owner, documentation and a maintenance budget.
A scorecard
| Criterion | What to test | Weight |
|---|---|---|
| Source coverage | Every channel you use, including walk-ins and calls | High |
| Dedupe quality | Same buyer across numbers and spellings | High |
| Assignment logic | Project, language, rotation and escalation | High |
| WhatsApp compliance | Opt-in, template approval and opt-out | High |
| Visit and offer tracking | Stage history, not just a status field | Medium |
| Mobile usability | Agent workflow on a mid-range phone | Medium |
| Reporting | Source, response time and conversion by agent | Medium |
| Data ownership | Export, number portability and account ownership | High |
Warning signs
- Automation built on unofficial WhatsApp access rather than the official platform.
- No consent capture, or an opt-out that only exists in a spreadsheet.
- Per-agent pricing that excludes the integration or message fees.
- A demo on invented leads with no duplicate or after-hours scenario.
- No export of leads, activities and consent records.
- Lead scoring sold before there is enough history to score.
- No visit or offer object, so the pipeline stops at "contacted".
- The agency or vendor owns the business number and the messaging account.
Pilot on one project
Pick one project and one sales team. Record the current first-response time, duplicate rate, contact rate and visit bookings for two weeks before switching anything on. Then run the new flow for four weeks on the same measures.
Test the awkward cases deliberately: a buyer who enquires on three portals, a couple with two numbers, a lead that arrives at midnight, an agent on leave and a buyer who asks to stop receiving messages. Acceptance is a clean record for each case, not a successful demo.
Keep the old channels running in parallel during the pilot so a failed message does not lose a buyer. Review the results with the agents who made the calls, not only with management.
Ownership and contract terms
- Account ownership. The WhatsApp Business Account, phone number and portal connections stay in your name.
- Consent evidence. Where the opt-in was captured, when, and how it can be produced later.
- Template approval. Who writes and submits message templates, and who can change them.
- Data processing. What the vendor may see, where it is stored and how long it is retained.
- Subcontractors. Any call centre or messaging partner that touches lead data.
- Exit. Export format, number portability, account transfer and deletion confirmation.
- Pricing basis. Users, leads, messages and storage priced separately, with the overage rule written down.
Buy, build or assemble
Buy when the sales process is conventional and speed matters. Build when the process is genuinely different, or when the system must connect to project inventory, land records or a finance workflow that no product covers. A middle path is common: a CRM for the pipeline and a small custom service for portal capture and dedupe.
A 60-day rollout
Weeks 1–2: map every lead source, the current assignment rules and the places leads are lost.
Weeks 3–4: clean the existing database, define dedupe rules and configure assignment and escalation.
Weeks 5–6: set up consent, message templates and the visit and offer stages; train agents on a phone, not a projector.
Weeks 7–8: run the pilot project, review the baseline measures and fix the route before extending to other projects.
Measures to review
First-response time by source, contact rate, duplicate rate, visit booking rate, visit-to-offer conversion, SLA breaches, opt-out rate and cost per qualified lead. Calculate the last one as total source and tool cost divided by qualified leads, not by all enquiries, or the number will flatter the wrong channel. Review weekly during the pilot and monthly afterwards; a process reviewed quarterly drifts back to the group chat.
Where this fits in our work
Property lead automation is delivered through Business Automation, with CRM and lead management setup covering capture, assignment and reporting. The pricing page sets out how setup and ongoing care are priced. For the failures this design is meant to prevent, read real estate lead automation problems and fixes.
Sources
- Meta, WhatsApp Business Cloud API overview, accessed 17 November 2026.
- WhatsApp Business, Messaging policy, accessed 17 November 2026.
- HubSpot, CRM contacts API, accessed 17 November 2026.
- NIST, Privacy Framework, accessed 17 November 2026.
- DataGuidance, Bangladesh jurisdiction overview, accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.