Lead routing rules by budget, city and language: examples, pitfalls and how to test them
How to route leads to the right agent by budget, city and language: five example rules, the pitfalls that break them, and how to test before going live.
Round-robin is a fair default. Add routing rules only where a real mismatch costs you sales: big budgets, specific cities, or customers who write in Arabic. Order rules from specific to general, plan for missing data, and test every rule with sample leads before it touches a real one.
Round-robin gives every agent a fair share of leads, and for most teams it is the right place to start. Then a few things happen. A buyer with a PKR 3 crore budget lands on the newest agent in the office. A Lahore enquiry goes to someone who only covers Karachi. A customer writing in Arabic is handed to an agent who cannot read it. Each of these is a lead you paid for and may now lose.
Routing rules fix this by letting the lead's own details decide who gets it. This guide covers when to use them, five examples you can copy, the mistakes that break them, and how to test them before a real lead goes through.
When rules help, and when they do not
Start with plain round-robin and look at what goes wrong over two or three weeks. Add a rule only when you can name the cost.
| Problem you see | Rule that helps |
|---|---|
| Large enquiries handled by inexperienced agents | Route by budget |
| Agents travelling to the wrong city | Route by city |
| Customers writing in a language the agent does not speak | Route by language |
| Some ad channels need a fast phone call, others a chat | Route by channel or source |
| Nobody covers late evenings | Route by time of day |
If you cannot name a problem, you do not need the rule. Every extra rule is one more thing someone must remember to update when a team changes.
Five example rules
These use Pakistani and Gulf examples. Change the numbers and names for your own market.
- Large budgets to senior agents. Budget more than PKR 5 crore, or more than AED 3 million, goes to your senior team.
- Small budgets to a junior team. Budget less than PKR 50 lac goes to newer agents, who get volume and practice.
- City to the local team. Leads mentioning Lahore go to the Lahore team, Karachi leads to the Karachi team.
- Arabic to Arabic speakers. Leads whose first message is in Arabic go to agents who speak it. A Roman Urdu rule can send Roman Urdu enquiries to agents comfortable in it.
- Late evening to the on-duty agent. Leads arriving between 9 pm and 1 am go to the agent covering the evening shift.
Rules can also combine conditions. "Lahore and more than PKR 2 crore" is stricter than either alone, and is usually what you really mean.
How rules are evaluated
Most systems, including BrokLeads, try rules from top to bottom and stop at the first one that matches. That has two consequences:
- Put specific rules above general ones. "Lahore and more than PKR 5 crore" must sit above "Lahore".
- End with a catch-all or a fallback. What happens to a lead that matches nothing? It should be a rule you chose, not an accident.
Pitfalls that break routing
Overlapping budget ranges
If one rule says "up to PKR 50 lac" and another says "PKR 50 lac and above", a lead with exactly PKR 50 lac fits both when the ends are inclusive. The first rule wins, so decide which side of the line you want and order them on purpose.
Missing data
A lead with no budget cannot match a budget rule. A chat that has not revealed a language cannot match a language rule. Many WhatsApp enquiries start with "price?" or "rate kya hai?" and nothing else. Your fallback has to handle leads that carry no budget, no city and no clue.
This is why asking for budget on your lead form matters. Facebook and TikTok forms can ask for it, and a budget rule is only as good as the answer that arrives.
Inconsistent spelling
Cities are text, not codes. "Lahore", "Lhr" and "لاہور" are three different strings, so list the spellings you actually see.
Language is a guess
Unless the customer says it, the language is inferred from their first message. A short message such as "Price?" tells you nothing, and Roman Urdu is easy to confuse with English. Treat language rules as a helpful tilt, not a guarantee.
Nobody is available
A rule can match and still have nobody to send the lead to: the senior team is on leave, or at its open-lead limit. Decide in advance what happens then. A well-designed system skips unavailable agents and falls back to your normal rotation rather than dropping the lead.
How to test rules before they go live
Do not test routing with real customers. Write ten sample leads on paper, with the details a rule might look at, and the agent you expect for each:
| Test lead | Budget | City | Language | Channel | Expected |
|---|---|---|---|---|---|
| Large Lahore buyer | PKR 6 crore | Lahore | English | Senior Lahore | |
| Boundary case | PKR 50 lac | Karachi | Roman Urdu | Decide the side | |
| No budget | none | Lahore | English | Fallback | |
| Arabic enquiry | AED 1.5 million | Dubai | Arabic | TikTok | Arabic speaker |
| Late evening | PKR 80 lac | Islamabad | English | Website | Evening agent |
Then run each one through a simulator if your system has one, and compare the answer with your expectation. Also try:
- A value exactly on a boundary.
- A lead with nothing filled in.
- A lead arriving outside the time window.
- An agent switched to unavailable, to see the fallback.
Fix the order, not the expectation, when they disagree. Re-run all ten after every change.
Checklist
- Each rule solves a problem you can name, and you have five or six rules at most
- Specific rules sit above general ones
- Budget boundaries are intentional, not accidental
- Missing budget, city or language falls through to a sensible default
- City spellings you really see are listed
- Language rules are treated as a guess
- The fallback when nobody is available is decided
- Ten sample leads tested before going live
- Someone owns the rules and reviews them monthly
How BrokLeads does this
BrokLeads has lead routing rules that match on source, campaign, city, budget (more than, less than or between, ends inclusive), language, channel (WhatsApp, Facebook, TikTok, website and so on), property type for real estate workspaces, and time of day. A rule's target is one agent, a team or the pool, and it picks either in rotation or the agent with the fewest open leads. Rules run in priority order, and a lead that matches none goes to the normal round-robin.
Language is guessed from the first message as English, Roman Urdu, Urdu or Arabic. Each agent has a routing profile: languages, cities, an open-leads limit and an on/off availability switch that agents flip themselves. Budget is read from Facebook and TikTok lead-form answers, from a form question named like "budget", including text such as "50 lac – 1 crore" (a range uses its upper bound).
A simulator answers "what would happen to a lead like this?" without changing anything, and every routed lead stores a "Why this agent?" explanation: which rule matched, who was eligible, and who was skipped and why. Both make the test table above quick to run.
Two honest notes. Rules apply to new leads as they arrive; optional reassignment of stale leads exists but is off until a workspace switches it on. And a budget rule can only work when the lead has a budget, which in practice means a form that asks for it.
Keep reading
- Round-robin vs manual lead assignment for the default these rules sit on top of.
- Facebook lead ads for real estate in Pakistan for asking budget on the form.
- TikTok lead ads for real estate in Pakistan for the other form source.