How an AI Receptionist Works for a Real Estate Team

Enquiry volume from portals and listings

Portal traffic is lumpy. A fresh listing, a price drop, or a weekend push produces a burst of short calls from people who have the reference in front of them. Mid-week late morning is often quieter. You do not need a survey to notice this: your call log already shows clusters after 18:00 and on Fridays in the GCC, and after work hours in Indian metros, because that is when people browse on their phones.

Those callers often have the listing ID, the building name, or a screenshot. They will not wait in a long IVR. They will also not repeat their story to a second agent tomorrow if the first call died in voicemail. Speed-to-lead on this channel is not a slogan; it is whether a viewing slot or a callback exists before they ring the next advert.

Signboards and WhatsApp clicks add a second pattern: withheld numbers, “I am downstairs now”, and people who think the number on the board is the owner. Your script needs a branch for walk-up and for “is this still available”, not only for “book me Saturday”.

WhatsApp and voice are not the same queue. A caller who already chatted on the listing ad may ring to skip the chat bot. If your CRM does not match CLI to the WhatsApp thread, the agent gets two tasks that look like two people. Match on phone number before create. If the WhatsApp lead is owned by another agent, do not silently reassign because the voice path has a different round-robin — flag a duplicate for a person.

Off-plan versus ready: the qualification questions diverge. Off-plan callers ask about handover dates, payment plans, and the developer. Ready stock asks about keys, furniture, and viewing today. If the listing type is off-plan, do not offer a “viewing this weekend” unless there is a real show apartment on the calendar. If you cannot tell the type from the reference, ask once, then route. Mixing them produces no-shows at buildings that do not exist yet.

Qualification: buyers versus tenants

Ask buy versus rent in the first exchange if the listing type is not already known from the DID or the portal reference. Mixing them in one pipeline is how a rental hunter is sent a mortgage pack.

Buyers you can usefully ask, if they will answer: area or building, bedroom count, whether they are ready to view this week, and whether they are already working with another agency. Budget is useful and often refused on a first call — record “not given” rather than guessing. Mortgage versus cash is an agent question unless you have a published process for it.

Tenants: move-in window, household size at a high level (not a census), whether they need the unit furnished, and whether they have a visa or employment situation they wish to mention. Do not interrogate income on a bot call. Do not take a holding deposit on the phone. Cheques, Ejari, and tenancy contract terms belong to a person.

Both: listing reference if they have it, name, callback number read back, language they prefer for the viewing. Stop there if they want to negotiate, complain about a landlord, or say they have already paid someone.

Viewing scheduling and agent routing

A viewing is a calendar event plus a person with keys. Software may offer slots only from a calendar that is true: the listing agent’s viewing blocks, a shared viewing rota, or published open-house times. If keys are held by a colleague who is not on that calendar, you will book ghosts.

Routing logic should be deterministic. Prefer: the listing’s nominated agent; if they are marked off-shift, the duty agent for that area; if the caller asks for a named person, that person. Round-robin is fine for unassigned inbound numbers, not for a listing that already has an owner. Write the owner at create time so two notifications do not fire.

Warm transfer during business hours if the agent’s phone is the culture of the team. After a short ring, fall back to the booked slot plus SMS, not to silence. Blind-transferring a qualified buyer into a silent mobile is how portals get a second call to a competitor.

Area specialists versus listing owners: if Fatima owns MR-4418 but the caller also asks about three other buildings she does not cover, do not auto-assign those extra buildings to her. Capture them as additional listing IDs on the same enquiry and let a person split or keep. Auto-creating three leads from one call is how the floor starts fighting.

Language on the viewing: if the caller booked in Hindi, the confirmation and the agent’s first SMS should not switch to English by default. Store preferred_language. An agent who cannot take that viewing should decline in the calendar so the bot never offered a slot they cannot honour.

Out-of-hours enquiries

After hours, do not pretend the agent is in the lobby. Offer the next published viewing window, take a structured message, and set a first-action time the duty agent already agreed (for example: first hour of the next working morning). If someone is downstairs at the building at 21:30, the honest answer is that a viewing cannot be invented; offer the next slot and capture the location so the agent knows it was a walk-up.

Emergencies are not portal leads: fire, flood, a tenant locked out who is already your client. Those should match a phrase list and hunt the property-management or on-call number, not create a “hot buyer” task.

