AI Receptionist for Estate Agents: Cost, Call Flow and Handover

An AI receptionist costs an estate agency about $50 to $300 a month on general plans and $499 to $1,500 on property-specific ones, against $810 to $2,100 for a human service. It should capture valuation and viewing details, then pass hot callers to a negotiator by live transfer or instant text.

The money is not the hard part. The hard part is the handover: software can answer a valuation call in one ring, but if the details reach a negotiator as a vague voicemail or arrive an hour late, you have bought a faster way to lose instructions. Judge any option first by what lands on the negotiator's phone and how quickly, and only then by its price.

Follow me on Instagram@sagnikteaches

Cost bands: what each kind of phone cover costs a month

I read the vendors' own pricing pages in October 2026. Figures are USD list prices and they move, so treat them as a guide to where each kind of product sits. One property-specific product, one general product family and two human options give a useful spread.

Connect on LinkedInSagnik Bhattacharya

So the real bands for a small agency are: about $49 to $299 a month for a general plan you configure yourself, $499 and up for a product designed around property enquiries, and $300 to $2,100 for human cover depending on calls. If you work at the cheap end you do the configuration: the valuation flow below is yours to write. If you pay for a property-specific product, ask to hear it handle a valuation request, not only a viewing, because the EstateVoice page describes showings in detail and valuations not at all.

Subscribe on YouTube@sagnikteaches

What 300 missed calls cost to cover in a sales and lettings office

Take an illustrative independent agency with six people: a branch manager, three negotiators, a lettings manager and an administrator. The phone gets about 40 inbound calls on a working day, 22 working days a month, so roughly 880 calls. Suppose, as an assumption to replace with your own phone log, that about a third are missed or arrive after hours: roughly 300 calls a month for the assistant, averaging two and a half minutes each.

The last row's sum is 17 × 40 × 52 / 12 = $2,946.67 a month before employer costs, and the hourly figure is an assumption. The cost per call is simply the monthly cost divided by 300. It is not a measure of quality: the cheapest option needs the most configuration, and the in-house option is the only one that reads a caller's mood well.

The question that matters is whether any option pays back. Say, as an assumption, a won sales instruction earns the agency $3,000 in fees. A $500 plan then needs just one extra instruction every six months to break even. A $129 plan needs one every 23 months. So the sensible test is not "is it cheap?" but "how many of my 300 missed calls were real vendors or landlords?" Check your phone log for four weeks, count missed calls from numbers not in your CRM, and call back a sample to see what they wanted.

Valuations, viewings, offers, repairs: who owns each call

An estate agency phone is not one flow. Write the owner of each call type before you configure anything.

If a call does not fit, the fallback is a message to the branch manager's queue with the transcript attached. For a broader view of which AI tools suit which part of the agency, AI tools for estate agents, by job from valuation to completion shows where the phone fits in the stack.

The valuation call, word for word

A valuation enquiry is the most valuable call an agency gets, and the one where a bad first impression costs most. The assistant's job is to be quick, collect the right facts, and avoid giving an opinion on price. An illustrative flow:

ASSISTANT: "Good morning, [agency name]. I'm an automated assistant.
How can I help?"
CALLER: "I'd like someone to value my house."
ASSISTANT: "Happy to arrange that. Can I take your name and the best
number to reach you on?"
...
Fields to collect, in this order:
1. Name, mobile number
2. Property address and postcode
3. Type and bedrooms (flat/house/bungalow, number of bedrooms)
4. Selling or letting?
5. Roughly when they want to move (this month / 3 months / just curious)
6. Whether the property is currently let (letting only)
7. Two or three preferred days/times for a visit

IF ASKED "WHAT'S IT WORTH?":
"I can't give a figure. A valuer will visit, look at the property and
give you a proper opinion. When suits you?"

Notice the order: contact details first, so a dropped line still leaves a callback number. The assistant refuses a price opinion every time, because a number from a phone assistant becomes the vendor's anchor. If your calendar is shared with the assistant, it can offer real slots. If not, it should collect two preferred times and tell the caller a valuer will confirm, with a text confirming the request. How estate agents use AI to prepare valuation appointments picks up where this call ends, once the visit is booked.

