leads routed by the map, not the inbox
A brokerage that works across a city does not sell one project — it sells wherever the buyer wants to live. The useful question is not "which unit" but "which micro-market, and who on the desk owns it". Metrik runs that first conversation and hands the lead to the person who actually knows the area.
inside the call
metrikAap kaunse area mein dekh rahe hain?
leadBaner preferred, but Wakad bhi chalega if the price is right.
metrikNoted — Baner first preference, Wakad backup. Ready possession chahiye ya under-construction bhi consider karenge?
leadReady hi chahiye, shifting jaldi karni hai.
sample conversation · hinglish · not a customer recording
the challenge
Location arrives as free text and leaves as free text. "Somewhere near the expressway", "Baner ya uske aas-paas", "wherever is good for schools" — all of it ends up in a notes field that no assignment rule can read, so leads get distributed by whoever is free rather than by who knows the market.
The cost of that shows up on the second call. A salesperson who does not work that micro-market cannot answer the follow-up questions, so the lead repeats their requirement to a second person and starts losing patience with the firm rather than with the process.
the strategy
The agent treats location as a first-class requirement instead of a note. It asks for preference and flexibility separately, keeps both, and resolves loose phrasing into the areas the desk actually organises itself around.
Budget, configuration, possession and timeline are collected in the same pass, because a location without a budget is not routable — it is just a pin on a map.
reading a location
People describe where they want to live relationally: near an office, near a school, near family, near a road they already drive. The agent accepts that and then asks the one clarifying question that turns it into something a desk can act on.
Preference and fallback are kept apart. A lead who says "Baner, but Wakad if the price is right" has told you two different things, and collapsing them into one field throws away the part that makes the lead workable.
the requirement
The same structured fields as every other Metrik deployment — configuration, budget band, possession preference, buying timeline, purchase intent and site-visit interest — so a location desk and a project desk are looking at the same shape of lead.
That consistency is what makes the requirement comparable. A desk can ask "who is looking for a ready 3BHK under a crore in Baner this month" and get an answer, rather than opening twenty call notes.
routing by market
Location logic maps the captured area onto the desk's own coverage, and assignment logic picks the owner within it. If the preference and the fallback belong to different owners, the rules decide which one takes it rather than leaving it to whoever refreshes their inbox first.
The handoff carries both areas, the budget band and the possession requirement, so the salesperson opens the conversation already knowing what to offer.
outcome
Leads reach the person who knows the streets they asked about, with the requirement already written down. The second conversation starts where the first one ended instead of starting again.
Where the routing rules sent a lead, and why, stays visible next to the transcript.