invextech

Case study

  • Real Estate

Regional Property GroupProperty enquiries were arriving from four places at once. None of them agreed with each other.

Portals, the website, phone calls and referrals each ended somewhere different. The work was not selling property. The work was finding out what had come in.

The challenge

Four intake routes, no shared record, and a team acting as the integration.

Enquiries reached the business through property portals, the website, direct calls and agent referrals. Each route landed in a different place, so the first job of every morning was reconciling them by hand into a spreadsheet. By the time an enquiry had an owner, hours had passed, and the person who eventually called had no idea whether a colleague had already spoken to them.

What it was costing

  • The same enquiry sometimes contacted twice, by two different agents
  • No reliable way to say which portal actually produced business
  • Follow-up depending entirely on whoever remembered
  • Reporting rebuilt by hand before every weekly meeting

Our approach

Fix the intake first. Everything downstream was a symptom of it.

  1. 01

    Make arrival the trigger

    Nothing should wait for a person to notice it. Every route into the business had to create the same record automatically, the moment it arrived.

  2. 02

    One record per enquiry, not one per channel

    The same buyer appearing through two portals had to resolve to a single record, otherwise the duplicate-contact problem would survive the rebuild.

  3. 03

    Let the team work the way they already did

    Agents were not going to adopt a system that was slower than the spreadsheet. The fastest path through the day had to be the one that recorded the data.

What we built

One intake, one record, routing that happens on arrival.

  1. 01

    Unified intake

    Every enquiry route now writes into the same CRM through a single capture layer, with the source attached to the record before anyone sees it.

    • Web forms
    • Portal feeds
    • Call tracking
    • Referral capture
  2. 02

    Matching and routing

    New enquiries are checked against existing records to catch repeat contacts, then assigned to an owner by territory and availability rules the team can edit.

    • Duplicate matching
    • Rule-based routing
    • Ownership rules
  3. 03

    Follow-up that continues

    Sequences run on a schedule after first contact, and a deal that goes quiet past a set threshold raises a reminder to its owner instead of simply ageing.

    • Automated sequences
    • Stall detection
    • Owner reminders

How it ran

Four phases, in this order.

  1. 01

    Traced real enquiries

    We followed a sample of recent enquiries from each of the four routes and timed what actually happened to them.

  2. 02

    Agreed the record

    Before configuration, we defined what one enquiry means, what makes it a duplicate, and what qualifies it.

  3. 03

    Built and ran in parallel

    The new intake ran alongside the spreadsheet on live enquiries so the team could compare before committing.

  4. 04

    Handed over with access

    Routing rules and sequence content were left editable by the team, with training on their own live pipeline.

The outcome

What the system does now that it did not before.

  • Every route creates a record automatically

    No enquiry depends on someone opening an inbox or checking a portal to exist in the system.

  • Each enquiry has an owner from the start

    Assignment happens on arrival by rules the team controls, rather than in a morning meeting.

  • Repeat contacts are caught before the call

    Matching runs against existing records, so two agents do not unknowingly work the same buyer.

  • Source is attached and stays attached

    The business can finally see which intake routes produce real conversations rather than volume.

On names and numbers. Client names are withheld and performance figures are not published here. Both belong to the client, and we share either only with their written approval.

Systems and technology

What this was built on.

  • 01

    Where it runs

    • CRM platform
    • Web forms
    • Portal integrations
  • 02

    How it connects

    • API integrations
    • Automation workflows
    • Call tracking
  • 03

    What the team uses

    • Pipeline views
    • Automated sequences
    • Owner notifications

Have a problem that looks like this?

Describe where work stalls in your business. We will tell you honestly whether this is the kind of thing we can help with.

Start that conversation