WhatsApp CRM for Real Estate: India 2026 Pipeline Guide

Why real-estate agents lose half their leads on WhatsApp

You open WhatsApp Web on Monday morning. 60 portal leads landed over the weekend from MagicBricks, 99acres, and Housing.com. 12 site visits are booked for the week. 4 brokers are asking for follow-up status on properties you showed last fortnight. The chat list is sorted by recency, so the cold lead from three weeks ago who finally replied looks identical to the customer chasing a token receipt. Sound familiar?

I'm Rakshit Soni, co-founder of Lion CRM at LotsOfCode Private Limited, based out of Pali in Rajasthan. I've spent four years watching real-estate agents and small agencies in Pali, Jaipur, Hyderabad, and the NCR corridor try to run pipelines on WhatsApp without a CRM. The number I keep seeing: 40–60% of inbound leads die in the gap between "first reply" and "second follow-up". Not because the agent is lazy. Because the chat list is the wrong tool for the job.

This is the post I wish someone had handed me when I started building Lion CRM. What a WhatsApp CRM for real estate actually does. The five-stage pipeline that beats the generic Lead/Prospect/Customer default. How site-visit booking inside WhatsApp is the single highest-leverage automation an agent can wire up this week. Why the Chrome-extension path makes more sense than the WhatsApp Business API for individual brokers and small agencies. And a 15-minute setup so you can stop reading and start dragging cards.

Honest take up front: if you sell property in India and your pipeline lives in your head plus a WhatsApp chat list, you're already losing deals. Let's fix that.

Why WhatsApp owns Indian real-estate sales now

The transaction has migrated. Five years ago, MagicBricks would email you the lead. The agent would call. The buyer would say "WhatsApp me the photos." Today, MagicBricks, 99acres, Housing.com, and NoBroker push the lead straight to WhatsApp on the agent's number — name, budget, locality, contact opt-in, all in the first message. The buyer expects a reply within minutes, on WhatsApp, with photos and a Google Maps location. Every step of the conversation lives there: budget back-and-forth, site-visit time confirmation, broker handoff, token receipt screenshot, registry document. The phone call still happens, but it slots between WhatsApp messages, not the other way around.

This shift is real and recent. India added 800 million WhatsApp users between 2018 and 2025, and Indian real-estate buyers — most of whom are first-time home buyers between 28 and 45 — overwhelmingly prefer asynchronous chat over phone calls when researching property. Agents who picked up on this early outperformed peers by a wide margin. Agencies that didn't are now playing catch-up with hosted CRM dashboards that don't talk to the WhatsApp number where the actual conversations happen.

The honest question every agent should ask in 2026: if WhatsApp is the channel where 80% of your sales conversations live, what's your WhatsApp pipeline strategy? "Stars and archive" is not a strategy. "I'll remember to follow up" is not a strategy. "I'll copy-paste leads into a Google Sheet on Sunday" is the strategy that loses you 40% of your pipeline.

A WhatsApp CRM for real estate is not optional anymore. It's the bare minimum a serious agent or agency needs to keep up with how Indian buyers actually transact in 2026.

What a WhatsApp CRM for real estate actually does

A WhatsApp CRM for real estate is a tool that sits on top of (or alongside) WhatsApp and does six concrete things a chat list cannot. Let me walk through them in order of leverage.

First, lead capture. When MagicBricks or Facebook Lead Ads pushes a lead to your WhatsApp number, the CRM tags the contact with the source automatically. You don't have to remember whether "Priya, 3BHK, Dwarka, ₹1.2Cr" came from a portal or a referral or a cold WhatsApp message. The source determines the follow-up cadence, the script, and the priority — without source tagging, every lead looks the same.

Second, pipeline stages. The CRM gives you a visual board where every contact sits in a stage that maps to your sales motion — Inquiry, Site Visit, Offer, Token Paid, Closed Won. You can see at a glance how many cards are stuck in Site Visit waiting for a confirmation versus how many are sitting in Offer waiting for the buyer to come back with a counter. The chat list cannot show you this. The pipeline view is the difference between selling and chasing.

Third, site-visit booking and reminders. Once a buyer confirms a site visit, the CRM holds the slot, sends the buyer a day-before nudge ("Reminder: site visit tomorrow 11 am at Sector 49 Gurgaon — Google Maps link") and a day-of confirmation. No-show rates drop materially when you automate this — most agents lose 25–30% of booked visits to silent no-shows that a single reminder would catch.

Fourth, follow-up cadence per stage. A lead in Inquiry needs a reply within 4 hours. A buyer in Offer needs a follow-up in 48 hours. A customer in Token Paid needs a check-in 7 days later to confirm registry timelines. The CRM holds these cadence rules and surfaces the next action so you don't have to keep them in your head.

