Skip to content
Our projects

Case studyReal estate sales follow-up

Automating prospect follow-up so no sales reminder is ever forgotten

An independent real estate agency centralises the enquiries it receives from listing portals, its website, Outlook and the phone. Each prospect is linked to the right property, assigned to a negotiator and given a next action, without enquiries scattering across mailboxes and personal notes.

  • Hektor
  • Property portals
  • Outlook
Three people look at a laptop around a wooden table
Company
Independent real estate agency with 8 staff
Volume
90 to 140 buyer and seller enquiries a month
Team
5 negotiators, 1 sales assistant and 2 directors
Tools involved
Hektor, property portals, Outlook and the website form

(01)Before the automation

Before: enquiries arrived quickly, but following them up depended on everyone staying alert

Buyer enquiries came from property portals, the website form, incoming calls and direct emails. Some concerned a specific property, others a broader search. Seller enquiries often came through the website or by phone, then were passed to whichever negotiator was available.

Portal emails landed in a shared mailbox, but each negotiator then kept their own notes. An enquiry could be copied into Hektor, stay in Outlook or be noted on a phone. Two negotiators could call the same prospect back, while another enquiry went unanswered after a first exchange.

The sales assistant regularly chased the team to find out whether a contact had been called back, whether a viewing had been offered or whether the project was still active. The directors knew how many enquiries came in, but not always the response time, the number of prospects with no next action or which channels actually produced listings or viewings.

(02)System put in place

Case study

After: each enquiry is linked to a property, an area and a responsible negotiator

The system centralises enquiries from the portals, the website and authorised Outlook mailboxes. It retrieves the prospect’s contact details, the property concerned, the source channel, the message, the type of project and, where the information exists, the budget, the area searched and the timeframe.

An assignment rule then names the responsible negotiator according to the property, the geographical area, the type of enquiry or the portfolio already handled. An enquiry tied to a specific listing goes to that property’s negotiator. A seller valuation goes to the person responsible for the area. In case of absence or overload, the assistant can reassign the file before contact is made.

The prospect is created or updated in Hektor with a dated next action. A buyer enquiry can trigger a callback within two hours, a viewing offer or a request for further information. After each exchange, the status is updated: to call back, viewing offered, viewing done, search ongoing, project postponed, out of scope or no answer.

(03)How the workflow runs

Case study

The workflow turns each incoming enquiry into a tracked sales file, without automating human qualification or the relationship with the prospect.

  1. 01

    Collect enquiries from the portals, the website and Outlook mailboxes

  2. 02

    Identify the property, the area and the type of project

  3. 03

    Standardise contact details and look for duplicates

  4. 04

    Assign the enquiry to the responsible negotiator

  5. 05

    Create or update the prospect in Hektor

  6. 06

    Schedule the callback, information request or viewing offer

  7. 07

    Update the status after each call, reply or viewing

  8. 08

    Flag prospects with no next action or no answer

What stays under human control

  • Actually qualifying the project and how mature it is
  • Assessing the prospect’s financing capacity and constraints
  • Choosing which properties to offer and preparing viewings
  • Handling negotiation and the sales relationship

Possible operational effects

  • Fewer enquiries forgotten in mailboxes
  • Clear assignment between negotiators
  • Callback times that are easier to track
  • Better visibility of prospects with no next action

(04)Example assignment rule

Case study

An enquiry received from a portal for a flat in central Bordeaux is linked to the listing concerned and assigned to the negotiator responsible for the property.

The system creates a callback within two hours and prepares the context for the contact: listing viewed, message, stated budget and contact details.

Portal enquiry → property identified → negotiator assigned → callback scheduled → status tracked in Hektor

If no property matches, if the contact already exists or if several negotiators could take the file, the enquiry goes into a validation queue for the sales assistant. The system does not choose arbitrarily when a rule does not allow a reliable assignment.

(05)Points to watch

Five things to keep an eye on.

  1. 01Assignment rules must take areas, listings and absences into account.
  2. 02Duplicate detection must match emails, phone numbers and existing enquiries.
  3. 03Scoring must not automatically rule out a prospect whose project deserves human qualification.
  4. 04Reminders must respect consent, the channel used and data protection rules.
  5. 05A prospect taken over manually by a negotiator must leave the automatic scenarios immediately.

Access rights, retention of exchanges, GDPR, error logging and recovery mechanisms must be suited to the tools actually connected.

(06)Conclusion of the case

Each enquiry becomes a visible sales action, not one more email in a shared mailbox

In this scenario, the agency replaces scattered follow-up with a shared flow for receiving, assigning and following up. Each prospect is linked to a property or an area and has a responsible negotiator and a dated next action, while qualification and the sales relationship remain entirely in the team’s hands.