The viewing call and the applicant questions

Viewing calls are simpler, but they carry two traps: availability and qualification. The assistant must not say a property is available unless it reads live data. And it must not improvise questions to applicants. Here is an illustrative flow for a viewing request:

1. Which property? (address or listing reference)
2. How many people will attend?
3. Preferred days and times (two options)
4. Name and mobile number
5. Is there anything we should know about access? (parking, mobility)

SAY: "I'll pass this to [negotiator] who confirms the time and
availability. You'll get a text shortly."

DO NOT: confirm the property is still available, answer whether the
vendor will accept offers, give the vendor's reason for selling, or
ask about the caller's family, job, benefits, age or nationality.

Keep any applicant registration to the fixed questions on your own registration form: budget range, areas, number of bedrooms, timescale, and for lettings the move-in date. Anything beyond that list should be a person's judgement. Equality law applies to how you treat enquirers, so do not let a model invent screening questions. Have your compliance contact or solicitor look at the form before it goes into the assistant's instructions.

For lettings, the registration record is the useful output. An illustrative one the assistant might email to the lettings manager after an applicant call:

APPLICANT REGISTRATION
Name: [first name] [surname]   Mobile: [number]
Looking for: 2-bed flat to rent
Budget: $1,300 to $1,600 a month (caller's range)
Areas: [area one], [area two]
Move-in: by [date]
Pets: asked only if the caller raised it
Notes: wants a garden or balcony; works from home
Not asked: household, employment, benefits, nationality

Check three things when you read records like this: the budget is a range the caller gave, the move-in is a date and not "soon", and the final line shows what the assistant deliberately did not ask. If a record contains a guess, such as "probably a family", remove that behaviour from the instructions at once.

Handover to a negotiator: the moment the phone should ring

A handover is the point where the assistant stops and a person takes over, and it works in two forms: a live transfer to a mobile or desk phone, or an instant message with a summary. Use live transfer sparingly, because every transfer interrupts someone. Reserve it for:

• A caller who says they want to make an offer or are ready to proceed.
• An existing vendor or landlord asking to speak to their negotiator.
• A caller who has asked for a person twice.
• An emergency on a managed property (to the on-call number, not a general queue).

Everything else is a message. For the transfer, set staffed hours, name the person for each property or area, and give a fallback if they do not answer within about 20 seconds: take a message and promise a call-back time. An illustrative text that lands on the negotiator's phone after a viewing request:

VIEWING REQUEST  14:12
Property: 14 [street name], 3-bed semi, ref 20417
Caller: [first name] [surname], 2 adults, mobile [number]
Wants: Sat 10:00-12:00 or Mon after 17:30
Said: "Is it still available?" - NOT answered, needs your confirmation
Action: please confirm availability and time by text within the hour
Recording and transcript: [links]

The line "NOT answered, needs your confirmation" is what makes this a good summary. The assistant is honest about what it did not say, and the negotiator knows the exact first step. Agree a target response time with your team, for example within the hour in working hours, and track it for the first month. If you plan to automate what happens after the first contact, automating buyer and vendor follow-up with AI covers the next stage.

Evening and weekend calls: before and after

Before: a vendor rings at 7pm on a Thursday. The office is shut. The phone goes to voicemail: "Please leave a message." The caller hangs up, because they have rung two other agencies and one of them answers. The agency never knows there was a call.

After: the assistant answers, says it is automated, collects the address, property type, timescale and two preferred times, and sends a summary to the valuer. The valuer sees it at 8:30 the next morning, texts the vendor with a proposed slot, and the visit is booked before the competitor has called back. Nothing about this required a human at 7pm. It did require a script that captured the right fields and a summary the valuer could act on in one read. Your own phone log is the evidence: look at when calls arrive and which hours go unanswered, rather than assuming.

Is it still for sale? A first test call and its fixes

Weight your test calls towards the two kinds that lead to fees, valuations and viewings, then add an offer, a lettings emergency, an applicant registration and a caller who will not give a number. An illustrative transcript from a first configuration:

TESTER: "Hi, I saw the flat on [street] in the window. Is it still for sale?"
ASSISTANT: "Yes, that property is currently available. Would you like
to arrange a viewing?"
TESTER: "What's the lowest they'd take?"
ASSISTANT: "The asking price is [price]. Offers are considered by the
vendor. I can take your details so a negotiator can discuss it."

Two things are wrong. The first answer asserted availability from a knowledge base that was weeks old. The second quoted a price, which was acceptable from the listing, but "offers are considered by the vendor" edges into a position on negotiation. Fixes: add the rule "never state availability, under offer status or price flexibility; say a negotiator will confirm", then rerun the same call and keep the transcript. If your vendor offers simulated calls or a test mode, use it for volume, and make the final calls on a real phone line. For checks to run in a vendor demo, a real estate AI chatbot demo test checklist has useful questions that apply to voice as well.

Under offer on Monday, two viewings booked on Tuesday

A negotiator marks a flat as under offer on Monday. The assistant's knowledge base still lists it as available, because the listing export runs once a week. On Tuesday the assistant tells three callers it is available and books two viewings. Wednesday, the negotiator finds two annoyed applicants and one booking she did not know about. Nothing malfunctioned: the assistant used the data it had. The fix is to stop treating availability as something the phone assistant knows. Remove availability statements from the knowledge base, require the "a negotiator will confirm" line, and where your system allows it, connect live listing status. A weekly export is not live data, and the assistant cannot tell the difference.

Rules for out-of-hours emergency calls on managed properties

If you manage lettings, one call type matters more than any other: a tenant reporting an emergency such as a leak, no heating in cold weather or a smell of gas. The assistant should not diagnose and should not give safety instructions beyond a line you have approved in advance, such as "if you believe there is immediate danger, contact the emergency services now". Then it routes to your out-of-hours contractor number or an on-call manager by live transfer, and falls back to an urgent text if nobody answers. Test this one thoroughly, because it is the call where a slow reply has real consequences. Document who is on call each week so the number it transfers to is staffed.

Timing the gap between a valuation call and the valuer's reply

For an agency, one measure matters more than call counts: how long a vendor or landlord waits between ending the call and hearing from a person. Log it for every valuation request in the first month, alongside what happened next. An illustrative first fortnight for the office above:

In this illustration the software did not change between the two weeks. What changed was that the branch manager moved valuation summaries from the shared inbox to the valuers' phones, and visits booked doubled. When requests grow but visits do not, look at the handover before you blame the assistant. If callers hang up before leaving details, shorten the question list. If the same query keeps appearing, such as parking or pet policy, put the answer on the listing and in the assistant's approved facts. Deciding what goes to a virtual assistant and what goes to AI helps if some of these calls turn out to need a human back-office person after all.

What sellers and tenants tell a recorded line

Callers to an agency volunteer more than the script asks for. A vendor explains that the sale follows a divorce or a death in the family; an applicant mentions debts; a landlord reads out a tenant's mobile number. None of that should be asked for, and very little of it belongs in a summary. Set two rules: the question list never asks why someone is selling or moving beyond the timescale, and when a caller volunteers personal circumstances, the summary records only "personal circumstances mentioned, negotiator to discuss" rather than the detail.

The recording still holds the detail, so limit who can open transcripts to the branch staff handling that property, and agree how quickly a recording is deleted when a caller asks. Before go-live, get the vendor's answers in writing on retention, deletion on request and whether calls are used to improve its models, and have the greeting say that the caller is speaking to an automated assistant on a recorded line. Applicant records the assistant creates carry the same data-protection duties as the ones your negotiators type.

Switching on one call type at a time

Rather than switching every call type on at once, add them in order of value and risk, and move to the next only after two weeks in which no summary needed correcting. Before the first stage, pull a month of call data and count the missed and after-hours calls, so you know which stage matters most to your office.

1. Valuation requests, evenings and weekends. The assistant captures the fields and texts the valuer; nobody is transferred. This is where missed calls cost most and the flow is simplest.
2. Viewing requests on listed properties. Still message-only, with the negotiator confirming availability and time.
3. Applicant registration. Only once your registration questions have been checked, since this is where an assistant is most tempted to improvise.
4. Live transfers for offers and existing clients. During staffed hours, once each negotiator has confirmed the number it rings.
5. Managed-property emergencies. Last, after the on-call rota has been tested end to end, because a failed transfer here has real consequences.

After each stage, decide whether to keep the plan, change tier or stop. If you would rather map the call flow and the handover rules with someone, my AI implementation consultation covers that; get in touch. And for a profession whose busiest weeks are set by a filing deadline rather than the property market, how an accounting firm scripts its phone for tax season makes a useful contrast.

Questions estate agency owners ask before switching on phone AI

Should the AI receptionist say whether a property is still available?

Only if it reads live data from your listings system. A stale answer books viewings on a property that is under offer and damages trust. Otherwise have it say a negotiator will confirm availability and take the caller's details and preferred viewing times.

Can it give a rough valuation over the phone?

It should not. A figure given by an assistant sounds like an agency opinion and can anchor a vendor's expectations. Have it collect the address, property details and reason for selling, then book a valuer's visit or pass the details on.

Will callers mind talking to an AI?

Many will not, if it is quick, honest about being automated and offers a person for anything involved. Say it is an automated assistant in the greeting, keep the questions few, and let any caller ask for a negotiator at any point.

How many calls does a small agency need to justify it?

Count missed and after-hours calls in your own phone log for four weeks. If you miss more than a handful of enquiries a week, even a plan under $150 a month can pay for itself with one extra instruction a year. If you miss almost none, wait.

What should never be left to the AI?

Offers, price negotiations, advice on a sale or purchase, anything about a specific chain or contract, and emergency repair calls on managed properties. These go to a person immediately, by live transfer or an urgent text.

Further reads

• Can an AI Chatbot Book Valuations for Estate Agents Out of Hours? — Booking valuations out of hours with a website chatbot.
• AI or Human Answering Service: Which Suits a Property Manager? — AI versus a human answering service for property managers.
• Real Estate Chatbot Pricing: What Agents Pay for AI Lead Capture — What agents pay for AI lead capture on the website.
• How to Write Call Scripts and Escalation Rules for an AI Receptionist — General method for call scripts and escalation rules.
• How Much Does an AI Receptionist Cost for a Small Business? — The general cost picture for any small business.
• How to Measure an AI Receptionist's Return in the First 90 Days — Judging the return in the first 90 days.
• AI Receptionist for Financial Advisers: Cost, Scripts and Limits — Cost from published plans, a never-say rule sheet with replacement wording, and identity-check and escalation rules for an advice firm's phone.
• ChatGPT for Estate Agents: Rules for Vendor Updates and Feedback — For the branch or brokerage owner: the rules, templates and fact checks that let agents use ChatGPT for vendor updates and viewing feedback safely.
• Material Information in Listings: What Estate Agents Must Capture — The Part A, B and C material information checklist for listings, and an AI workflow that chases the gaps without guessing.
• Sales Progression for Estate Agents: Chain Chasers With AI — A sales progressor's setup: chain tracker, AI-drafted chasers, milestone alerts and an escalation ladder that keep a property chain moving and clients informed.
• Can Estate Agents Be Found in AI Search? What to Fix Now — A fix list for estate agencies that want to appear when buyers and sellers ask AI for local agents, with a monthly check you can run yourself.
• Real Estate AI Chatbot Use Cases: Which Three to Start With — Build three narrow chatbot flows first, test the handovers and keep property claims and decisions with agents.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: EstateVoice, Smith.ai (AI and human plans), Rosie, Goodcall, Frontdesk and CloudTalk pricing pages, read October 2026 and rechecked 1 November 2026.