Duty-agent rotas fail when they exist only in someone’s head. If Saturday cover is “whoever is free”, the bot cannot route. Publish a weekly rota into the same calendar the viewing slots use, even if it is a simple all-day busy block on everyone except the duty name. Without that, after-hours capture becomes a shared inbox nobody wants, and the Monday pile is stale.

Time zones are not decorative. A caller in Riyadh booking a Dubai viewing, or a NRI calling from another country, will hear “Saturday 11:00” and mean a different clock. State the zone in the recap and in the SMS. Store the viewing in one zone (the property’s city) and never in the agent’s laptop local time.

What should be written to CRM, and in what shape

One contact, one deal or enquiry object, one listing ID. Fields that earn their keep: full name; phone as confirmed; buy or rent; listing reference or building; bedroom count if given; budget or “not given”; viewing datetime or “callback requested”; source (portal name if you know it from the DID, else inbound_voice); owner agent; outcome (viewing_booked, callback, transferred, unavailable_listing, out_of_scope).

Put the transcript behind a link. Do not paste a wall of text into a notes field that syncs to WhatsApp groups. The summary should mention the listing and the next step, not a personality sketch. If the same CLI calls twice in a day, update the existing enquiry; a second lead is how two agents collide.

Portal source should be a field, not a guess in the notes. If each portal has its own tracking DID, map DID → source in a table the bot cannot freestyle. If everyone shares one number, ask “which site did you see this on” once, then store the answer as they said it. Agents argue about attribution arguments; a structured field ends more of them than a transcript.

Viewing events need a reminder task and a no-show outcome. If Saturday 11:00 passes with no update, the enquiry should not stay viewing_booked forever. A nightly pass — even a human looking at a list — that marks no_show or completed keeps the pipeline honest. Software that only writes at call time will rot by Monday.

When the property is already gone

Portals lag. Signboards lag. The worst sentence software can say is “I can book you a viewing” against a status of sold, let, or withdrawn. The listing store the bot reads must be the same status the team uses, or the bot must be told “if status is not available, do not offer a viewing”.

Honest path: say the specific unit is no longer available, offer to take criteria for something similar, and create an enquiry with listing_status = unavailable and a similar-search task for the agent. Do not quote a price from a cached advert. Do not book the empty slot in the building next door unless that listing is actually for let or sale and the caller agreed to switch.

If the caller says they already paid a deposit on this unit, transfer. That is a dispute, not a new lead.

Similar-unit offers need constraints: same area or building, same buy/rent, overlapping bedroom count, status available. Offer at most a short list, and only if the caller said they still want to look. Dumping eight random units is a portal, not a receptionist. If you have no similar available stock, take the criteria and stop. Honesty here is how you get the callback when the next unit hits the market; a fake viewing is how you get a one-star story about the board that was still up.

Worked example: portal call through to a booked viewing

Team: a small agency in Dubai Marina. Listing: two-bed to rent, reference MR-4418, status available, owner agent Fatima, viewing calendar has Saturday 11:00 and Sunday 17:00. Inbound DID is the portal tracking number for that advert.

CRM write: Contact Rohan Mehta, phone = confirmed CLI, type = rent, listing = MR-4418, status available, move_in = end of next month, viewing = Saturday 11:00 Asia/Dubai, owner = Fatima, outcome = viewing_booked, source = portal_did. Task on Fatima: confirm keys. If status had been let, the system would have skipped the slot question, said the unit was no longer available, and opened similar_search instead of a viewing.

What goes wrong

• Stale status: viewing booked on a unit let yesterday because the portal feed was not the CRM status.
• Two owners: listing agent and duty agent both get a push because the record was written twice.
• Wrong CLI: callback rings the office DID; Rohan is lost.
• Keys not on the calendar: Saturday 11:00 is booked, Fatima is in Abu Dhabi, nobody has the bunch.
• Buyer script on a landlord cheque call: the caller is furious and the CRM says “hot lead”.
• After-hours “come now” accepted as a viewing: the caller waits in a lobby that is closed.

What this does not solve

It will not make agents follow up. It will not refresh a portal that your listings coordinator does not update. It will not hold a tenancy deposit or give legal advice on a contract. It will not stop a caller who wants the owner’s private number. If your real problem is that listings have no owner, assign owners before you connect the public DID.

Frequently asked questions

Monarc Voice is an AI receptionist in development, including for teams who take portal calls on a business number. It is not launched, and it is not a listings CRM.