An estate agency responds to every portal lead in under two minutes, automatically

Representative examplesEvery case study in this library is an illustrative composite of the kind of engagement we deliver — written to show our method and standards, not to name clients.

Where they started

Three high-street branches sell and let residential property, with most buyer enquiries arriving through the big property portals. Agents spend the day out on viewings — the branches live by appointments, not inboxes — and the culture runs on the phone: a good agent rings a hot buyer back within minutes or loses them to whoever does. Each branch had evolved its own habits for sharing leads between the desk and the road, none of them written down, all of them dependent on whoever happened to be at the computer.

What it was costing

Portal leads arrived by email at all hours; the first agent to notice replied, everyone else assumed someone had. Response time averaged 9 hours, and post-viewing follow-up depended on memory — two hot buyers went cold every month.

What they could see

• Portal leads sat unread for hours when the on-duty agent was showing a property, because the inbox lived on one desktop.
• Two agents occasionally replied to the same lead from different branches, and the buyer got two different voices in one morning.
• Post-viewing follow-up lived in memory and diaries; the feedback request went out only if someone remembered on the drive back.
• The branch managers could not answer who was chasing which lead without calling each other.

The constraints we worked inside

• Agents work viewings, not inboxes — routing had to respect who was actually available.
• Three portals, three payload formats — normalization had to be boring and reliable.
• The agency's phone-first culture meant the system had to text, not email.

What had been tried before

A shared inbox alias was set up so every agent could see portal enquiries.

Seeing is not owning — replies duplicated when two agents checked within minutes of each other, and unclaimed leads just sat there longer.

The principal bought a CRM seat for each branch after a trade show.

Agents work from phones between viewings; a desktop-first CRM got updated at closing time, by which point the response window was gone.

What we proposed

We proposed an n8n cloud workflow that watches all three portal mailboxes, normalizes every enquiry into one lead record, and routes it by text to whichever agent is actually on duty — with acknowledgment tracking so an unclaimed lead escalates to the branch manager in minutes instead of dying. The routing logic keys off the shift rota rather than the clock alone, because an agent deep in a viewing isn't available no matter what the timer says. Post-viewing follow-ups run on schedules keyed to the viewing itself, which ends the memory dependency. The CRM they already have stays the record; nothing asked the branches to change tools.

Just as important is what we ruled out, and why:

• A full CRM migration first — Four weeks cannot absorb a data migration and a culture change; we routed into the CRM they had and left re-platforming for later.
• An auto-reply email for every lead — Their buyers phone and text; a templated email would have satisfied the SLA on paper while doing nothing for the conversation.
• A website chatbot to pre-qualify buyers — The leads come from portals, not the site — the bottleneck was distribution between agents, not intake volume.

How the work ran

Delivered by the systems pod — automation specialist over 4 weeks, with working increments reviewed with the client every week.

The stack, and the reasoning

n8n (cloud)

No one at the agency maintains servers; the cloud tier meant the owner's IT contact manages a login, not a machine.

Email/portal triggers

All three portals deliver by email, so watching those mailboxes covered every source without asking a portal for anything special.

SMS node

The phone-first culture settled it — an email notification would have waited; a text gets read between appointments.

CRM integration

Leads write straight into the CRM the branches already had, so history survives even when the agent on duty changes.

Error workflows

A dropped lead is lost revenue nobody notices; failures now hold the lead in a review state until a human claims it, instead of paging anyone or vanishing.

What went wrong

How we worked together

Cadence

Fifteen minutes with the branch managers every Monday and Friday; between calls, a live dashboard of unacknowledged leads did the nagging.

Client side

The principal's deputy owned the rota rules; each branch nominated its most organised agent to test routing for a week.

Decisions

The deputy settled anything the demo didn't — escalation windows, rota edge cases — usually by text the same day.

They provided

Portal notification samples from all three sources, the shift rota for each branch, and a quiet Friday to trial live routing.

What changed

The headline: median first-response time to portal leads, first full month — 9 hrs → <2 min, read from Workflow timestamps. A second check: second viewings booked from portal leads at +23%.

The branches stopped competing for inbox luck and started competing on callbacks. The deputy reads the morning routing report instead of asking who saw what, and the Friday argument about who dropped a lead has simply ended — the log answers it. Post-viewing follow-ups go out on schedule whether or not the agent remembered, which changed the tone of buyer conversations: agents now promise a second viewing knowing the system will hold the thread. When one branch covered a holiday from the old shared inbox, the agents asked for the routing back before the week was out.

The result was read from Workflow timestamps against the pre-engagement baseline over the stated window, with a guardrail check on second viewings booked from portal leads. Where platform-reported numbers and business outcomes differ, this record says which layer it is quoting.

What they own now

• The n8n cloud workspace watching all three portal mailboxes, with a documented export of the routing, escalation, and follow-up workflows.
• A one-page runbook for adding a new portal trigger to the normalizer, including where the mailbox credentials live.
• The routing and escalation rules written out, signed off by the deputy.
• Access to the unacknowledged-leads dashboard the managers now open daily.
• A walkthrough recording for new agents explaining what happens when a lead arrives.