Lead routing and assignment in a brokerage: rules and records

What routing decides

Between capture and the first reply there is a gap, and in many offices it is filled by whoever sees the notification first. Routing closes that gap. When an enquiry arrives from a portal, a website form, a call or a walk-in, a routing rule picks an owner, starts a clock and says what happens if the clock runs out.

Routing is not scoring. Lead-management guides treat scoring as a numeric priority layered on a lead, which answers which lead first, while routing answers who gets it. The two are often sold together, but an office can fix routing without any scoring at all.^[7]

The same guides keep the stage of a lead (is it qualified?) apart from the stage of a deal once one exists. Mixing the two makes it hard to report how many enquiries become deals, which is why routing rules should act on the lead record and leave the deal pipeline alone.^[8]

The five common rule families

Routing guides written by software vendors and consultants describe the same handful of rules. They are vendor and consultant material, so treat them as a description of common practice rather than a standard.^[4][5]

The guides describe weighted rotation as giving, for example, a new hire half a share and a senior agent two shares, and capacity rules as capping the number of hot leads an agent holds at once, often at two or three. Those figures are examples from the guides, not recommendations.^[4][5]

Most real set-ups chain the rules. An example would be to match on area or language first, rotate among the agents who qualify, and skip anyone at their cap. In a Dubai office the useful questions are practical ones: who covers Friday evening, who speaks the buyer's language, and who handles off-plan enquiries.

Match the person before assigning the lead

A router that does not check for an existing client will hand the same buyer to a second agent. The material reviewed describes a matching step before assignment: compare the new enquiry with existing records, and if the person is already held, send the enquiry to the agent who holds the relationship with the history attached.^[4]

This matters for a brokerage because the same buyer often enquires on two portals about the same unit. Without a match step, two agents call the same person and neither knows. With one, the second enquiry becomes a note on an existing record.

The three parts that make routing work

The routing guides keep returning to the same three parts. Each is simple, and offices tend to skip them.

A fallback owner. Every rule can end in no eligible agent: everyone is away, on a viewing or at their cap. The material describes working-hours awareness and a defined fallback owner as what separates a robust router from one that silently drops leads.^[4] Name the fallback in advance for each day and hour, including weekends.

A timer and a reassignment rule. Each assignment starts a clock and sends the agent an alert. If nothing is recorded within the window, the lead moves to the next eligible agent or to a manager. The guides mention first-contact targets of a few hours, with tighter windows for hot leads, but the window is configuration, not law.^[4][5] Choose one your office can actually staff, because a timer nobody can meet teaches people to ignore it.

A log. Record every assignment and reassignment with the time, the recipient and the reason. The material describes this as an audit trail for fairness and coaching.^[4] It answers the arguments routing creates, such as who received how many leads, who let one expire and which source brings enquiries that nobody picks up.

Portals, webhooks and repeated events

In Dubai most enquiries arrive through the two large portals. Property Finder publishes an enterprise API reference and, as described in its documentation, announces events such as a lead being created or assigned through webhooks that are delivered at least once.^[6] At-least-once delivery means the same event can arrive twice.

A CRM built for this has to check an event identifier and ignore repeats, otherwise one enquiry can create two leads and two assignments. If you are comparing software, ask the vendor to explain how it handles a repeated event. A clear answer is a good sign, and a vague one is worth pressing.

Portals also keep their own measures of how quickly you respond, whether or not your CRM records it. Recording the first reply time per lead and per channel in your own system lets you compare it with what the portals show. This guide did not find a published weight for response time in either portal's listing placement, so treat any claim about that effect as unconfirmed.

What the research says about speed

The most cited source is a short Harvard Business Review article from March 2011. The authors audited 2,241 US companies by sending each a web-generated test lead. About 37% responded within an hour, 24% took more than 24 hours and 23% never responded. Among companies that replied within 30 days, the average response time was 42 hours.^[1]

The article also refers to a separate study of 1.25 million leads, in which firms that tried to contact a lead within an hour were nearly seven times as likely to qualify it as firms that tried an hour later. The authors define qualifying as a meaningful conversation with a key decision maker. That is an early step, not a sale, and the comparison is between groups of firms, so faster firms may differ in other ways.^[1]

The same article lists reasons for slow replies that read like routing problems: leads collected from the CRM daily rather than continuously, sales staff busy generating their own leads, and rules for distributing leads among agents and partners based on geography and fairness.^[1] A 2013 Journal of Marketing study puts a different number on the follow-up problem. It describes a sales lead black hole, the 70% of marketing-generated leads that sales representatives do not pursue, and links follow-up to prequalification, managerial tracking and the experience of the rep.^[2]

A 2025 Journal of Marketing study on automated lead nurturing found that the average effect on conversion ranged from none to 23 percentage points, depending on sales cycle length, expected sales volume and any existing relationship with the seller.^[3] None of these sources tests a particular CRM or studies UAE real estate, and none reports a controlled experiment on response time. The fair reading is that a slow or missing first reply is a plausible place to lose enquiries, and that measuring your own is the cheapest first step. No source opened for this guide supports a particular number of minutes for Dubai.

A first version before any software

An office can test its routing in a week with a shared sheet.

• List each lead source, and for each one who is on duty for every day and hour, including Friday and weekends.
• Choose one rule per source in plain words, and one fallback owner.
• Set a response window the office can staff, and decide who receives a lead that misses it.
• Log every enquiry with its arrival time, its owner and its first reply time.
• After four weeks, read the log: which source waits longest and which agent holds the most expired leads.

Then decide whether software is the next step. The Works CRM, which The Works Group sells and which is still in build, has separate routing for each of nine lead sources, counted from the product's code on 6 October 2026.^[9] It is one option among several, and your own list from the steps above is the best test for comparing any of them.

Questions