Field notesARTICLE
Your Customer Wrote Something Your CRM Has No Field For
“Somewhere quiet, my mother has trouble with stairs.” No CRM has a field for that, and it is the whole reason the enquiry exists. What an assistant does with the part that does not fit.
Costa3 min read
Short answer
The important half of most enquiries is free text a CRM cannot store: a reason, a constraint, a worry. An assistant should carry that text forward verbatim rather than compress it into a dropdown, because the dropdown value is what the salesperson sees and the sentence is what closes the sale.
Key facts
- A CRM records what a request is; the message usually explains why, and that half has no field.
- The assistant keeps the original sentence attached to the record rather than replacing it with a category.
- Anything it could not classify goes to a person as written, not as a best guess.
- The rule is one line: never invent a value the customer did not give.
A property enquiry came in that read, in full: looking for two bedrooms, somewhere quiet, my mother is coming to live with us and she has trouble with stairs.
The CRM has a field for bedrooms. It has a field for budget, for area, for property type. It has no field for a mother who cannot manage stairs, and that sentence is the entire enquiry. Everything that will decide this sale — ground floor or a working lift, not above a bar, near a clinic — is in the half the form cannot hold.
What usually happens to that sentence
It gets thrown away. Someone reads the message, fills in bedrooms: 2, picks quiet from a dropdown that does not have it and settles for residential area, and the mother disappears. Two days later a broker sends four listings, three of them on the third floor without a lift, and the customer stops replying. Nobody records why.
That is not a CRM problem and it is not a people problem. It is that the structured fields are a summary, and somebody treated the summary as the record.
What it keeps
Two things, and the second one matters more than the first.
It fills the fields it can honestly fill — bedrooms, budget when given, area when given — and leaves the rest empty rather than approximating. An empty field is a known gap. A guessed one is a false fact that everybody downstream now believes.
And it keeps the sentence. The lead that reaches the broker carries 2 bedrooms at the top and, under it, the customer's own words, unedited, in the language they wrote them in. The broker reads nine words and knows to filter for a lift before they open a single listing.
The one thing it does ask about
Some things are not ambiguity to be preserved, they are questions to be asked. "Quiet" is one: quiet street, quiet building, or away from the tourist centre? That is one short question and it saves a viewing.
The rule underneath both behaviours is the same one line: never write a value the customer did not give. Ask, or hand it over as written. A confident wrong value in a CRM outlives the conversation that produced it and is believed by everyone who reads it afterwards.
Why this is the assistant's job and not the form's
You could add a field. Then the next enquiry says we have a large dog or I need to be able to see the sea from the kitchen or my husband works nights, and you are back where you started, one field richer.
Structure is for what you count. Sentences are for what you sell on. The useful thing EstateAI and OmniAI do here is not classification — it is refusing to lose the part that does not classify, on top of whatever CRM you already run.
The broker read nine words. No field would have held them.
Questions this raises
- Why not just add a field?
- Because the next customer will write something that does not fit that one either. Fields are for what you count. Sentences are for what you sell on, and the fix is to keep them, not to enumerate them.
- Does the assistant summarise the conversation?
- It attaches it. A summary is useful at the top; the transcript underneath is what stops a salesperson from re-asking a question the customer already answered at two in the morning.
- What if it guesses wrong about what the customer meant?
- It is built not to guess. An unclear request gets a short question, and an ambiguous one gets handed over with the ambiguity intact — a wrong value written confidently into a CRM is worse than an empty one.