Inquiry routing: assign by region, product, and deal size while balancing sales workload
1. The three assignment dimensions: how region, product, and deal size stack
When an inquiry comes in, score it first, then route it. Routing isn’t based on a single dimension, it stacks region, product, and deal size. A salesperson who matches all three gets priority, two matches come next, and one match is the fallback. This order of priority can’t be shuffled.
| Dimension | Match criteria | Weight | What happens when it doesn’t match | Example |
|---|---|---|---|---|
| Region | Buyer’s country, language, time zone | 40% | Language barrier, time zone mismatch, slow response | A German buyer goes to a German-speaking salesperson |
| Product | Product line or model mentioned in the inquiry | 35% | Not enough expertise, can’t answer technical questions | An inquiry about model X100 goes to the X100 product line salesperson |
| Scale | Estimated order volume, customer tier | 25% | A big account goes to a junior rep and the deal is lost | A customer buying $500K a year goes to a senior salesperson |
Of the three dimensions, region carries the most weight (40%), because language and time zone are hard constraints. Route a Japanese buyer’s inquiry to a salesperson who doesn’t speak Japanese and is 8 time zones away, and even with strong product expertise, the reply won’t go out until the next afternoon, blowing the first-response SLA. Product carries 35%, because failing to answer a technical question is worse than replying late. Deal size carries 25%, mainly to keep big accounts from being misrouted to new hires.
Example: an inquiry comes in from Brazil mentioning Model X200, with an estimated monthly purchase of 2,000 units. By region, it should go to a South America rep who speaks Portuguese; by product, the senior rep on the X200 line knows it best; by deal size, 2,000 units a month makes it a key account, so it should go to a senior rep. All three dimensions point to the same person — that’s the ideal outcome. If three different people match on different dimensions, score them by region 40% + product 35% + deal size 25% and pick the highest total. For the overall approach to lead scoring, see Lead Scoring and Prioritization for Inquiries.
2. Load balancing: distribute by capability, not equally
This is the most important judgment call: load balancing does not mean splitting inquiries evenly. When many teams set up routing, their first instinct is “everyone gets the same number of inquiries.” That looks fair, but in practice it punishes your best closers. A rep who closes 20% of inquiries and one who closes 5%, given the same number of inquiries, means high-quality inquiries are wasted on the low converter.
| Rep type | Typical close rate | Recommended distribution | Max open inquiries | Inquiry quality tier |
|---|---|---|---|---|
| Senior salesperson | 15% to 25% | Priority for high-intent inquiries | 12 to 15 | Score 70+ first |
| Mid-level rep | 8% to 15% | Normal distribution, with coaching | 10 to 12 | Score 50 to 70 |
| Junior rep | 3% to 8% | Low-intent inquiries for practice | 8 to 10 | Score 40 to 60 |
| Sales manager | — | Escalations and key accounts only | No proactive distribution | Score 85+ or escalations |
The most counterintuitive point in this table: senior reps actually have a higher cap on open inquiries (12 to 15), not a lower one. That’s because they close at a higher rate, so they work through the same number of inquiries faster and nothing piles up. Junior reps have a lower cap (8 to 10) because they follow up slowly, and too many inquiries will pile up. True load balancing means “distribute by capacity to work inquiries,” not “split evenly per person.”
The exact load cap numbers can be adjusted to fit your team. The core rule: when a rep’s open inquiries reach 80% of the cap, the system sends an alert; at 100%, new inquiries stop going to them and go to a teammate in the same group; once they move their open inquiries to the next stage (quoted, sample sent, etc.) and the count drops, distribution resumes. This keeps inquiries from getting stuck when a rep is on vacation or swamped. For team structure and role setup, see Taking a Go-Global Team from 0 to 1.
3. Distribution SLA: how fast inquiries go out
Faster distribution isn’t always better, but there must be a time limit. If a high-intent inquiry is distributed slowly, the first-response SLA is already broken. Low-intent inquiries can wait a bit, since they’re still in the nurturing stage. Tier the time limits by score.
| Inquiry score | Intent score | Distribution SLA | How credit is assigned | Action on timeout |
|---|---|---|---|---|
| 80 or above | A · High intent | Distribute immediately (within 5 minutes) | Auto-route + manager confirmation | If unassigned after 10 minutes, auto-forward to the on-duty manager |
| 60 to 79 | B — Medium intent | Assigned within 1 hour | Auto-routing | Escalate to manager if unassigned after 2 hours |
| 40–59 points | C — Low intent | Assigned same day | Bulk assignment | Moved to nurture pool if still unassigned next day |
| Under 40 points | D — Nurture | Not assigned directly | Enter marketing automation sequence | Nurtured by marketing team |
A-grade leads must be assigned automatically, never through manual approval. The moment someone has to decide by hand who gets an A-grade lead, the 5-minute SLA is broken. The right approach: the system scores the best match across three dimensions, assigns it directly, and notifies the manager. If the manager thinks the assignment is wrong, they can adjust it within 10 minutes — but by default it runs automatically and waits for no one.
Don’t route D-grade leads to sales, because even if you do, the rep won’t work them. D-grade leads belong in the marketing automation nurture sequence, warmed up slowly through email, content and events, and only enter the sales assignment pool once they heat up to C or above. This tiering saves reps’ time and spends it only on leads worth spending it on. For how first-response SLA works with assignment, see First-response SLA and conversion rate for inquiries.
4. Handling assignment exceptions: what if the routing is wrong
A routing system can’t get it right 100% of the time. So what do you do when it’s wrong? The key is to have a “return mechanism” and a “re-routing mechanism” instead of forcing a rep to grind through a lead that doesn’t fit.
| Exception scenario | Trigger | Action | Re-routing target | Latency |
|---|---|---|---|---|
| Language mismatch | Rep doesn’t speak the buyer’s language | Can be returned within 24 hours | Rep in the same region who speaks that language | Reassigned within 4 hours |
| Product mismatch | Lead’s product line is outside the rep’s scope | Returned within 12 hours | Rep for the matching product line | Reassigned within 2 hours |
| Capacity full | Rep already at the limit of active leads | Automatically returned to the queue | Next-best rep on the same dimension | Re-routed immediately |
| Buyer names someone | Buyer asks for a specific person in their email | Skip routing and assign directly | The person named | Assigned immediately |
The key to a return mechanism: reps must feel no guilt about returning a lead. Many teams treat return rate as a performance metric, so reps take on leads they know they can’t handle and end up killing them. The right approach is to not measure return rate, but to require a reason for every return — with a reason logged, the system can learn and route better next time. The common return reasons are the four types in the table above, and the system keeps refining routing weights from that data.
Connecting your website to the CRM is the technical prerequisite for routing to run automatically. For field mapping, deduplication and auto-assignment rules, see Website leads to CRM. For form reliability and data quality issues, see Inquiry Form Reliability and Spam-Proof Delivery.
FAQ
Should leads be split evenly among reps?
How many leads should one rep work at the same time?
How fast must a new lead be assigned?
What if a lead is assigned to the wrong rep?
Of region, product and company size, which dimension has the highest priority?
Should low-intent leads also go to reps?
Final thoughts
Inquiry routing sounds like an internal management issue, but it directly determines your inquiry conversion rate. Take the same 100 inquiries: routed to the right people, they might close 20 deals; routed to the wrong people, maybe 5. The gap isn’t sales skill, it’s routing logic. Most teams don’t have a sales problem, they have a problem getting inquiries to the right hands.
Three steps to implement: first, define routing rules across region, product, and deal size, weighted 40/35/25; then set load caps, 15 for senior reps and 8 to 10 for junior reps, and pause routing once exceeded; finally, tier your routing SLA by score, A-tier auto-routed in 5 minutes, B-tier in 1 hour, C-tier same day. Run this for a quarter, then use conversion data to recalibrate the weights and caps.
One line worth remembering: inquiry routing isn’t “whoever’s free gets it,” it’s “whoever’s the best fit gets it”—even distribution looks fair, but it’s actually the biggest penalty for your high-converting reps.