The first enquiry came in eighteen months ago. It went nowhere. Now the same address is in the inbox again. The instinct is to reach for the CRM record, treat the new enquiry as a continuation of the old one, and assume low urgency because the last contact did not convert. That assumption loses instructions that were there to be won.
The repeat address problem
Properties appear in agency pipelines more than once for reasons that are completely unrelated to the first contact. A property that was tentatively explored two years ago by an owner who decided not to sell may now be enquiring because that owner has retired, separated, been made redundant, or inherited a second property. The address is the same. The seller's situation is entirely different.
In some cases the property has changed hands. A buyer who purchased the property at auction is now a seller. A property left in an estate has passed to a new owner who is assessing their options. The CRM record from the previous contact is not just unhelpful. It is actively misleading.
What drives a second enquiry
Second enquiries from the same address are almost always driven by a life event that has changed the seller's position since the first contact. The most common triggers are remarriage or new partnership, where combined property ownership requires rationalisation. Retirement, where the property no longer fits the life stage. Upsizing driven by a growing family or new financial position. Downsizing following children leaving home.
In each case, the instruction likelihood of the second enquiry has no relationship to what the first enquiry produced. The seller is making a new decision from a new position. The only thing they share with the previous contact is a postcode.
Why the context resets
The signals that determine instruction likelihood exist in the current enquiry, not in the history of the address. A seller who is downsizing following retirement and has a defined timeline is an imminent instructing seller regardless of whether that address produced a cold contact eighteen months ago.
Reading the current enquiry on its own terms means extracting the signals it actually contains: the motivation described, the timeline mentioned, the urgency or absence of urgency in the language. Those signals are the input. The address history is not.
The CRM trap
CRM systems store historical contact data against addresses and names. That data is useful for understanding what has been discussed before and avoiding duplication of effort. It is not useful as a proxy for current instruction likelihood.
The trap is treating a CRM record as intelligence. A record shows what happened. It does not show what the seller's current position is, what has changed in their life, or how close they are to instructing today. Agencies that use historical records to deprioritise current enquiries are making a classification error before they have read what the seller actually said.
What this means at intake
Every enquiry from a known address should be assessed on its own signals at the point of arrival. The presence of a prior record is context, not a classification. If the current enquiry contains strong instruction signals, it should be treated as a high-priority contact regardless of what the address has produced before.
The seller who enquired eighteen months ago and went cold was at a different stage of a different decision. The seller in the inbox today may be ready to instruct within the month. The only way to know is to read what they sent rather than what the database says about them.