Field notesARTICLE
The Listing Was Already Sold
A flat goes under contract on Thursday. Nobody updates the record until Monday. On Saturday at 22:40 someone asks about it, and the assistant answers from a system that is wrong.
Costa4 min read
Short answer
An assistant must never assert availability it cannot verify. It answers from the record while naming the record as its source, offers the nearest alternatives, and leaves the confirmation to a person — a confirmed viewing on a sold property costs you the customer, a hedged one costs a phone call.
Key facts
- Omni AI answers from the CRM already in use and does not keep a second copy of the truth.
- Availability is reported as the state of the record, not asserted as a fact about the world.
- A viewing is created as a request until a person confirms it.
- Anything the record cannot vouch for goes to the agent with the customer's message attached.
An enquiry arrives at 22:40 on a Saturday: two bedrooms, the one on the corner, can I see it this week.
The flat went under contract on Thursday. The agent who did the deal was driving when it happened, then it was Friday, then it was the weekend. The record still says available, and the record is the only thing the assistant can read.
This is not a problem an assistant creates. Every agency past four people has stale listings, and they had them when the only thing answering at 22:40 was nothing at all.
The answer that costs the most
"Yes, it's available — when would you like to view it?"
Now you have promised a specific flat, in writing, in a channel that can be screenshotted, to someone who was ready to spend Saturday night planning their week around it. On Monday somebody has to take it back. What the customer hears is not that your system was out of date. It is that you were careless with them, and they had already started imagining the place.
The second-worst answer is nothing until Monday, which costs you the enquiry but not the trust.
One clause, and what it changes
Every availability answer is phrased against the source rather than against the world. Not it's available but it's listed as available and I'll have the agent confirm first thing. Not I've booked you in for Tuesday but I've put Tuesday down and the agent confirms it in the morning.
That is one clause. It is also the entire difference between reporting a record and guaranteeing a fact, and it survives the case where the record is wrong. The rule underneath it is the same one that governs what the assistant writes into your CRM: never state something the system cannot vouch for.
The two minutes that keep the customer
A hedge on its own is a half-answer, and a half-answer at 22:40 loses to the agency down the road that sends three photographs.
So the same message carries the two closest listings — same area, same bracket, one of them with the lift the customer mentioned needing. If the corner flat is gone, the conversation is still alive on Monday morning. A stale record then costs you a viewing rather than a buyer, and that is a scale of damage a business can absorb every week.
Who finds out first now
Before, a listing sold on Thursday surfaced on Tuesday, when a broker phoned a seller and got an awkward pause. Now it surfaces at 22:41 on Saturday, in front of a customer.
Nothing got worse. The distance between the mistake and the person who pays for it went from four days to nine seconds, and stale data stopped being an internal inconvenience that everyone had learned to live with. Uncomfortable, and the correct direction — problems that are visible on Saturday night are the only ones that ever get fixed.
The Thursday nobody recorded
None of the repair work is in the assistant.
Status changes at the moment of the handshake, from a phone, in one tap, and the agent who does the deal owns that tap. Then one query on a schedule: listings that took enquiries this week and have not changed status in thirty days. That list is short, and it is where the next Saturday is hiding.
Omni AI sits on top of whatever you already run, which means it inherits whatever your records happen to be worth. It answers honestly about them, and it makes the gaps arrive early enough to be worth closing.
The corner flat was sold on Thursday. The only question a system can settle is how many people find out from you rather than from silence.
Questions this raises
- Can it check whether the listing is genuinely available?
- Only as far as your system knows. If the deal was signed on Thursday and entered on Monday, nothing on your side knows on Saturday — not a person, not software. That is exactly why the wording of the answer carries the weight.
- Doesn't hedging every answer make it sound unsure of itself?
- One clause, once. “It's listed as available, and I'll have the agent confirm first thing” reads as an agency that knows how its own process works. Three hedges in one message is a different problem.
- What if the customer wants to lock in a viewing right away?
- It takes the slot and says what the slot is — a request the agent confirms in the morning. The customer keeps their place in the diary and nobody has promised them a flat that is gone.