A ₹1.8Cr enquiry for a 3BHK in Whitefield came in on 99acres at 8:42 PM on a Saturday. The buyer filled the same form on Housing eleven minutes later, and on MagicBricks before bed. By Monday morning, two of your reps had called — one from the 99acres lead, one from the Housing lead — both leaving the same voicemail. The buyer had already booked a site visit on Sunday with the developer who texted back within the hour. That deal is gone, and you paid three portal subscriptions to lose it.
This is what real estate enquiry management in India actually looks like once volume crosses a few hundred enquiries a month. Not a CRM problem. A routing-and-speed problem dressed up as one.
TL;DR
- Enquiries scatter across 6+ sources — 99acres, Housing, MagicBricks, the site form, Facebook lead ads, WhatsApp walk-ins — each in its own inbox nobody owns end to end.
- The same buyer enquires on three portals in one hour; without dedup, three reps chase one person and your pipeline count lies.
- First response decides the site visit. Grade A buyers convert within ~47 minutes; the developer who calls first usually books the visit.
- No source attribution means you can't tell whether 99acres or Housing earned its subscription — so you renew on guesswork.
- A unified, scored, queued inbox — every channel in one feed, graded A–F, ranked by ₹ at risk — fixes the leak without ripping out your CRM.
The enquiry doesn't get lost. It gets scattered.
Walk into most developer sales offices and the "lead system" is a stack of logins. One tab for the 99acres dashboard. One for the Housing portal. One for MagicBricks. A shared Gmail for the website form. A WhatsApp Business number a junior checks "when free." Maybe a Facebook lead-ad export someone downloads on Fridays.
Each of those is a real source of ₹40L–₹3Cr enquiries. None of them talk to each other. So the question "what came in today, and which ones are worth calling now?" has no answer. Somebody has to open six tabs and eyeball them. Nobody does that at 9 PM on a Saturday, which is exactly when serious buyers — people with day jobs — sit down to browse property.
The enquiry isn't lost because a rep ignored it. It's lost because no single screen ever showed it next to everything else, ranked by what it's worth.
Duplicate enquiries quietly wreck your numbers
Portal buyers don't enquire once. They shortlist four projects and fire the form on all four, often across all three portals in the same sitting. From the buyer's side that's normal. From your side it creates a mess.
Without deduplication, the same person becomes three "leads." Three reps see three records. Two of them call the buyer — who now feels hunted by your brand before a single site visit. Your manager opens the weekly report and sees 340 enquiries when the real number of human beings was closer to 220. Conversion rate looks worse than it is. Cost-per-lead looks better than it is. Every decision you make off that report is slightly wrong.
A unified inbox merges the three into one record and keeps all three source tags attached. One rep owns the buyer. The pipeline count reflects reality. And when renewal season comes, you can see that 99acres sent the original and Housing sent the duplicate — which matters for the next point.
You're renewing portal subscriptions on a hunch
99acres, Housing and MagicBricks each cost real money — often ₹50,000 to several lakhs a year per project, depending on the package. The only honest way to decide which to renew is to know which one sourced enquiries that actually booked.
Most teams can't answer that. The moment an enquiry leaves the portal dashboard and gets typed into a CRM or a spreadsheet, the source label gets dropped, fat-fingered, or overwritten. So you renew all three because cancelling feels risky, and you keep paying for the portal that sends you tyre-kickers in ₹15L bands when your inventory starts at ₹60L.
Source attribution that survives all the way to "booked / lost" turns renewal from a hunch into a number. Maybe MagicBricks sources 40% of your enquiries but 8% of your bookings. That's a ₹-per-booking you can compare across portals — and a renewal conversation you can win.
Speed is the whole game, and you're losing it by hours
A portal buyer who enquired on three listings is, right now, being called by three developers. The site visit goes to whoever gets there first with a real human voice and a relevant project. This is not a personality contest. It's a clock.
Grade A enquiries — budget that fits your inventory, location intent that matches your project, a buyer ready to visit — convert when someone reaches them within roughly 47 minutes. After that the curve falls off a cliff. If your enquiries sit in six separate inboxes until a rep happens to check, your average first response is measured in hours, not minutes, and the hot ones cool while the junk gets called first because it happened to be at the top of one tab.
The leak here is pure rupees. Every Grade A enquiry that waits four hours instead of forty minutes is a ₹40L–₹3Cr opportunity you've handed to a faster competitor. The portal didn't fail you. The subscription worked. The handoff after it failed.
What a unified, scored, queued inbox actually changes
The fix isn't a bigger CRM. It's a behaviour layer that sits in front of everything and answers one question for the rep: who do I call right now, and why?
Here's the shape of it.
One feed, every source. 99acres, Housing, MagicBricks, website form, Facebook lead ads, WhatsApp — all land in a single inbox. No tab-switching. No 9 PM blind spot.
Graded A–F in under 500ms. Each enquiry is scored the moment it arrives, on budget fit, location intent, and project match. A ₹1.8Cr-ready buyer for your live Whitefield project is Grade A. A ₹20L enquiry against ₹80L inventory is Grade D, and it stops eating your best reps' mornings.
A Priority Queue that re-ranks live. The top of the list is always the highest ₹-at-risk enquiry that hasn't been contacted yet. Reps don't decide who to call — the queue does, and it's right, because it's ranked by money and freshness, not by which tab loaded first.
Dedup built in. The same buyer across three portals collapses into one record with three source tags. One owner. Honest pipeline.
WhatsApp logging in 3 taps. When a rep messages a buyer on WhatsApp — the channel Indian property buyers actually reply on — logging it takes three taps, not a CRM form nobody fills. So the activity history is real, and the next person who touches the lead knows what was said.
The Missed Opportunity Engine, in rupees. Anything that slipped — a Grade A that aged past its window, a site visit nobody followed up — surfaces with the ₹ at risk attached. Not "you have 12 overdue tasks." Instead: "₹2.4Cr in Grade A enquiries went un-contacted past 47 minutes this week." That's a number a sales head acts on before lunch. See exactly how that works in the Missed Opportunity Engine.
This is the difference between recording what happened and changing what happens. Your CRM stays where it is for contracts and reporting. The behaviour layer makes sure the ₹1.8Cr enquiry on a Saturday night gets called in 47 minutes, by the right rep, before the buyer books elsewhere.
Setup runs about 60 minutes — connect your portals, set your inventory bands, point your WhatsApp number, and the queue starts ranking. No three-month implementation. See it applied to property teams on the real estate use case, and once the inbox is unified, tighten the part most teams still get wrong with these real estate lead follow-up best practices for India.
Stop paying portals to warm up leads for the competition
Three subscriptions, six inboxes, and a buyer who books with whoever calls first — that's the current setup, and it leaks ₹ every weekend. The enquiries are fine. The portals are doing their job. What's missing is the one screen that pulls them together, scores them, and tells the rep which ₹40L–₹3Cr buyer to call in the next 47 minutes.
See your own enquiries unified, graded, and queued — book a demo and watch a Saturday-night ₹1.8Cr enquiry get to the right rep before the buyer's coffee goes cold.