Property portal and website lead integration
Property portal lead integration moves enquiries from listing portals, landing pages and form tools into the developer's CRM automatically. MapBhoomi gives each portal or tool its own secret webhook URL with a preset source, project and campaign and a field map, accepts JSON, form or query posts, also takes leads through a REST API with project keys, merges repeat buyers by phone or email, and logs each post as created, merged or failed.
Portal leads usually arrive as emails, or in a dashboard nobody checks on Sunday. Every hour they wait, the buyer is talking to someone else. Pushing them straight into the CRM puts them in the same queue, with the same rules, as every other lead.
Where the usual way breaks
- Portal leads arrive by email and are copied in by hand.
- The same buyer comes from two portals and is called twice.
- Nobody can tell which portal brings bookings.
- Landing page forms email an inbox nobody owns.
Ways leads come in
- A secret webhook URL per portal or form tool, which you can rotate.
- Field mapping by path, or common portal field names recognised automatically.
- REST API: post a lead with a project key; a new lead returns 201, a merged one 200.
- Hosted and embeddable forms, with UTM tags mapped to campaigns.
- CSV import with a dry run first.
One queue for every source
Whatever the source, the lead goes through the same deduplication, assignment rules and first-response timer, and its source is kept for reports.
Who it is for
- Developers listing on several property portals
- Marketing teams with landing pages
- Agencies sending leads to builders
- Teams replacing email lead alerts
Portal enquiries into one queue
- Buyer enquires on a portal. Buyer: Enquired on a listing (Skyline Towers · 3 BHK).
- Portal posts to your webhook. Sales team: Webhook post · created (Source and project preset).
- Same buyer, second portal. Buyer: Enquired on another portal (Same phone number). Sales team: Merged into the lead (Score raised, no second call).
- Assigned, timer running. Sales team: Assigned to Kiran (First-response timer on). Buyer: Call from Skyline Towers (One call, not two).
- Portals compared. Management: Leads and bookings by source (Which portal sells).
Modules it uses
- Pre-sales CRM: Every enquiry becomes a lead with an owner, a next step and a visit
- Live inventory maps: Your layout, live: every plot coloured by what it is right now
- WhatsApp: Receipts, reminders and replies on WhatsApp, from your number or ours
- Sales & collections: Hold, book and collect from the map, with every rupee tracked to the unit
- Builder websites: A premium company website from your live projects, on your own domain
Which portals are supported?
Any portal or tool that can post to a webhook URL or call an API. Fields are mapped once per source.
What if the same buyer comes from two portals?
The second enquiry joins the existing lead and raises its score.
Can I see what a portal sent?
Each webhook keeps a log of recent posts with their result and the field names received.
Is the webhook secure?
Each URL carries a secret token checked on every post; rotating it stops the old URL at once.