Real estate customer insights: finding main concerns in conversations

Short answer

To find real estate customers' main concerns, five or six fields extracted from conversations are enough: the project or area of interest, property type and number of rooms, budget range, payment method (cash, mortgage, instalments), purchase purpose (to live in, investment, to rent out) and main objection (price, location, handover date, mortgage terms, trust in the construction). The cross-tabs between these fields — for example, project × objection — are the most valuable insight for a developer or agency.

In real estate the sales cycle is long, and a customer writes, calls and visits several times. That makes conversation analytics especially useful here: when a decision takes weeks, it shows which question the customer is stuck on.

Why conversations are especially valuable here

Buying property is a big, rare decision. Customers ask many questions: payment plan, documents, handover date, infrastructure, schools and transport. Those questions reveal their real concerns. The CRM usually holds only an "interested" or "visited" status. Fields extracted from conversations answer "why haven't they decided yet?"

Recommended fields

1. 1Project or area of interestA closed list: real project or area names plus "other". Do not replace the list with one generic value — each project must be its own value, or the cross-tab shows nothing.
2. 2Property type and roomsFlat, house, commercial; 1–4+ rooms, "unknown".
3. 3Budget range4–5 ranges suited to your market, plus "unknown".
4. 4Payment methodCash, mortgage, instalments, undecided.
5. 5Purchase purposeTo live in, investment, to rent out, for a child, other.
6. 6Main objectionPrice, location, handover date, mortgage terms, trust in construction, documents, other.

The most useful cross-tabs

• Project × objection: what customers hesitate about in each project — price, handover, location.
• Budget × property type: which segment demand is in, and whether your offer fits it.
• Payment method × objection: is the main problem for mortgage seekers the rate, the down payment or the documents?
• Purchase purpose × project: which project investors are interested in, and which families.

Typical concerns and what they mean

1. 1Handover dateThe most common concern in projects under construction. In a market with a history of delays, it is a trust issue.
2. 2Mortgage termsRate, down payment, bank requirements. Customers do not know they need to ask the bank, not the developer.
3. 3Location and infrastructureSchools, transport, shops, parks — especially for families.
4. 4Price and hidden costsRenovation, utilities and service charges on top of the price per square metre.
5. 5DocumentsTitle extract, registration, ownership — a matter of trust.

Conversations after a viewing

The most valuable conversations often come after a viewing: the customer has seen the flat and now asks concrete questions — "the kitchen is small", "the window faces the road", "when will the next block be finished?". Analyse these conversations as a separate segment. Objections before a viewing are about ads and presentation; those after it are about the product itself: layout, view, build quality. The latter feed directly into a developer's project decisions and can inform the planning of the next project.

Season and campaigns

Property demand is sensitive to season, interest-rate changes and campaigns. A new project's sales launch, a change in mortgage terms or a holiday campaign shifts the conversation mix sharply. Mark these events on the trend chart so you do not read a campaign's temporary interest as lasting demand.

Illustrative example

This is an illustrative example. A developer is selling two projects at the same time. The project × objection cross-tab shows the main objection for the city-centre project is price, while for the suburban one it is transport and schools. The budget field shows most of those interested in the suburban project are families planning to pay with a mortgage.

Decisions: school and shuttle-bus information is added to the suburban project's ads, the sales team gets a ready answer on mortgage terms, and an instalment plan is tested for the city-centre project.

Agency vs developer

A developer looks for insight about its own projects: which project, which objection, which floor and layout. An agency looks at the market: which area, budget and type customers want, and what is missing from its portfolio. For an agency, the "asked for but we don't have" field is especially valuable — which area and budget have no offer.

Working with individual leads

Beyond aggregate insight, the fields help with individual leads too: a sales manager sees the customer's budget, room count and main objection without rereading the conversation. But this is only what the customer said. Estimating a customer's income or ability to pay and treating them differently because of it is wrong.

Typical mistakes

• Building the project list with a single generic value.
• Leaving "unknown" out of the budget field — most customers do not state a budget.
• Treating campaign-period interest as lasting demand.
• Not recording mortgage questions as something the developer cannot answer.

Limits

• Conversations only see customers who contact you; they do not show overall market demand.
• The budget a customer states is not always their real ability to pay.
• On mortgage and legal questions, only a bank or a lawyer can give the customer exact terms.

Real estate fields in Vexvon

In Vexvon the company sets up fields such as project, property type, rooms, budget, payment method, purpose and objection in its own panel; AI picks from the list using the customer's words in each conversation and keeps the sentence as evidence. The panel's AI assistant gives cross-tabs such as "project × objection" by conversation count and can show a list of customers matching a condition. Conversations sit alongside the lead record in the CRM. More: analytics and CRM.

Next step

Read the conversations of 30 leads from the last two months who did not come to a viewing, and write down the project and main objection for each. For the general objection map method, see sales objection analysis; for call quality, real estate call QA. We can set up the fields together in a demo.

Further reading on this topic: price objection analysis, customer demand trends.