This is the capture layer that catches the duplicate before it embarrasses you — pulling every enquiry from MagicBricks, 99acres, Housing and NoBroker into one CRM, deduping on arrival, and assigning each lead to the right agent in seconds.
For channel partners & builder sales teams · the top of the funnel · capture → dedupe → assign · scoring and nurture live downstream.
A real estate lead-capture CRM pulls every property enquiry — from MagicBricks, 99acres, Housing.com, NoBroker, your website, and walk-ins — into one place, detects duplicates so the same buyer isn't worked by two agents, and assigns each lead to the right agent in seconds with a consent-based WhatsApp acknowledgement. This page is the capture layer at the top of the funnel. The lead scoring and drip nurture that follow are the separate marketing-automation solution; the site-visit booking is the appointment-scheduling solution; and rich listings plus portal syndication are property listings showcase.
A 2BHK in a Jaipur project gets advertised on three portals at once. Within an hour the same buyer, Mr Khandelwal, raises his hand on two of them and walks into the office. Here's the capture log — and the moment the duplicate gets caught.
| Time | Source | What the CRM did |
|---|---|---|
| 10:02 | 99acres | Captured · new lead · source tagged · assigned to Whitefield-equivalent zone agent by rule |
| 10:04 | WhatsApp ack | Consent-based DLT utility acknowledgement sent — buyer knows the firm received it |
| 10:31 | MagicBricks | Same number + same property → flagged DUPLICATE on capture, linked to the 10:02 lead, no second agent assigned |
| 11:15 | Walk-in | Front desk logs him; CRM matches the number → same lead, no third record created |
| 11:16 | Owner clear | One lead, one assigned agent, three sources recorded — agent sees the full enquiry trail |
| → | Handoff | Lead now flows downstream to nurture/scoring and, when ready, site-visit booking |
Leads sit in the 99acres panel, the MagicBricks panel, the Housing inbox, and a website email — each watched by a different person, none watched on a busy day. A paid lead goes cold because no one was looking at its particular inbox.
The same buyer enquired on two portals, so two agents call him within the hour. He concludes the firm is disorganised — and that impression costs more than the duplicate did.
An enquiry lands in a shared inbox and everyone assumes someone else will call. By the time anyone does, the buyer has booked a site visit with a competitor who replied in ten minutes.
Money goes to all four portals every month. At quarter-end nobody can say which one actually produced buyers, because the leads were never captured in one place with their source intact.
Link the firm's MagicBricks, 99acres, Housing.com and NoBroker accounts, the website enquiry form, and a way to log walk-ins and calls. Every enquiry now lands in one CRM instead of four inboxes and a notebook.
When the same buyer enquires for the same property through two portals, or rings after filling the website form, the CRM detects the duplicate on capture — by phone number and property — so two agents never end up calling one buyer.
Each new lead gets a consent-based WhatsApp Business utility acknowledgement under TRAI TCCCPR 2018 DLT within seconds of arriving — the buyer knows the firm received the enquiry, before a competitor calls them first.
The lead is assigned by rule — locality, property type, or round-robin — so it has a clear owner from the first minute, not after it has gone cold in a shared inbox.
Once captured and assigned, the lead moves downstream: the marketing-automation solution takes over scoring and drip nurture, and the appointment-scheduling solution handles the site-visit booking. This page's job ends at a clean, owned, acknowledged lead.
The instant acknowledgement is a consent-based WhatsApp Business utility template, sent through Databus as a Meta Business Solution Provider — a transactional confirmation the buyer's enquiry was received, not unsolicited marketing. No mass dialling, no spam blasts.
Enquiry data is captured under Section 6 consent, for the limited purpose of responding to the enquiry. The Act is phased — Phase I notified 13 November 2025, full compliance 13 May 2027 — and capture is built to that consent model rather than against it.
Every captured enquiry is stored as a Section 65B-admissible electronic record with source, timestamp, and consent state — useful for a channel partner who needs to show which firm first registered a buyer for a project.
Framework references: TRAI TCCCPR 2018 (DLT registration via Databus as Meta BSP); Digital Personal Data Protection Act 2023 §6 (Phase I notified 13 Nov 2025; full compliance 13 May 2027); Information Technology Act 2000 §65B (admissibility of electronic records). EstateDeck never holds buyer funds and is not a payment aggregator — capture is about contact and assignment, not money.
EstateDeck splits the property sales funnel across three solution pages on purpose, so each ranks for its own stage and none competes with the next. This is the upstream capture stage.
Portal-to-CRM, dedupe, first-touch assignment, WhatsApp ack
The job is identical — get every lead in, deduped, owned; the volume and the assignment rules change with the firm.
A six-agent firm reselling several builders' projects. Leads pour in from four portals for a dozen properties; capture-time dedupe and zone-based assignment keep one buyer with one agent and credit the right portal.
A builder running campaigns for a single launch needs every enquiry caught and acknowledged in seconds, because the cost-per-lead is high and a slow first response is a wasted ad rupee. Source tagging shows which channel the launch budget should favour.
Multiple branches drawing from the same portal accounts need assignment rules that route a lead to the right branch and agent — and dedupe that works across branches, so two offices don't both chase the same enquiry.
"We run a small channel-partner firm — six agents, and we advertise the same projects on 99acres, MagicBricks, Housing and NoBroker. The problem was never getting leads; it was that the same buyer would come in on two portals and two of my agents would call him the same morning. He'd think we were a mess, and he wasn't wrong. What I needed wasn't fancy scoring — that comes later — it was just to catch the duplicate the moment it arrived and give the lead one owner. Now an enquiry lands, the buyer gets a WhatsApp acknowledgement within a minute and a half, the system spots if he's already in our pipeline, and one agent owns him. The double-calls stopped. And at the end of the quarter I can finally see which portal actually sent me buyers instead of just bills. I keep the scoring and the drip stuff on the other module; this one just has to get the lead in cleanly, and it does."
What every channel partner and builder sales head asks before they change how leads come in.
We'll show you portal-to-CRM capture from MagicBricks, 99acres, Housing and NoBroker, capture-time dedupe, the consent-based WhatsApp acknowledgement, and rule-based assignment — in a demo on your firm's actual portals.
Book the Lead-Capture Demo →