Leads are perishable; run them like it
A portal lead is a person mid-search who messaged several listings and will remember whoever answered first and best. Between that moment and a site visit sits your lead operation, and for most agencies it is the leakiest part of the business. This guide is the operation, end to end.
Operator guide, written August 2026. Security practice varies with premises and state rules; treat this as method, and your society's bye-laws and local police guidance as the authority.
One queue or nothing
Leads arrive from 99acres, Magicbricks, Housing, walk-ins, referrals and the office number, and the failure mode is geography: each source living where it landed, portal dashboards, two phones, an inbox. The fix is a single queue: every lead, whatever the source, lands in one place with a source tag, an owner and a clock. How they land varies by account and portal, notification emails parsed, exports imported on a daily rhythm, or direct capture where available, and the mechanics matter less than the rule: if it is not in the queue, it does not exist. Agencies running one queue answer in minutes and measure everything; agencies running five surfaces answer eventually and measure nothing.
The first response, and the cadence after
The first response decides most outcomes, so design it: an on-duty responder during business hours, a same-hour standard, and a first message that moves the conversation, confirming the requirement, offering two visit slots, not 'yes it is available'. After that, cadence beats memory: day-one follow-up, day-three, day-seven, then a longer tail, each with an owner and a date, each ending in an outcome. A lead closed as 'visited, chose elsewhere, budget mismatch' is operational gold; a lead that just went quiet is a hole in your data and probably a deal someone else closed.
Step by step
-
1
Land every lead in one queue
Portals, calls, walk-ins — one place, source-tagged, deduped on phone number.
-
2
Assign an owner and start the clock
A duty responder and a same-hour standard; the first reply offers slots, not adjectives.
-
3
Run the cadence
Day 1, 3, 7, then the tail — dated follow-ups with owners, every lead closed to an outcome.
-
4
Schedule visits like appointments
Slots, reminders, outcomes recorded; a no-show is a follow-up, not an ending.
-
5
Review the funnel weekly
Per portal: leads, response time, visits, closures, cost per closure — and spend accordingly.
Handovers, absences and the queue that survives them
Lead operations break at the seams — the duty responder's day off, the colleague who quits, the festival week when nobody owned the queue. The one-queue design absorbs all three if two rules hold: every lead's history lives on the lead, not in a personal chat, and duty transfers by roster, not by memory. A handover then takes minutes — the incoming responder reads today's due follow-ups and continues in the same thread of record — and a resignation costs a login change instead of a book of contacts. The same structure is what lets a two-person agency take a holiday without the pipeline noticing, which is a better test of a lead system than any feature list: can the operation run for a week without its best person, and can anyone prove on Friday what happened to Monday's leads.
Site visits are the conversion event
Everything upstream exists to produce a visit, and visits leak twice: no-shows and unrecorded outcomes. Cut no-shows with confirmed slots and a reminder the evening before, WhatsApp does what calls did, cheaper. Record outcomes the same day: liked but budget, disliked layout, wants ground floor — because outcome patterns are your inventory strategy whispering. An agency that knows why the last forty visits did not close knows exactly which listings to hunt next; one that only counts visits knows it is busy.
How EstateDeck applies this
EstateDeck's CRM is this system: one deduped queue across portals, owners and response timers, cadences with dates, site-visit scheduling with reminders, and the per-portal funnel that decides next year's spend.
Go deeper: Lead CRM · Site visits
Written by Databus Technology Solutions, the makers of EstateDeck. These guides describe how housing societies and property operations run in practice; they are not legal advice. Cooperative and apartment law varies by state and changes on its own schedule, so verify specifics against your state's act and your society's bye-laws before acting.
Frequently asked questions
Are WhatsApp enquiries portal leads too?
Treat them as leads from the channel they arrived on — a WhatsApp message from a portal listing is that portal's lead, and belongs in the same queue with the same source tag, owner and clock. The mistake is letting WhatsApp threads live as their own parallel pipeline in someone's phone: the response happens fast, which feels like performance, but nothing is recorded, nothing is measured, and the thread leaves with the phone. Bridge the habit, not the tool — reply in WhatsApp, record in the queue.
How do we stop duplicate leads across portals?
Dedupe on phone number at entry: the same buyer enquiring on two portals becomes one lead with two source tags, and the response history travels with them. Without this, two colleagues call the same buyer with different prices, which buyers remember for the wrong reasons.
Should we reply to leads outside business hours?
An acknowledgement, yes; a negotiation, no. An automated or templated same-evening reply that confirms receipt and promises a morning call holds the buyer better than silence, and the morning call must then actually happen — the promise is now on the record. Late-night manual conversations burn responders out and train buyers to expect midnight service; the sustainable shape is fast acknowledgement always, substantive response within the published window, and the duty roster deciding who owns the morning queue.
Who should own portal leads in a small agency?
One named responder per duty window, not 'whoever is free' — shared ownership is unowned. Rotate the duty; keep the standard. Even a two-person agency runs this cleanly with a simple roster.
What should we log from every conversation?
Requirement, budget, localities, timeline, and the next action with a date. One structured minute per call. It is what makes handovers survivable and makes your matching improve, because tomorrow's new listing should surface yesterday's matching buyers automatically.
How long do we work a cold portal lead?
Through the cadence, then into a nurture list, not a bin: requirements resurface, budgets change, and the buyer who went quiet in March transacts in August, and the nurture message costs nothing but the list being alive. The monthly 'new matches' message to a nurture list is the highest-yield low-effort habit in the business.
Which portal deserves next year's budget?
The one your funnel says converts: leads to visits to closures to cost per closure, by portal, from your own records. Package salesmen carry impressive dashboards; your closure table outranks them all.
Related guides
Answer first; measure everything.
Applied on every payslip, files generated for upload — per employee, per month.
Start free