Reliable Lead Capture and Lot Availability for a Residential Developer

#The starting position

Selling house and land is a long, emotional purchase compressed into a few critical moments. A family sees an estate advertised, enquires, visits, chooses a lot, pays a deposit and waits for settlement. At every step, the developer has to know exactly which lots are available, which are held and which are sold, and the buyer has to hear back quickly from someone who knows the estate.

The developer in this engagement sells lots across several estates. Leads come from Facebook Lead Ads, the website and estate marketing tools. Lot information is published through Mapovis, the interactive estate map buyers use to choose a lot. Sales staff work in Microsoft 365 and Salesforce.

The business depended on these systems agreeing with each other, and they often did not. Lot statuses did not always follow the deals: the rule that moved a lot from available to held to sold did not track the deposit milestones properly and did not exclude lost opportunities, so lots could appear committed when they were free. A mapping error in the Zapier step that brought Facebook leads into Salesforce meant phone numbers were not landing in the right field, so some leads could not be called. Email history with buyers was inconsistent, because the connection to Microsoft email was not working reliably for every user. And, like any busy sales team, people were regularly locked out of Salesforce by multi-factor authentication changes.

Each estate also had its own rhythm. Releases of new stages, price changes and promotions all created bursts of enquiries, and those are exactly the moments when a broken lead mapping or a wrong lot status does the most damage.

None of these problems was dramatic on its own. Together they meant lost leads, confused buyers and a sales team that did not fully trust the system.

#What we built and fixed

01 Opportunity-to-lot status automation

We rebuilt the Flow that keeps lot status in step with the deal. The status of a lot now follows the deposit milestones on the opportunity that is buying it, and opportunities marked Closed Lost are explicitly excluded, so a lost deal can never hold a lot. Lot availability is now a consequence of the sales process instead of a separate task.

02 Lead capture from Facebook

We corrected the phone field mapping in the Zapier integration that brings Facebook Lead Ads into Salesforce. Every new Facebook lead now arrives with a callable phone number in the right field.

03 Lead routing by estate

Leads and opportunities are routed according to the estate and project they relate to, with project-specific processes where an estate needs them. A buyer asking about one estate reaches the people selling it.

04 Mapovis lot data and document links

We supported the Mapovis integration with the data fields it needs and the workflows that store document URLs, so lot information and supporting documents are consistent between the estate map and Salesforce.

05 Email capture from Microsoft 365

We troubleshot and fixed the connection between Salesforce Inbox, Microsoft Graph and Einstein Activity Capture, including the permissions behind it, so emails with buyers are recorded against the right records without staff changing how they work.

06 Settlement communication

For one of the estates, we built email automation around settlement, the final and most anxious stage for a buyer, so they receive consistent communication as their purchase completes.

07 Access and account support

We handle login, multi-factor authentication and passkey recovery for the team, the unglamorous work that keeps a sales team selling instead of waiting for access.

08 ActiveCampaign sync, staged for acceptance

The lead sync between ActiveCampaign and Salesforce is configured in a sandbox and awaiting user acceptance testing. It is deliberately kept separate from the live integrations until the developer signs it off.

#A lot, from enquiry to settlement

A couple sees an estate advertised on Facebook and fills in the lead form. The lead reaches Salesforce through Zapier with their phone number in the right place and is routed to the team selling that estate. A salesperson calls the same day, and the conversation that follows by email is captured from Microsoft 365 onto the record.

They visit, choose a lot on the Mapovis map and pay an initial deposit. The opportunity moves to the deposit stage, and the Flow updates the lot's status, so the map and the sales team both show it as held. If the couple later withdraw and the opportunity is marked lost, the rule ignores it and the lot is free to sell again. If they proceed, the lot moves through to sold as the deposit milestones are met, and settlement emails keep them informed through the final stage.

At no point does anyone edit a lot status by hand, and at no point does the map disagree with the CRM.

#Why availability has to be automatic

For a developer, lot availability is the inventory, and inventory errors are expensive in both directions. A lot shown as sold when it is free is revenue left on the table, sometimes for months. A lot shown as free when it is committed leads to two buyers wanting the same block, which is one of the worst conversations a sales team can have.

Manual status updates fail because they depend on someone remembering, at the right moment, in the right system. Tying the status to the deposit milestones on the opportunity removes the memory from the process. The rule has to be precise, though. It must follow the real milestones the business uses, and it must handle the unhappy path, a lost deal, as carefully as the happy one. That is where the original logic fell short, and where most of the fix was focused.

#How we delivered it, end to end

Find the breaks first. We traced each integration and automation from source to record and listed every point where data was lost or contradicted, from the Zapier phone mapping to the lot status rule.

Fix the rules that drive inventory. The opportunity-to-lot logic was corrected first, because availability errors have the biggest commercial cost.

Repair, then extend. Lead capture, routing, Mapovis fields and email capture were repaired before new integrations were added.

Stage new integrations honestly. The ActiveCampaign sync is built in a sandbox and waits for acceptance before it touches live data.

Stay close to the team. Ongoing administration, access support and settlement automation keep the system useful day to day.

#The decisions that mattered

Automate lot status completely. Allowing manual overrides would have reintroduced the errors. The deal drives the lot.

Treat lost deals as a first-class case. Excluding Closed Lost was the single most important line in the new rule.

Fix the plumbing before adding pipes. Repairing existing integrations delivered more value, sooner, than adding new ones would have.

#What changed

#What we would tell a developer starting this

Make lot availability a result of the sales process, and test the rule against every way a deal can end, not just the good ones. Then audit every lead source end to end, because a single broken mapping can silently cost you buyers. Fix what you already have before you add more, and keep anything unfinished clearly labeled until your team has signed it off.