Fifth, broker handoff and team visibility. When you hand a lead to a colleague for the actual site visit, the CRM should pass the chat history, budget notes, and prior site-visit feedback. Without it, the colleague walks in cold and the buyer feels handed off. The CRM also lets the team-mate see the same pipeline view you see, so the agency owner can spot leaks across multiple agents.

Sixth, document sharing and post-token follow-through. Token receipts, agreement drafts, registry papers — every property sale generates a paper trail that lives partly on WhatsApp and partly in email. The CRM keeps the WhatsApp side of that organised so you can find the receipt 6 months later when the buyer comes back for a second property.

What it is NOT: a replacement for the WhatsApp chat itself. The conversation still happens in WhatsApp. The CRM is the layer that adds memory, structure, and accountability to those conversations.

The five-stage real-estate pipeline that actually works

Most CRMs ship with a generic four-stage default — Lead, Prospect, Customer, VIP — and most real-estate agents try to make it fit. It doesn't. The property sales motion has a hard milestone the generic default obscures: the site visit. Until a buyer physically stands on the property, no real-estate deal moves forward. After the site visit, the conversation either accelerates rapidly toward an offer or dies. The site visit is the single most predictive event in a property pipeline, and any CRM that doesn't make it its own stage is missing the most important signal you have.

The five-stage default I recommend for almost every real-estate agent and small agency in India: Inquiry → Site Visit → Offer → Token Paid → Closed Won. Let me walk through what each stage means in chat-behaviour terms, with entry and exit conditions, because stages without exit conditions are where pipelines die.

Inquiry — they replied at least once. They came in from a portal, an ad, a referral, or a cold message and they engaged. They asked about a specific property, a budget range, or a locality. The action you owe them: a reply within 4 hours with photos, location, and one qualifying question (typically budget confirmation or move-in timeline). If an Inquiry doesn't move to Site Visit within 7 days, it goes to a "Re-nurture" parallel column for a follow-up touch in 30 days. If it doesn't move in 21 days, archive.

Site Visit — the buyer has agreed to physically visit the property. This is the most important stage because it's where pipelines either accelerate or die. Entry condition: a confirmed date and time and a shared Google Maps location. Exit condition: the visit happens and you have a verbal sentiment from the buyer ("liked it / want to see more options / not what we expected"). The action you owe them between booking and visit: a day-before reminder and a day-of confirmation. Without these two nudges, expect 25–30% no-shows. With them, no-shows drop to under 10%.

Offer — the buyer has signalled buying intent post-visit. They asked about price negotiation, asked about payment plans, asked about possession timelines, asked for the legal documents. The action you owe them: a clear next step within 48 hours — written offer, second visit with the spouse, or a meeting with the builder. Offer is the stage where most real-estate pipelines leak because the agent waits for the buyer to push and the buyer waits for the agent to push. The pipeline view makes the leak visible — when 8 cards have been sitting in Offer for 7+ days, you have a leak.

Token Paid — the buyer has paid the booking amount, typically ₹50,000 to ₹2,00,000 depending on property class. The action you owe them: agreement draft within 7 days, registry timeline communication, and a 14-day check-in to confirm everything is on track. The biggest mistake here is treating Token Paid as a quiet stage where you can stop touching the buyer. They are anxious about a large payment and need confirmation that you're on top of the process.

Closed Won — the registry is complete, the keys are handed over, the deal is closed. The action you owe them: a 30-day post-handover check-in, a referral ask at 60 days when they're settled and happy, and a re-engagement touch at 18 months for resale or upgrade conversations. Real estate has the longest customer-revisit cycle of any retail vertical — a happy buyer in 2026 is a referral source for 2027 and a resale lead for 2032. Closed Won is not terminal; it's a long-cycle re-entry stage.

Run this five-stage default for one full week before you start adding columns. Most agents who try to add a sixth or seventh stage on day one end up over-engineering and abandoning the board within a fortnight. Five stages is enough to make every important decision visible. More stages mostly add noise.

Site-visit booking inside WhatsApp — the leverage point

Of all the things a WhatsApp CRM for real estate can do, site-visit booking automation has the highest ROI. It costs about 30 minutes to set up. It pays back the investment within the first week. It quietly removes the single biggest hole in your pipeline.

Here's the math. A typical real-estate agent in a Tier-1 Indian city books 25–40 site visits a month across their active leads. Without reminders, no-show rates run 25–30% — that's 7 to 12 visits a month where the buyer doesn't turn up, the agent travels for nothing, and the lead silently goes cold because no-show is a polite signal that the buyer isn't seriously interested. With a single day-before reminder and a single day-of confirmation, no-show rates drop to under 10%. The math on recovered visits alone — 4 to 8 additional realised visits per agent per month — adds up to 1 or 2 extra closed deals over a quarter.

