Skip to content
Expert scenario

Stop losing enquiries at the door and bring the people who actually buy through to a viewing.

Agencies and developers: inbound enquiries, qualification, viewings, property matching, deal support, working the contact database.

An agent hands keys to a couple across a meeting table, with documents beside them.

Key constraints

  • a decision matures over months, while an enquiry needs an answer within the hour

  • one lost buyer costs more than a manager's monthly salary

  • the contact database accumulates for years and is barely used

Industry economics

  • The commission on a single deal covers months of operating costs — which makes a lost enquiry disproportionately expensive.

  • A manager busy with unqualified enquiries is not working with the people ready to buy.

  • A contact database nobody works is marketing already paid for and left idle.

Typical processes and pains

  • Symptom

    Enquiries arrive around the clock and are handled in office hours.

    Economic consequence

    Evening and weekend enquiries go cold, and the buyer goes to whoever answered.

    What share of your enquiries arrives outside working hours?

  • Symptom

    Buyer qualification depends on the individual manager's experience.

    Economic consequence

    Viewing time goes into enquiries that were never going to convert.

  • Symptom

    The old contact database is never worked.

    Economic consequence

    Customers who postponed a purchase for a year come back to the competitor who reminded them.

Priority AI scenarios

Answer enquiries outside working hours

  1. 1Parse the enquiry
  2. 2ask clarifying questions by the rules
  3. 3match properties
  4. 4a morning task for the manager with the context ready
Inputs
Enquiries from forms, messengers and listing sites, the property database, qualification rules.
Output
An immediate reply to the customer and a record with clarified parameters and matched properties.
Where the human stays
Deal terms and price are confirmed by a manager; the system does not negotiate and promises no discounts.
Integrations
CRM, the property database, messengers, telephony
Metrics
Time to first response, share of enquiries reaching a viewing, conversion by channel.
Limitations
If the property database is not readable, matching will be approximate and will need manual checking.

Bring postponed enquiries back into play

  1. 1Match past requests to new properties
  2. 2select matches
  3. 3send an offer
  4. 4create a task for the manager
Inputs
Enquiry history, loss reasons, search parameters, new properties in the database.
Output
A list of postponed enquiries for which a suitable property has appeared.
Where the human stays
Contact frequency is capped by a rule; the manager decides whether to call — the system only supplies the grounds.
Integrations
CRM, the property database, messengers and e-mail
Metrics
Share of enquiries revived, database-to-viewing conversion, cost per deal from the database versus a new enquiry.
Limitations
Past request parameters are often unrecorded: without them matching relies on correspondence and is rougher.

Where teams usually start

This is an observation across similar companies, not a universal recommendation: the order follows where your bottleneck actually is.
  1. 1Out-of-hours response is the usual start: that is where most is lost and the effect is immediate.
  2. 2Qualification comes next, so viewings go to buyers who convert.
  3. 3Working the old base comes last: it needs enquiry history in a usable form.
  4. 4The order follows where your buyer is lost.

Industry systems and data

  • CRM
  • the property database
  • listing sites
  • messengers
  • telephony
  • document storage

Risks and constraints

  • A buyer leaves a phone number for one property: on what grounds and how often they may be contacted afterwards is settled before launch, not after the first mailout.

  • The property database must be readable, or matching will diverge from actual availability.

  • Adoption: managers won't work tasks from the database if they can't see the reasoning behind them.

  • Enquiry history is often incomplete — then postponed-enquiry work is limited to correspondence.

Frequently asked questions

Won't an answer that is not from a person put buyers off?

What puts buyers off is not an automated reply but its content: pretending to be a person and selling in the first message. The opposite works — quickly clarify the parameters, show suitable properties and say plainly that a manager will call in the morning. We write that boundary into the rules before launch.

There are thousands of old contacts in the database. Where do we start?

With the ones whose search parameters were recorded: matching there is precise and the result shows within weeks. The rest are handled later and rely on correspondence, which produces more noise. We estimate the usable share on your own database before the work starts.

Let's work through one workflow in real estate

Thirty to forty-five minutes on your specific case. If it isn't a fit, we'll say so on the call.