Lead routing by postal code and area

Geographic routing is the most intuitive lead-distribution rule a team can run: the Etobicoke lead goes to the agent who works Etobicoke. It is also the rule most teams implement as tribal knowledge — “that’s Priya’s area” — which works until the night lead arrives, the borders blur, or Priya goes on vacation. Making area routing real means making it data: defined territories, a location signal on every lead, and a written answer for the gaps.

Route on FSAs, not on vibes

American playbooks talk zip codes; the Canadian unit is the FSA — the first three characters of the postal code. Define each territory as a list of FSAs plus, where your market needs finer grain, named communities within them. This gives you boundaries a CRM rule can evaluate, instead of boundaries that live in the team lead’s head. Keep territories few and coarse at first: a five-agent team slicing a city into thirty micro-zones has built an administration problem, not a routing system.

Where the location signal comes from

A routing rule is only as good as the location on the lead, and the best signal is behavioural. A lead who registered while viewing a listing carries that listing’s location; a lead who asked about a specific property is telling you exactly where they are shopping. On BrokerFold, captured leads carry the listing and search context they came from, so an area rule has something concrete to evaluate the moment the lead lands. Form-fill address fields, by contrast, are sparse and often junk — treat them as a tiebreaker, not the primary key.

The three gaps every geographic system must close

The uncovered area. Leads from outside every territory need a default — usually rotation across the whole roster, as covered in round robin vs shark tank. Never let the map’s edges become a lead graveyard. The absent owner. Territory ownership must have an availability condition: if the area agent doesn’t act within your claim window, the lead escalates to the team pool. A territory is a first right, not a warehouse. The double-coverage zone. Where two agents legitimately work the same ground, write the sharing rule down — alternating assignment, or a split by price band. The wider set of recipes lives in our lead routing rules pillar.

Keep fairness measurable

Geography is not evenly rich. One agent’s FSAs may produce triple the leads of another’s, and a system that ignores this breeds quiet exits. Review quarterly: leads per territory, contact and appointment rates per territory, and revenue per territory. Rebalance by moving FSAs, not by making exceptions per lead — exceptions are how a routing system dies. If one area consistently overwhelms its owner, that is a recruiting signal as much as a routing one.

Sign calls and farming still follow the map

Area routing shouldn’t stop at web leads. Sign calls, open-house walk-ins and geographic farming all touch the same map, and running them on different mental maps guarantees conflict — the agent farming a neighbourhood for a year has a reasonable expectation about its sign calls. Fold all of it into one territory definition, reviewed on one schedule; the operational detail is in territory management for teams. The routing engine itself — rules evaluated at capture, assignment to a seat, escalation timers — is precisely the layer BrokerFold’s lead routing runs for you; the map, and the fairness review behind it, stay yours.

Start coarse, earn granularity

If you are introducing geographic routing to a team that has never had it, resist launching the full map on day one. Begin with two or three broad zones built around where your agents already demonstrably work, run a month, and measure whether area-matched leads actually convert better for you — they usually do, but your own evidence buys the roster’s trust in the system. Granularity is a reward for a working model, not a starting requirement, and every boundary you add is one more edge case the rules must cover.