The setup is straightforward inside Lion CRM. When a card moves from Inquiry to Site Visit, the Smart Calendar feature triggers two events automatically: a day-before reminder at 7 pm ("Reminder: site visit tomorrow at 11 am — [property name] — [Google Maps link] — reply YES to confirm") and a day-of confirmation at 9 am ("Hi [name], confirming we're meeting at [property] at [time] today — see you there"). Both messages send from your WhatsApp number, in your tone, with your branding. They feel personal because they are personal — the agent is the sender; the CRM is just the trigger.

The second piece is broker handoff. When you can't take the visit yourself and a colleague has to step in, the WhatsApp CRM should pass the chat history, the budget context, the buyer's specific concerns ("they asked twice about car parking"), and the prior visit feedback if there was one. Without this handoff, the colleague walks in cold and the buyer feels handed off — that's when you lose the deal. Lion CRM handles this by letting you assign a card to a team-mate; the team-mate sees the entire context, not just the contact name.

The third piece is post-visit feedback capture. Within an hour of the site visit, you should have a status update on the card: "loved it / wants to see two more / out of budget / not what they pictured". This single data point determines what happens next — Offer stage, second-visit booking, or Re-nurture. Most agents skip this step because it's tedious. The fix: a Quick Reply template in Lion CRM that takes one tap to send the buyer a "How did the visit go?" message and one tap to log the response on the card.

Wire up just these three things — day-before reminder, broker handoff, post-visit feedback — and you'll see the impact on your pipeline within a fortnight. The rest of the CRM features compound on top of this foundation, but this is the first thing to set up.

Auto-capture portal leads without the WhatsApp Business API

The single biggest source of leakage in a real-estate WhatsApp pipeline isn't follow-up — it's the portal lead that never gets entered into a pipeline at all. Here's the typical pattern: a lead lands from MagicBricks, the agent replies once on WhatsApp, the conversation continues for two days, the agent gets distracted by another deal, the lead falls out of the chat list's "recent" view, and three weeks later when the agent finally remembers to follow up, the buyer has already signed elsewhere. That lead never made it onto a pipeline board because there was no automatic capture step.

The hosted CRM dashboard built on the WhatsApp Business API solves this with portal integrations and template-broadcast drips. It works, but the cost is real: 1–3 weeks of Meta verification and template approval, ₹0.08 to ₹1.40 per WhatsApp conversation in India depending on category, and a separate dashboard at app.theirsaas.com you have to log into instead of staying in WhatsApp Web. For an individual broker or a small agency, that overhead kills the project before it ships.

The Chrome-extension path skips all of that. When MagicBricks pushes a portal lead to your WhatsApp number, the lead lands as a new chat in your WhatsApp Web inbox. The Lion CRM extension, sitting on top of WhatsApp Web, sees the new chat appear and creates a card in the Inquiry stage automatically. You can configure the extension to tag the card with "MagicBricks" as the source, set a 4-hour follow-up reminder via Smart Calendar, and pull in any structured data the portal sent (budget range, locality, property ID) into custom fields on the card. All of this happens inside your existing WhatsApp Web tab. No Meta API, no BSP, no Zapier subscription, no separate dashboard.

The same pattern works for Facebook Lead Ads. Run a Facebook lead campaign for "3BHK in Sector 49 Gurgaon", route the lead-form opt-in to a WhatsApp click-to-chat link with a UTM parameter, and the lead lands in WhatsApp Web. The Lion CRM extension auto-tags Facebook-sourced leads differently from portal-sourced leads (because the conversion intent is different — Facebook leads are early-funnel research, portal leads are mid-funnel "I want to visit"). You then run different Smart Calendar cadences against each tag without leaving WhatsApp.

Where this Chrome-extension path falls short is bulk template-broadcast — you can't push a "10 new properties launched in your locality" template message to 5,000 contacts at once outside the 24-hour window the way the API path can. For mass-marketing-broadcast use cases, the API is the right tool. For inbound lead capture and one-to-one nurture, which is where 90% of an SMB real-estate pipeline lives, the Chrome extension does the job at zero per-message cost. The full architecture comparison — when to pick which — is in WhatsApp CRM vs WhatsApp Business API: which to pick (2026).

Lion CRM Chrome-extension architecture for real estate

Lion CRM is a Chrome extension that runs on top of WhatsApp Web. That sentence is doing a lot of work, so let me unpack what it means specifically for a real-estate agent.

