Handling out-of-hours enquiries for estate agents with AI

Most UK estate agent offices close between 5:30pm and 6pm. Rightmove, Zoopla and OnTheMarket do not. Out-of-hours estate agent enquiries are a documented operational gap: buyers who work full-time browse property portals on weekday evenings and over weekends, and the enquiries they submit sit unanswered until the following morning or after the weekend. A viewing request submitted at 7pm on a Thursday receives a response fourteen or more hours later. One submitted at 6pm on a Friday can wait more than sixty hours. Handling out-of-hours enquiries for estate agents with AI closes that gap without requiring office staff to work unsociable hours or outsourcing calls to a generic answering service.

Why out-of-hours enquiries are a bigger risk than they look

The mechanics are simpler than most acknowledge. A buyer submits an enquiry. If no one replies promptly, they move on. In a market where the same type of property appears on multiple agents' books, a slow response is a signal about the agency's responsiveness in general. A buyer who requests a viewing on a Friday evening and hears nothing until Monday may have already booked a viewing through another agent over the weekend.

The cost is not only the lost viewing. Agents who have a mechanism for responding out of hours capture first contact with the buyer before competitors do. First contact with a motivated buyer has value at valuation as well as at sale. An agency that can honestly say they respond to portal enquiries within the hour is making a credible, verifiable distinction.

The common alternative to doing nothing is a telephone answering service. These vary widely across the industry. At their best, they capture a name, a number and the property the caller is asking about. At their worst, they take a message and promise a callback without recording enough context to make that callback useful. Either way, office staff arrive in the morning with a list of callbacks and no prioritisation information.

AI out-of-hours enquiry handling is a different shape of solution. It does not replace a person. It ensures that every evening or weekend enquiry receives an accurate, appropriate response within minutes, that the relevant context is captured and logged, and that the negotiator arrives the next morning briefed rather than starting from a cold voicemail list.

What an AI agent does with an out-of-hours enquiry

The shape of the system follows the same event-triggered loop Sortd applies across its estate agency automation work: trigger, read context, reason, take action, log.

Trigger. An enquiry arrives outside business hours via the portal integration, by email or through the agency's contact form. The agent receives it immediately. There is no polling delay and no need for someone to be watching an inbox.

Read context. The agent reads the enquiry text and cross-references it against the property record in the CRM. It checks what the property is, where it is in the pipeline (available, under offer, or let agreed) and, where the enquirer's email matches an existing contact, what previous interaction the agency has had with them. If the property is already under offer, the response changes. If the enquirer has submitted enquiries about several properties over the past few weeks, that context is relevant to the morning briefing.

Reason. The agent classifies the enquiry. A straightforward viewing request for an available property is one type of task. A question about the chain, a query about price or a complaint from an existing client each warrant a different response and a different person to see it in the morning.

Take action. For a viewing request on an available property, the agent sends an acknowledgement: the buyer's name, the property they enquired about, a clear statement that the team will contact them in the morning to confirm a time, and any relevant publicly available details about the property. It does not promise a specific viewing slot it has not confirmed. It does not commit the agency to something a negotiator has not agreed to. Where the agency's diary is exposed to the agent, it can tentatively suggest an available slot pending confirmation, provided the copy is worded accurately to reflect that status.

For enquiries that are not straightforward viewing requests, the agent acknowledges receipt and flags the message for the appropriate person without attempting a substantive reply on a subject that needs a human.

All responses pass through the same approval layer that Sortd's viewing receptionist service applies: the agency's tone, the correct property name and the right call to action, checked against the record before anything is sent.

From enquiry to morning briefing

The log step is where the overnight handling produces its clearest value for the negotiator starting the day.

Every enquiry processed out of hours is logged in the CRM with the enquiry text, the response sent, the classification and any context the agent extracted from the record. Where the lead qualification layer has previous information about the enquirer, that is surfaced alongside the new enquiry. The negotiator's morning briefing presents this as a card for each overnight enquiry: buyer name, time of enquiry, property, what was said, what the agent replied, and a suggested opening line for the callback.

The negotiator arrives knowing exactly who to call, about which property and with what to say. The buyer, meanwhile, has already received a professional response and is not wondering whether their enquiry reached anyone. The gap that exists in a manual-only operation has been closed on both ends.

What it looks like for an agency

A two-branch independent running fifty active instructions. It is Saturday afternoon. A buyer submits a Rightmove enquiry for a three-bedroom semi at 2:15pm asking about weekend viewings.

Within a few minutes, the buyer receives a response. It uses the agency's name, acknowledges the specific property and tells them a member of the team will be in touch on Monday morning to arrange a time. It includes the property's headline specification in case they are comparing several options. There is no generic "thank you for your message" and no promise the agency cannot keep.

On Monday morning, the negotiator opens their briefing digest. The Saturday enquiry appears at the top: buyer name, time received, the property, the response sent, a note from the enquiry text that the buyer is available at weekends, and a suggested opening line for the call. The negotiator calls at 9:20am. The buyer had heard from two other agents over the weekend but had not yet committed to a viewing. The appointment is confirmed.

The digest also shows a Friday evening enquiry that was classified as a question about a property already under offer. The agent responded with an accurate status update and flagged the enquirer as a potential match for a similar property at the same price point. The negotiator has the context to decide whether to follow up with an alternative without needing to re-read the original message.

The inbox copilot layer connects the out-of-hours handling to the full working-day email flow, so the context built overnight carries into the negotiator's inbox management from the moment they open their laptop.

Compliance and integration

Out-of-hours enquiry handling sits within UK GDPR's legitimate interests ground in most cases. The person who submitted an enquiry has initiated contact about a specific property. Responding to that contact, logging it and using the information to follow up is processing a reasonable person would expect. The key obligation is accuracy: the AI's response must not confirm a viewing time that has not been agreed, describe a property incorrectly or suggest a negotiator will call at a time the agency cannot guarantee. The TPO code requires that applicant communications are accurate and not misleading. A system that makes promises it cannot keep creates liability regardless of whether a person or a machine made them.

UK GDPR also requires that data is held within UK or EU infrastructure. Sortd runs on UK and EU servers by default. The AI provider operating the language model must have a data processing agreement in place before any live enquiry data is involved, and enquiry data is not used for model training. These conditions are written into the build contract, not left to a terms-of-service clause to handle.

CRM integration covers the platforms UK independent agencies use: Reapit, Alto, Jupix, Vebra, Dezrez and agentOS. Propertymark publishes guidance on client communication standards that is worth reading alongside any AI deployment in this area. Property Industry Eye carries regular coverage of how agencies are adapting to portal-driven lead volumes and response time expectations.

How to get started

The right starting point is an honest count of your out-of-hours enquiry traffic. Across one month of portal activity, look at how many enquiries arrived outside business hours and measure the average response time for each. Then look at the conversion rate on those enquiries compared to enquiries that received a same-hour response. The gap is usually larger than expected, and it is consistent across the week.

Sortd builds a working version of the out-of-hours loop against your portal integrations and CRM at no cost before anything touches a live enquiry. You approve the response templates. You set the business hours boundary. You decide which enquiry types receive an immediate response and which are held for a person to handle the following morning.

If out-of-hours estate agent enquiries are converting at a lower rate than your daytime leads, book a discovery call and we will show you what the build looks like on your actual enquiry flow.