Rightmove AI lead response: how estate agents stop losing enquiries to slow replies

The first thing most buyers do after sending a Rightmove enquiry is open the next property on the list. Portal behaviour is not loyal. A buyer who sends three enquiries at once will speak to whichever agent replies first, and often book the viewing from that conversation. Rightmove AI lead response addresses this window directly: the gap between an enquiry landing in the inbox and a meaningful reply leaving the office. For most agencies that gap runs to hours, not minutes. The fix is not faster staff. It is an AI agent wired into the enquiry flow so the first reply goes back within seconds, qualified and in your agency's voice.

Why portal enquiries slip through

Portal enquiries are time-critical in a way that most agency workflows are not designed to handle. A Rightmove message arrives by email, often to the general office address, alongside solicitor threads, vendor calls and the day's outstanding tasks. A negotiator picks it up when they reach it.

By that point, the buyer may already have spoken to another agent. Some will have booked a viewing elsewhere. A few will have moved on from the property entirely. Speed matters more at the portal enquiry stage than almost anywhere else in the sales process, because the buyer has given you nothing beyond an email address and a momentary interest. There is no relationship to fall back on.

The second problem is qualification. Not every Rightmove enquiry is a proceedable buyer. Some are early-stage browsers. Some have circumstances that make the property unsuitable. Some are investors who want the yield before they want the address. Separating proceedable buyers from everyone else takes a conversation, and a conversation takes time.

These two problems compound each other. The team replies slowly because they are doing qualification work on every enquiry. And qualification suffers because there are too many enquiries to move through carefully. The result is a pipeline where the most time-sensitive leads get the most inconsistent handling.

How a Rightmove AI lead response agent works

The architecture is an event-triggered agent with one clear loop: trigger, read context, reason, take action, log.

The trigger is an inbound enquiry from Rightmove, Zoopla or OnTheMarket. The agent reads the enquiry text alongside the property record in the CRM, including the price, type, tenure, EPC rating, current availability and any notes already on file. It decides on the right response: a direct answer to the question the buyer asked, a short set of qualifying questions if the buyer has not provided key information, or an invitation to book a viewing if the signals are strong. It sends the reply in your agency's voice. It writes the exchange back to the CRM.

This is not a scripted chatbot. The agent reads the specific enquiry and constructs a specific response. A buyer who asks whether there is off-road parking gets an answer about parking. A buyer who asks about the chain situation gets the current position from the CRM notes. The reply is accurate and relevant, not a template.

Where the conversation goes next depends on what the buyer says. If they confirm they are mortgage-ready and available, the agent checks the diary and offers viewing slots. The confirmation lands with the buyer and the appointment appears in the CRM. If the buyer asks something the agent cannot answer from available data, sounds frustrated, or raises price, the thread is escalated to a negotiator with the full context already summarised. The negotiator picks up a briefed conversation, not a cold inbox thread.

This is the shape of Sortd's lead qualification service. The same event-driven loop also powers the viewing receptionist, which handles booking, confirmation and rescheduling once the enquiry has converted to a viewing. And the qualification data the agent collects on buying position, timescales and chain status feeds directly into sales progression once an offer is accepted, so the negotiator starts that process with context already assembled rather than collecting it again from scratch.

What it looks like on a Monday morning

Take an independent agency with two branches running a shared portal inbox. On a busy weekend, thirty enquiries arrive across Rightmove and Zoopla between Friday evening and Monday morning. Without automation, most are answered when the inbox is opened on Monday, which means buyers have had a silent weekend.

With an AI lead response agent running, the pattern is different.

A buyer sends an enquiry at 11pm on Saturday about a two-bedroom flat. The agent replies within seconds: a direct answer to their question, confirmation that the property is still available, and two qualifying questions about buying position and timescales. The buyer replies on Sunday morning. They are mortgage-ready, in a proceedable position and want to view on Tuesday. The agent books the Tuesday slot, sends the buyer a confirmation and creates the diary entry in the CRM.

On Monday morning, the negotiator opens the CRM and finds a booked viewing with a full note of the Saturday conversation already in place. The enquiry is resolved.

The same process runs across every enquiry that came in over the weekend. The ones that needed a judgement call are flagged and waiting. The ones that were straightforward and qualified are booked. The negotiator's Monday starts with a clear picture rather than a backlog of unanswered messages.

Compliance and integration

Portal enquiry handling touches personal data from the first message. The buyer's name, contact details and stated buying position are subject to UK GDPR from the moment they arrive in your inbox.

The lawful basis for processing is usually legitimate interests: responding to a direct enquiry from someone who chose to make contact via a property portal. The agent processes only what is necessary for that purpose, holds data in line with your agency's privacy notice, and does not retain it beyond what the enquiry requires. Every Sortd build uses UK or EU data residency by default. No buyer data is routed through US infrastructure.

The TPO code of practice requires that buyers are dealt with honestly and accurately. AI-generated replies must not create false impressions about the property, its availability, or the agency's capacity to act. The agency is responsible for every message sent in its name. The voice, tone and factual scope of the agent are agreed with your team before anything reaches a live buyer, and the agent is tested against real enquiry samples from your own inbox before going live.

On integration, the enquiry agent connects to Reapit, Alto, Jupix, Vebra, Dezrez and agentOS. Enquiries from Rightmove and Zoopla arrive via webhook or email parsing depending on the portal's available integration options. Property Industry Eye covers AI adoption patterns across the UK agency sector if you want a broader view of where the market is moving. The Negotiator is a useful source for how portal relationships and technology are developing across the industry.

How to evaluate and get started

The right starting point is your current portal numbers. How many enquiries arrive each week across Rightmove and Zoopla? How long does a first reply typically take? What proportion of enquiries convert to a booked viewing, and how many go cold before any contact is made?

Those are the baseline figures. A lead response agent is evaluated against them. If a build cannot demonstrate a measurable change in reply speed and enquiry-to-viewing conversion, it is not a well-specified build. Be direct about this with any supplier you evaluate.

Sortd's starting point is a discovery call and a free working version of the agent. We build the agent, wire it into a test slice of your enquiry flow, and run it against real incoming enquiries before anything goes near a live buyer. You see how it responds to your actual leads, in your agency's voice, before it speaks to anyone.

If the speed of first response to Rightmove enquiries is costing your agency viewings, start with a conversation.