A Kolkata real-estate developer had leads scattered across Meta ads, WhatsApp, and manual intake with no shared visibility. DXDasia built a custom CRM (customer relationship management) that unifies lead capture, automates WhatsApp notifications and legal document generation, and feeds real sale outcomes back into Meta ad optimization.
One Pipeline, From Ad Click to Signed Agreement
Leads for a growing real-estate developer arrived from three disconnected places with no shared record.
We built a CRM around the developer’s actual sales process, not a generic template.
The sales team now works from one system instead of three disconnected channels:
Real-estate sales cycles are long and touch a lot of paperwork — the win wasn’t a single flashy feature, it was removing every manual handoff between a lead coming in and a deal closing, so nothing depends on one person’s memory or availability.
The CRM ingests leads two ways: a webhook that receives Meta lead-ad submissions the moment they’re submitted, and a WhatsApp messaging integration that auto-creates a lead from any inbound message that doesn’t already match an existing customer. Every automated WhatsApp send and inbound reply is logged against the lead record, so a salesperson opening a lead sees the full conversation history, not just a phone number. Document generation runs through a hand-built PDF engine that pulls real unit pricing, GST calculations, and payment-plan data directly from the database, so every generated agreement reflects the actual deal, not a static template with blanks. Outcome data flows back out to the ad platform on every status change, closing the loop between ad spend and actual sales.
In property sales the weak point is rarely the advertisement. It is the hand-off between a form submission, a call, a site visit and a booking. Meta's own guidance for connecting a CRM to lead ads is built around that gap: advertisers should send all stages of leads as they are updated, a minimum of two stages including the raw lead event, and three or more if possible.
| Requirement | Meta's guidance |
|---|---|
| Lead volume | At least 200 leads per month |
| Stages sent | Minimum two, including the raw lead; three or more recommended |
| Optimisation stage timing | Within 28 days of the lead being generated |
| Optimisation stage conversion rate | Between 1% and 40% |
| Lead coverage | At least 60% of leads |
| Matching | lead_id from the lead ad, stored with the lead |
Source: [Meta for Developers, Conversions API for CRM](https://developers.facebook.com/documentation/ads-commerce/conversions-api/guides/conversions-api-crm-for-platforms).
Read literally, a stage that very few leads reach, such as a signed agreement, may fall outside the 1% to 40% window, and a long sale may not complete within 28 days. In practice that points towards a mid-funnel stage such as a confirmed site visit as the optimisation event, with later stages still reported so the team can see which channels produce sales.
WhatsApp's Business Messaging Policy says a business may contact someone only if they have given their number and opt-in permission to receive messages, and the business is solely responsible for how opt-in is obtained. On cost, Meta bills per delivered template message since 1 July 2025. Non-template messages can be sent only inside the 24-hour customer service window, which opens when the user messages you, and utility templates sent inside an open window are free.
That makes record-keeping part of the design: store when and where each buyer opted in, and log every message and reply against the lead. The same discipline applies to documents. Commentary on RERA notes that the Act expects advertisements to be consistent with sanctioned plans, so pricing and unit details should come from one source of truth rather than being retyped into each booking form or agreement. Our overview of a WhatsApp automation platform explains the messaging side in more detail.
ANAROCK's H1 2025 survey found that 98% of surveyed buyers want timely completion assurance, which makes proactive progress and payment updates a trust feature as well as a convenience. Speed matters earlier in the funnel too: Harvard Business Review's research concluded that most companies are not responding nearly fast enough to online leads. Accuracy carries legal weight in this sector. MahaRERA has penalised an advertiser whose registration details were illegible, so the same care belongs in every generated document.
Whether you buy a CRM or build one, these steps decide whether the ad account learns from real sales.
In our own WhatsApp CRM, used by e-commerce clients, a shopper complained about receiving abandoned-cart reminders "once every day". Reminders were capped per cart instead of per customer, and a backlog of old carts was released at once. We now cap marketing messages at 2 per contact per rolling 7 days and nudges at 1 per contact per 24 hours, while order-status messages are never capped. The lesson carries over to property: cap messages per person, not per record.
With inbound WhatsApp already logging into the CRM, the next phase is giving the sales team a full two-way WhatsApp inbox inside the CRM itself, so replies never have to leave the system leads already live in. The ad-conversion feedback loop is also young enough that its real value — letting ad spend shift toward the channels and creatives that produce actual sales, not just form fills — will keep compounding as more sale outcomes accumulate in the data.
Yes. Meta's Conversions API for CRM lets you send lead stage updates, matched by lead_id, so campaigns optimise towards leads that progress rather than those that merely submit a form. Meta recommends at least 200 leads per month and a minimum of two stages.
Meta advises a stage reached within 28 days of the lead and by between 1% and 40% of leads, per its CRM guidance. For long property cycles that usually means a confirmed site visit rather than a booking. Keep reporting later stages so you can judge channels by sales.
Only with their permission. WhatsApp's policy requires opt-in confirming the person wishes to receive messages. Add a clear consent line to the form, store the timestamp, and use approved templates when the 24-hour service window is closed.
Buy if your process is standard and the tool already handles stages, WhatsApp and Meta feedback. Build when your pricing, tax, commission or document logic is specific to you. Our work on AI-assisted CRM and custom web applications covers both routes.