You install the extension from the Chrome Web Store. You open WhatsApp Web at web.whatsapp.com and scan the QR code with your phone the way you always have. The extension hooks into the same session — your number, your messages, your contacts. There's no separate Lion CRM login, no separate cloud database, no second dashboard to keep in sync. The Kanban board appears as a panel inside your WhatsApp Web tab. You drag a card from Inquiry to Site Visit. The card carries the contact, the chat history, the tags, the custom fields, and the Smart Calendar reminders with it. The card you see on the board is the same chat that lives in WhatsApp Web's chat list — there's no copy, no sync, no reconciliation.

What this architecture means for a real-estate team:

• 100% local data. Every card on your pipeline, every contact tag, every site-visit note, every custom field is stored on your own device. There's no cloud database with your buyer list, your budget data, or your token-paid amounts sitting on a third-party server. If you uninstall the extension, your data stays on your laptop. For an agent dealing with high-net-worth buyer information, this matters.
• Zero per-message cost. You're sending from your own WhatsApp number, exactly the way you would without any extension. There are no per-message fees because there is no Meta API metering. A pipeline with 1,000 active leads costs the same as one with 10. No surprise ₹15,000 monthly bill at the end of a busy month.
• No Meta verification needed. No business verification, no template review, no BSP onboarding. You install the extension and you're operational in under 15 minutes. Compare to the 1–3 weeks the API path takes to go live.
• One-tab workflow. The Kanban board, Custom Tabs, Smart Calendar, and message templates all sit inside the WhatsApp Web tab. You never context-switch into a separate dashboard. For an agent running 20 active conversations simultaneously, this is the difference between a tool you actually use and a tool you stop opening after week two.
• Custom Tabs filter the chat list. Filter by source ("MagicBricks leads only"), by stage ("Site Visit this week"), by property type ("3BHK Gurgaon"), or by any custom tag. The chat list itself becomes a slice of your pipeline.
• Smart Calendar holds the cadence. Day-before site-visit reminders, 48-hour Offer follow-ups, 14-day Token Paid check-ins — all automated and triggered by stage changes on the Kanban.
• 9 languages including Hindi. The extension UI works in Hindi, English, and 7 more languages. For Tier-2 city brokers and team-mates more comfortable in Hindi, this matters. Lion CRM is one of the few Chrome-extension CRMs that ships proper Hindi localisation rather than a Google-translate afterthought.

The trade-off is honest: this architecture is built for individual brokers, small-to-mid agencies (typically up to 25 brokers), franchise networks, and whitelabel resellers. If you're an enterprise builder running multi-agent contact centers across 20+ projects with hundreds of thousands of inbound conversations a month, the WhatsApp Business API path is what fits — and that's what enterprise platforms like Sell.Do exist for. The good news is the architecture choice is yours, and the vast majority of Indian real-estate agents and agencies fall into the SMB bucket where the Chrome-extension path is the right tool.

Whitelabel WhatsApp CRM for real-estate agencies and franchisors

There's a second audience for this conversation that doesn't get enough airtime: the real-estate agency owner with 10 to 50 brokers under their network, or the franchise operator running multiple branch offices. For these owners, the question isn't "which WhatsApp CRM should I use?" — it's "which WhatsApp CRM can I rebrand and resell to my network as my own?"

That's the whitelabel reseller model, and Lion CRM is built for it from the ground up. As a whitelabel partner, you take the Lion CRM Chrome extension, replace the branding with your own (logo, colours, name), set your own pricing tier per broker, and resell licences to your network. The brokers see "ABC Realty CRM" instead of "Lion CRM". You own the pipeline-view dashboard across your entire broker network. You see which broker is leaking deals at the Site Visit stage and which is closing fastest. You handle the licence sales and the broker support. The Lion CRM team handles the engineering, the WhatsApp Web compatibility, and the feature roadmap.

The whitelabel pricing is deliberately simple and SMB-affordable: Starter ($150 one-time + $2.50/user/month), Growth ($200 one-time + $2.00/user/month, the most popular tier for 10–30 broker agencies), Enterprise ($250 one-time + $1.00/user/month for franchises with 30+ active brokers). There's a 30-active-user-after-3-months minimum once your grace period ends. The Webstore Setup add-on ($250 one-time) configures a public marketing site under your brand if you want one. Whitelabel signup is at admin.lioncrm.com/public/login.php.

For a real-estate franchise operator, the maths is straightforward. If you run 30 brokers and resell at ₹999/month per broker, that's ₹3.6 lakh a year in recurring revenue from your existing network with near-zero engineering overhead on your side. You position the CRM as "your network's competitive advantage" instead of "another SaaS tool brokers have to log into". The brokers pay because the pipeline tooling helps them close more deals — and you take a margin on every licence.

