Discarding candidates in matching with a reason: how to fine-tune your buyer list

A property goes on your books and matching returns twelve compatible buyers. You call the first three: one already bought elsewhere, another likes the flat but not that orientation, the third does not pick up. Two weeks later you open the same list and all twelve are still there, including those three. If you do not write down why a candidate does not work, the list asks you the same thing every time you look at it.

To filter buyers by property in real estate matching, the practical approach is to discard each candidate who does not fit and give a reason, so they drop off that property's list without being deleted from the CRM. In RealEstateCRM discarding is done with a reason and can be undone: the buyer stays in your contact base and you can restore them if circumstances change.

Why the percentage is not enough

The compatibility percentage, from 0 to 100, comes from crossing area, price, size, bedrooms and property type. It is a good first ordering, but it does not know what you know after talking to the client. A 92% might be a buyer who already viewed the flat and turned it down because of street noise, and the file has no field for that. The system puts them back on top because the numbers still match.

This is where discarding adds something the algorithm cannot: information that only exists in a conversation. You discard, type the reason in one sentence ("viewed it, says it is too dark") and that candidate stops competing for your attention on that property.

Writing the reason matters more than it seems

It is tempting to discard without a note just to tidy the list, and it works on day one. The trouble comes a month later, when a colleague opens the property and wonders why a buyer at 88% is missing. With a reason, the answer is right there. Without one, somebody ends up phoning the same client again, who already said no.

It helps you too. If after a few months you notice most discards in one area say "price", maybe the problem is not the buyer list but the asking price. A written reason is, without you planning it, a small piece of market data from your own portfolio.

Restoring a discarded buyer when things change

Discarding is not burying. A buyer who rejected a flat on price may come back when the owner drops 15,000 euros, or when they raise their own budget after selling. Because the CRM lets you restore candidates, you do not have to hunt for them or remember their name: you bring them back and they return to that property's list.

On top of that, the percentage is recalculated when the property or the buyer's criteria change. If you lower the property price and one of the candidates you had set aside now falls within range, you have a good reason to review that file's discarded buyers before calling the list exhausted. Remember that below 60% compatibility the match is not even shown, so what you discard is always people who, on paper, did fit.

A case: a penthouse in Pontevedra and nine candidates

An agency lists a 285,000 euro penthouse in central Pontevedra and matching suggests nine buyers. Before the first call, the agent discards two she has already spoken to that week: one bought another home and the other is looking for something without a terrace. She phones four more, and three drop out with a reason: two on price and one who prefers a ground floor with a garden. Three live buyers remain, and those get her morning of viewings.

A month later the owner agrees to drop to 265,000 euros. She opens the discarded list, restores the two who left over price, and the list has five names worth a call again. She did not have to rebuild anything from memory.

If you want to see how each percentage is calculated before you start discarding, we explain it in how matching scoring works. The rest of the module's tools are in the CRM features, and if your follow-up depends on not losing anyone along the way, it is worth reading why real estate leads get lost. RealEstateCRM keeps the why behind every discard so the next person to open the property does not start from zero.