Rebuilding intake for a property brokerage

Why intake, not speed

It would have been easy to sell this brokerage a faster auto responder. It is the obvious fix, and it would have made the real problem worse, because a faster reply to an enquiry that never becomes a record just loses the same lead more quickly.

The diagnosis traced one enquiry from each channel end to end and timed every handover. The delay was real, but it was a symptom. The cause was that four channels wrote to four places, so there was no single record to reply from, report on, or trust. Fixing the reply time without fixing the record would have papered over the leak.

What we built, and what we deliberately did not

We built a single intake layer in front of the tools they already used. Every channel, the four portals, the web form, and WhatsApp, lands in one place, becomes one record, and is checked against existing contacts before it is created, so the same buyer stops appearing three times.

The one place AI earned its keep was reading the unstructured portal text into clean fields: budget, location, bedrooms, timeline. It drafts, a person confirms, and the confirmation teaches the next draft. Everywhere a decision needed a human, an agent stayed in the loop by design. This is the line we hold on every AI system we build.

What we did not do matters as much. We did not migrate them to a new CRM, because the one they had was fine once it was being fed correctly. We did not build a chat bot to talk to buyers, because the agents were good at that part. The build was small on purpose, aimed only at the step the diagnosis had priced as the most expensive.

The shape of the result

The outcome numbers above are held until the brokerage clears them for publication, so they read as placeholders here rather than invented figures. The shape is consistent with the pattern: when intake becomes one clean record instead of four scattered ones, the enquiries that used to evaporate turn into conversations, and the hours agents spent re-typing turn back into selling.

If you recognise your own business in the situation, the same arc starts the same way, with a diagnosis that prices the leak before anyone writes code. The reasoning behind starting there is worked through in our guide to build versus buy.