The full whitelabel breakdown — including the difference between just-resell vs full-rebrand vs marketing-site setup — is in Whitelabel WhatsApp CRM Software: founder's 2026 guide. If you're an agency owner reading this and you've been wondering whether to build your own CRM or buy one, whitelabel is the third path most owners don't realise exists.

Pitfalls that kill real-estate WhatsApp pipelines

After watching hundreds of real-estate agents and agency owners set up their first WhatsApp pipelines, the same five mistakes show up over and over. None of them are fatal — they're just the difference between a pipeline that runs your agency and a pipeline you stop checking after a fortnight.

Leaking site-visit no-shows. The agent books the visit, doesn't send a day-before reminder, the buyer forgets, no-show happens, the agent travels for nothing. Repeat 8 times in a month. The fix is the single most important automation in this whole post: day-before reminder + day-of confirmation. Set it once, never think about it again.

Stale leads at Inquiry without an exit rule. A card sits in Inquiry for 21 days because the agent forgot. The buyer has long signed elsewhere. The card sits there permanently, inflating your top-of-funnel count and making your pipeline metrics dishonest. The fix: a 7-day rule. If a card hasn't moved in 7 days, it gets a force-decision — Re-nurture (parallel column, follow up in 30 days), or archive. The board exists to surface this decision; you have to actually make it weekly.

Ghost numbers from portal scrapers. Some MagicBricks-style portal subscription tiers send you raw lead exports that include numbers that never actually opted in. You message them, they don't reply (because they're not real prospects), and the cards sit in Inquiry forever. The fix is upstream: use the Bulk Number Validator to filter dead numbers before you import them into the board. The safe-send playbook for portal lead bulk handling is the same playbook for protecting your number from getting banned — read it before you import any list above 50 contacts.

No broker-handoff process. The agent assigns a site visit to a colleague but doesn't pass the chat history, the budget context, or the buyer's specific concerns. The colleague walks in cold. The buyer feels handed off. Deal lost. The fix: a one-line handoff note on every assigned card, plus the colleague reading the last 20 messages on the chat before the visit. Lion CRM's contact-card-with-history view makes this take 60 seconds, but it requires the discipline of actually doing it.

Treating Closed Won as terminal. Every property sale in India has a 18-to-24-month resale window and a same-day referral window. A buyer who just took possession is the warmest possible source for "do you know anyone else looking?". A buyer 18 months in is your highest-intent lead for upgrade or investment property. Cards in Closed Won should get a 30-day post-handover check-in, a 60-day referral ask, and a 18-month re-engagement touch. Most agents archive Closed Won cards on day one and lose 30% of their referral pipeline.

Bonus pitfall: over-stage-ing. Someone reads about pipeline best practices, gets excited, creates 9 stages on day one, gets paralysed, abandons the board within a week. Start with five. Add a sixth only when the existing five stop carrying enough information. More than six and you're managing the board, not the buyers.

Chrome-extension vs WhatsApp Business API for real-estate teams

The honest comparison for real-estate teams specifically. I'm not going to pretend one path is universally right.

Time to live. Chrome extension: 15 minutes (install, scan QR, customise five stages, drag your first 20 leads). WhatsApp Business API + hosted CRM: 1–3 weeks (Meta business verification, BSP onboarding, template message review, dashboard configuration, broker training on the new dashboard). If you need a pipeline this week because your agency is bleeding leads, only one of these gets you there.

Cost. Chrome extension: flat licence fee — Lion CRM is $100/year direct for one number on up to 4 devices, $150–$250 one-time + $1–$2.50/user/month whitelabel. API path: per-message metered billing on top of the hosted CRM subscription. For a typical real-estate agent sending 2,000 conversations a month in India, the WhatsApp metering alone runs ₹2,000–₹6,000/month, before the dashboard subscription on top. Chrome extension scales linearly with users; API scales linearly with messages.

Where your data lives. Chrome extension: on your device. API + hosted CRM: on the BSP's cloud or the SaaS vendor's database. Neither is universally better — local data is a privacy and ownership win but a backup risk; cloud data is a backup win but means your buyer list and budget data sit on someone else's server. For most independent agents, local data wins. For multi-agent enterprises with regulatory or audit requirements, cloud data wins.

Scale ceiling. Chrome extension: comfortably handles individual brokers and agencies up to about 25 active brokers, on a small number of WhatsApp numbers, with disciplined pipeline hygiene. WhatsApp Business API + hosted CRM: needed once you're running multi-agent contact centers, ≥50 simultaneous agents, hundreds of thousands of inbound messages a month, or template-broadcast marketing outside the 24-hour window. There's a real ceiling on the extension path — the question is whether your business will hit it. Most won't.

