Home/ Case Studies/ Real-Estate CRM
Real Estate · CRM · WhatsApp

Real-Estate CRM with WhatsApp Automation — From Cold Leads to 4.2x Higher Site-Visit Conversion

A nine-property residential developer was buying leads from portals at Rs 800 a head and converting 0.8% to site visits. We built a CRM with WhatsApp Cloud API automation that lifted site-visit conversion to 3.4% — a 4.2x improvement on the same lead spend.

4.2xSite-Visit Conversion
28,000+Leads Managed
9Properties Onboarded
87%WhatsApp Open Rate

Project at a glance

Industry
Residential real estate · multi-project developer
Scope
CRM web app, sales-team mobile app, channel-partner app, WhatsApp automation
Team size
6 engineers + 1 PM + 1 RevOps consultant
Timeline
3 months to v1 · 5 months to full feature parity
Regions
Mumbai + Pune metropolitan; architecture portable to any city
Status
Live · two new property launches running on the platform

The client & the problem

The developer was running their pipeline on a mix of MagicBricks back-end, an ageing Salesforce instance two SDRs barely opened, and Excel. By the time a lead reached a sales person it was 18-36 hours cold. The pitch we made to them: speed-to-first-touch is the single biggest lever in real-estate, and WhatsApp + automation is how you get there.

  • Slow first response: Average time-to-first-call was 14 hours; competitors were under one.
  • Channel-partner blackbox: 200+ brokers brought leads but had no app or visibility — they were leaving for competitors with better tooling.
  • Sales-app dysfunction: Sales people kept notes on phones and lost half of them.
  • Re-engagement gap: After a missed call, a lead was effectively dead — there was no automated nurture.
  • WhatsApp risk: The team WhatsApp-pasted brochures from personal numbers; one number got banned, blowing up that quarter's pipeline.

The solution

Three apps + a WhatsApp automation engine. The non-obvious decision was building the channel-partner app first; brokers contributed 60% of leads and our competitors were not investing in them.

1. CRM web app (React)

Lead inbox with auto-assignment, multi-source ingestion (MagicBricks, 99acres, FB lead-form, web forms), pipeline stages, site-visit booking, document drawer, communication log (calls, WhatsApp, email), property-specific dashboards.

2. Sales-team mobile app (React Native)

Day-view of calls + visits, one-tap call (with auto-log), WhatsApp template send, geo-tagged site-visit attendance, voice-note capture, deal-stage update, commission view.

3. Channel-partner app (React Native)

Brokers add their own clients, get real-time updates on lead status, see their commission earned, and book site visits. This single feature made us non-trivial to switch away from.

4. WhatsApp automation engine

WhatsApp Cloud API integration. Templates for: instant lead acknowledgement, brochure send, virtual-tour link, site-visit reminder, post-visit thank-you, post-visit drip (5-message sequence over 14 days). Inbound replies route to sales app.

5. Backend (Laravel + Postgres)

Laravel 10, Postgres for relational data, Redis for queueing, BullMQ-style worker for WhatsApp throttling and template-rate-limit handling, S3 for documents, Twilio fallback for SMS.

Tech stack & why

We picked the stack for fit, performance under realistic load, and operational simplicity. Here is the breakdown:

Laravel 10 PHP 8.2 PostgreSQL Redis React 18 React Native WhatsApp Cloud API Twilio Razorpay AWS S3 GitHub Actions Sentry Datadog

WhatsApp Cloud API, not vendor wrapper: we integrated directly to Meta's Cloud API instead of using a Wati / AiSensy reseller. Saves Rs 25-40 per 1,000 messages at scale and eliminates the third-party-outage risk that hit us once on a competing build.

Laravel for the CRM API: the team's strongest stack, ecosystem (Eloquent, Sanctum, Horizon) covered 80% of what we needed. Performance was a non-issue at 28,000 leads — would re-evaluate at 1M.

React Native for two apps: sales and channel-partner apps share 60% of code. Half the build budget of two native iOS + Android codebases.

The hardest technical problem we solved

WhatsApp template approvals at scale.

WhatsApp's template-approval policy is undocumented in any useful sense and changes month-to-month. A real-estate developer needs ~25 distinct templates: lead ack, brochure, RERA disclosure, virtual tour, visit reminder, visit confirmation, post-visit thank-you, drip 1-5, etc. Submit them naively and 40% get rejected.

We built a template-versioning system inside the CRM. Each template has versions; rejections store Meta's reason code; a team-mate can iterate without losing history. We also encoded the policy patterns we'd learned (no commercial language in "authentication" templates, no embedded URLs in "marketing" templates without variable mapping, etc.).

Approval rate went from ~60% (industry default) to 92%. Time-to-launch a new template went from 3 days to 4 hours.

Go-to-market & ramp

We launched on a single property — 1,200 existing leads, 12 sales people, 30 channel partners. Two weeks of intensive ops involvement. Then second property, then third. By property five the on-boarding was a 3-day playbook.

Channel-partner adoption was the leading indicator. When we hit 70% of partners using the app weekly, lead quality jumped because partners shared their best clients, not their leftovers.

Results

4.2xSite-Visit Conversion (vs baseline)
28,000+Leads Managed
9Properties Live
87%WhatsApp Open Rate (24h)
48 secAvg Time-to-First-Response
60%Lead Volume from Channel Partners
Rs 4,800Avg CAC (vs Rs 22,000 portal-only)
92%WhatsApp Template Approval Rate

“Speed-to-first-touch was where we leaked everything. The platform closes that gap; the WhatsApp automation closes it for the leads we miss. Our channel-partner app is now the reason brokers keep coming back to us first.”

Sales Director

Residential Developer · Mumbai & Pune

What we would do differently

Build the channel-partner app in v1, not v1.5. We launched without it for the first six weeks; partners brought us mediocre leads because they had no skin in the game. Once we shipped the app and they could see real-time status + commission, lead quality jumped. Should have been week one.

Building a real-estate CRM or sales-automation platform?

Real estate is a speed game won by the tools you give your sales team and your channel. We've shipped CRMs that pay back in one launch cycle. Talk to engineers who've shipped this before.

Get a Free Consultation

Get Digital Growth Tips in Your Inbox

Weekly insights on app development, web design, SEO, and marketing. No spam — just actionable advice.

Join 2,500+ business owners. Unsubscribe anytime.