Ban risk and account safety. This question comes up every time. The honest answer: any tool can get a number banned if it's used to mass-message strangers, and any tool keeps a number safer if it's used to nurture opted-in contacts at human pace. WhatsApp's own anti-spam policy is clear that mass messaging unknown contacts is what triggers bans, not the existence of any particular extension. Lion CRM ships with built-in safety features — pause settings, human-like delays, the Bulk Number Validator — specifically to keep extension users on the right side of WhatsApp's quality detection. Use them. Send to opted-in real-estate buyers at human cadence and your number is materially safer than it would be without the safety nets. Send 5,000 cold messages to portal-scraped contacts in 90 seconds and any tool — extension or API — will get you in trouble.

For most independent brokers, small agencies, franchise operators, and whitelabel resellers in Indian real estate, the Chrome-extension path is the right starting point. It's how almost every Lion CRM real-estate user starts, and it's how most stay because the API path's overhead is overkill for their volume. If you're not sure which side you're on, start with the extension. You can always graduate to the API path later. You can't undo three weeks of Meta verification you didn't need.

Step-by-step: build your real-estate WhatsApp pipeline in 15 minutes

This is the actual setup I'd walk a new real-estate agent through over a screen-share. No magic. 15 minutes start to finish.

1. Install the Lion CRM Chrome extension from the Chrome Web Store. Pin the icon to your Chrome toolbar so the panel is one click away.
2. Open WhatsApp Web at web.whatsapp.com and scan the QR code with your phone the way you normally would. The extension hooks into the same session — your number, your messages, no separate login.
3. Open the Kanban panel from the extension toolbar inside WhatsApp Web. The default four stages — Lead, Prospect, Customer, VIP — are pre-configured.
4. Customise to the five real-estate stages: rename the columns to Inquiry → Site Visit → Offer → Token Paid → Closed Won. Add a parallel "Re-nurture" column for cold leads worth a 30-day follow-up. This takes about 2 minutes.
5. Drag your last 30 active conversations into stages. Pick the most active chats from the past two weeks and drop them where they actually are. Don't try to sort everyone on day one. This snapshot alone is the moment you realise how leaky your current pipeline is.
6. Set Smart Calendar cadence per stage. Inquiry = 4-hour reply reminder + 7-day exit rule. Site Visit = day-before reminder at 7 pm + day-of confirmation at 9 am. Offer = 48-hour follow-up reminder. Token Paid = 14-day check-in. Closed Won = 30-day post-handover check-in + 60-day referral ask + 18-month re-engagement touch.
7. Wire one Powerful WebHook to a shared Google Sheet so your team-mates can see the same pipeline summary. Stage changes push to the sheet, the sheet shows which agent has which lead at which stage. This is what unlocks team visibility without buying a separate dashboard.
8. Run the board for one full week before customising further. This is the rule almost everyone breaks. Resist the urge to add stages or rename things on day three. Most of the "missing stage" feelings on day three turn out to be unnecessary by day seven.

By the end of week one you'll know two things: which stage is leaking the most cards (that's where your sales energy goes next), and which integrations you actually want (you'll feel the absence of an automation before you wire it up). The order matters: pipeline first, automations second, integrations third.

If you're an agency owner setting this up across 10+ brokers, the Whitelabel WhatsApp CRM Software guide covers the rebrand-and-resell path so you can roll out the same pipeline tooling across your network with your branding instead of Lion CRM's.

Lion CRM at a glance — 16 features for real-estate teams

The Kanban Board is one of 16 features inside Lion CRM. The other 15 exist because pipeline management isn't useful in isolation — you also need to talk to those leads efficiently, capture the right context, and keep your number safe. Here's the canonical list, with a real-estate lens on which feature does what for an agent.

Bulk Messaging (portal-lead drip campaigns), Custom Tabs (filter chat list by property type / locality / source), Message Templates (saved scripts for Inquiry / Site Visit / Token Paid replies), Quick Reply (one-tap responses to common buyer questions), Kanban Board (the five-stage real-estate pipeline), Smart Calendar (site-visit reminders + Offer follow-up cadence), Profile Chat (custom fields per contact — budget, locality, BHK preference), Chat Toolbar (in-chat shortcuts), Bulk Number Validator (filter ghost numbers from portal exports), WhatsApp Status Automation (daily new-listings status broadcasts), AI Integration (auto-classify inbound buyer intent with your own OpenAI / Gemini / DeepSeek key), 9 Languages (Hindi UI for Tier-2 brokers), Backup & Restore (laptop-loss safety net), Powerful WebHooks (sync to Google Sheets / Zapier / HubSpot for team visibility), Configure API (custom integrations), and Custom Signature (auto-append your contact + RERA number to outbound replies).

The extension UI ships in 9 languages — English, Hindi, Portuguese, Spanish, German, French, Italian, Dutch, with more being added. For a Tier-2 city brokerage in Indore or Lucknow with team-mates more comfortable in Hindi, the localised UI removes a real adoption barrier.

Pricing is deliberately simple. Direct end-user: $100/year for one WhatsApp number on up to 4 devices. Whitelabel partner: Starter $150 one-time + $2.50/user/month, Growth $200 one-time + $2.00/user/month (most popular for 10–30 broker agencies), Enterprise $250 one-time + $1.00/user/month, with a 30-active-user-after-3-months minimum after the grace period. Webstore Setup add-on $250 one-time. The whitelabel admin lives at admin.lioncrm.com/public/login.php.

For comparison shopping against the rest of the Chrome-extension category, Best WhatsApp CRM Extensions for Chrome walks through how Lion CRM stacks up. For the head-to-head against the closest direct competitor, see Lion CRM vs Watidy.

Frequently asked questions

Can I use WhatsApp Business for real estate?

Yes, but the WhatsApp Business app alone is not enough for a serious real-estate pipeline. The Business app gives you a business profile, quick replies, and labels — useful for solo brokers handling under 30 chats a week. Beyond that, you need pipeline stages, site-visit reminders, broker handoff, and team visibility. That's where a WhatsApp CRM for real estate — a Chrome extension on top of WhatsApp Web (Lion CRM) or a hosted dashboard built on the WhatsApp Business API (BSP-class platforms like Sell.Do or AiSensy) — becomes necessary. For most individual brokers and small agencies, the Chrome-extension path is faster, cheaper, and easier to roll out.

Which CRM works best with WhatsApp for real estate?

It depends on your size. For individual brokers and agencies up to about 25 brokers, a Chrome-extension CRM that runs on top of WhatsApp Web — Lion CRM is the one I built and the one I'd recommend, for obvious reasons — gives you a 15-minute setup, zero per-message cost, and local data. For enterprise builders with multi-agent contact centers across 20+ projects and hundreds of thousands of monthly inbound messages, a hosted CRM built on the WhatsApp Business API (Sell.Do is the established Indian incumbent) is the right tool. The honest test: if you can name every broker on your team by face and you process under 5,000 buyer conversations a month, the Chrome-extension path fits you. If you can't, the API path fits you.

How do I manage real estate leads on WhatsApp?

Three pieces. First, capture every lead into a pipeline view automatically — manual copy-paste from MagicBricks or 99acres into a Google Sheet is where most leakage starts. Second, run a five-stage pipeline (Inquiry → Site Visit → Offer → Token Paid → Closed Won) so every lead has a clear current state and a clear next action. Third, automate the high-leverage cadences: 4-hour reply on Inquiry, day-before reminder on Site Visit, 48-hour follow-up on Offer. A WhatsApp CRM for real estate (Lion CRM is one option) gives you the pipeline view, the automations, and the team visibility in one tool. Without it, you're managing leads in your head — which works at 10 active conversations and breaks at 50.

Does a WhatsApp CRM for real estate work without WhatsApp Business API?

Yes, completely. Lion CRM is a Chrome extension that runs on top of WhatsApp Web — it does not use the WhatsApp Business API or have any partnership with Meta. Your messages flow through your own WhatsApp Web session, the same way they would without any extension. The pipeline view, Kanban board, Smart Calendar reminders, and lead-source tagging all live inside the extension on your device. The trade-off: you can't send template-broadcast messages outside the 24-hour window the way the API allows, but for inbound lead capture, one-to-one nurture, and pipeline management — which is where 90% of an SMB real-estate workflow lives — the no-API path does the job.

How do I auto-capture MagicBricks / 99acres leads in WhatsApp?

When MagicBricks or 99acres pushes a portal lead to your WhatsApp number, the lead lands as a new chat in your WhatsApp Web inbox. The Lion CRM Chrome extension, sitting on top of WhatsApp Web, sees the new chat appear and creates a card in the Inquiry stage automatically. Configure the source-tagging rule once (e.g., "if first message contains MagicBricks lead format, tag as MagicBricks"), and every future portal lead gets tagged automatically. From there, the Smart Calendar fires the 4-hour Inquiry follow-up reminder. No Zapier subscription, no API wrangling, no separate dashboard. The same pattern works for Facebook Lead Ads — route the form to a WhatsApp click-to-chat link and the extension picks up the lead.

Can my whole real-estate team see the same WhatsApp pipeline?

In Lion CRM, the Kanban data is stored locally on each agent's device by default — that's the privacy and zero-cost trade-off of the Chrome-extension architecture. To share pipeline visibility across a team, you have two options: (1) use the Backup & Restore feature to export and import the same Kanban configuration across team-mate devices, or (2) wire stage-change events to a shared Google Sheet via Powerful WebHooks so every team member sees the same pipeline summary in one place — most agencies find this gives the agency owner sufficient visibility without sacrificing the per-agent data privacy. For full concurrent multi-agent editing of the same board across devices in real time, the WhatsApp Business API + hosted CRM path is a better architectural fit.

Related guides

• Lion CRM — The Ultimate WhatsApp CRM Chrome Extension (Complete Guide) — the canonical pillar guide for the product, with screenshots of every feature including the Kanban Board.
• WhatsApp Kanban Board: 2026 Sales Pipeline Guide — yesterday’s deep-dive on the Kanban methodology and the four-stage default this real-estate guide builds on.
• WhatsApp CRM vs WhatsApp Business API: Which to Pick (2026) — full architecture comparison between the Chrome-extension path and the BSP/API path.
• Whitelabel WhatsApp CRM Software: Founder’s 2026 Guide — for agency owners and franchisors who want to rebrand and resell the CRM to their broker network.
• Best WhatsApp CRM Extensions for Chrome — Which One Can You Rebrand & Sell? — comparison of the top Chrome-extension CRMs.
• Lion CRM vs Watidy — head-to-head against the closest direct competitor.
• How to Send Bulk WhatsApp Messages Without Getting Banned — required reading before you import any portal-lead list above 50 contacts.
• How to Schedule WhatsApp Messages — No Per-Message Cost — for the drip-campaign cadence on portal-sourced leads.

The honest verdict on WhatsApp CRM for real estate

If you sell property in India in 2026 and your pipeline lives in your WhatsApp chat list plus a memory of which buyer wanted which BHK, you're losing 40 to 60 percent of your leads to follow-up gaps. That's not a guess — it's the number I've watched play out across hundreds of real-estate agents over four years of building WhatsApp tooling. The chat list is for talking. A pipeline view is for selling. They're not the same tool.

The choice between the Chrome-extension Kanban path (Lion CRM) and the WhatsApp Business API + hosted CRM path (Sell.Do, AiSensy, and the rest of the BSP-class platforms) is real and worth thinking through. For individual brokers, small agencies, franchise networks, and whitelabel resellers — which is the vast majority of the Indian real-estate market — the extension path is the right starting point. 15 minutes to live versus 1–3 weeks for Meta verification. Zero per-message cost versus ₹0.08–₹1.40 per WhatsApp conversation. Local data on your laptop versus a BSP cloud you don't own. For enterprise builders running multi-agent contact centers across 20+ projects, the API path is what fits — and that's a legitimate, valuable choice for that specific scale.

If you're going to try the Chrome-extension path, Lion CRM's free 7-day trial is the lowest-risk way in. Install from the Chrome Web Store, open WhatsApp Web the way you already do, customise the five-stage real-estate pipeline, drag last week's 30 active leads into stages, set the Smart Calendar reminders for site visits, and run it for a week. If after a week you don't think it's better than your old chat-list workflow, walk away — no contract, no per-message cost, no API approval to undo. That's the entire pitch. The LotsOfCode YouTube channel has the walkthrough videos if you'd rather watch the setup before you commit.

Whatever path you pick, get a pipeline view in place this week. Lion CRM, a product by LotsOfCode Private Limited based in Pali, exists because too many Indian real-estate agents lose too much pipeline to a chat list that wasn't built for selling property. Don't let yours be one of them.

Try Lion CRM free for 7 days

Want to test before you commit? Install Lion CRM directly from the Chrome Web Store — every first-time install gets an automatic 7-day free trial.

Steps:

1. Click the install link → Get Lion CRM on Chrome Web Store.
2. Click "Add to Chrome" — the extension installs in seconds.
3. Open WhatsApp Web in your browser — Lion CRM activates automatically.
4. Your 7-day trial starts the moment you log in. No credit card needed.
5. Customise the default Kanban into the five-stage real-estate pipeline (Inquiry → Site Visit → Offer → Token Paid → Closed Won) and start dragging cards.

Written by Rakshit Soni, co-founder of LotsOfCode Private Limited and creator of Lion CRM, based in Pali, Rajasthan. Kuldeep Dadhich, co-founder, leads engineering on the extension. Both are reachable through the WhatsApp number on the lioncrm.site contact page if you want to discuss your specific real-estate pipeline before signing up.