When a high-intent lead fills out your form at 2pm on a Tuesday, what happens next determines whether they become a customer or a competitor's win. That window between submission and first contact is where deals are made or lost, and for most growing teams, that window is managed by someone manually checking a spreadsheet.
Lead routing based on criteria is the process of automatically directing incoming leads to the right sales rep, team, or workflow based on specific data points captured at the point of conversion. Company size, industry, geography, budget, product interest — these signals tell you who should handle a lead, and criteria-based routing acts on that information instantly.
For high-growth teams, manual lead assignment is a bottleneck that doesn't scale. As your pipeline grows, the cost of misrouted leads compounds: wrong reps chase wrong-fit prospects, response times slow, and conversion rates suffer. A well-built routing system eliminates that friction entirely.
This guide walks you through exactly how to build a lead routing system from scratch. From defining your routing logic to connecting your form data to your CRM and testing every path before going live, you'll finish with a fully operational system tied directly to your lead capture forms.
By the end, you'll know how to define the criteria that matter most to your sales team, structure your intake forms to collect the right routing signals, build routing rules that match your sales structure, connect everything to your CRM, and monitor performance over time.
Let's build it.
Step 1: Define Your Routing Criteria Before Touching Any Tool
This is the step most teams skip, and it's the reason most routing systems break. Before you open your CRM, your form builder, or any automation tool, you need a written document that describes exactly how leads should be assigned. Everything else is just implementation.
Start by identifying the core data points your sales team actually uses to decide who handles a lead. The most common routing criteria fall into a few categories:
Firmographic criteria: Company size, industry vertical, and geographic territory. These are the most common routing signals because they map directly to how most sales teams are structured.
Deal-level criteria: Budget range, deal size, or timeline to purchase. These signals help separate leads that are ready to buy from those that need nurturing.
Behavioral and interest criteria: Product interest indicated on the form, content downloaded before converting, or specific pages visited. These signals indicate intent beyond just fit.
Once you've listed your criteria, map them to your actual sales team structure. Territory-based routing assigns leads by region or named account list. Round-robin routing distributes leads evenly within a qualified segment. Skill-based routing matches leads to reps with specific product expertise. Tiered routing combines lead scoring with rep seniority, so higher-scored leads go to senior closers.
Next, distinguish between hard criteria and soft criteria. Hard criteria are must-match rules: if a lead's company is in a specific region, it goes to that territory's rep, full stop. Soft criteria are weighted factors: a lead from a preferred industry gets a higher score, which influences routing tier, but doesn't override a hard rule.
Before you build anything, document your routing logic as a decision tree or matrix. A simple table works: rows represent criteria combinations, columns represent the assigned destination. For example: company size 500+, industry SaaS, geography North America routes to the Enterprise AE team. Company size under 50, any industry, routes to the SMB nurture sequence.
The output of this step is a written routing matrix. It doesn't need to be pretty. It needs to be complete. Every routing scenario you can anticipate should have a defined destination, including a fallback for leads that don't match any primary rule.
Skipping this step and building rules reactively leads to conflicting logic and gaps where leads fall into an unassigned state. Review lead routing best practices to understand how teams structure their criteria documentation before writing a single rule.
Step 2: Build Intake Forms That Capture the Right Routing Signals
Your form is the data source for every routing decision downstream. If the right fields aren't present, or if they're collecting data in the wrong format, your routing logic breaks before it even starts.
For most routing setups, you'll need these fields at minimum: company name, company size (structured dropdown), industry (structured dropdown), job title or role, geographic location, and primary use case or product interest. These fields directly feed the criteria you defined in Step 1.
The most important formatting rule: use dropdowns or radio buttons for any field that feeds a routing rule, not free text. "Enterprise" is routeable. "We have about 500 people across three offices" is not. Your CRM routing rules will look for exact string matches or predefined values, so unstructured input creates mismatches that silently break your system.
Use conditional logic to show or hide fields based on earlier answers. This keeps your form from feeling like a questionnaire while still capturing the depth of data you need. For example: only show a "team size" field if the respondent selects "B2B company" as their business type. Only show a "current tool stack" field if they indicate they're evaluating alternatives. Dynamic form fields based on user input reduce friction while preserving data quality.
For returning visitors or leads you've already partially profiled, consider progressive profiling. Rather than asking the same questions again, surface new fields that enrich the existing record. This is especially useful for leads re-engaging through gated content or product interest forms.
Here's the success check for this step: every routing rule in your matrix from Step 1 should have a corresponding form field that feeds it. Go through your routing matrix row by row. If a rule says "route enterprise leads to the Enterprise AE team," your form must have a company size field with "Enterprise" as a selectable option. If there's a routing rule without a corresponding form field, you have a gap.
Orbit AI's form builder is designed for exactly this kind of structured data capture, with conditional logic and dropdown fields built in so your routing signals are clean from the moment of submission.
Step 3: Score and Segment Leads at the Point of Submission
Routing isn't just about directing leads to the right rep. It's about directing the right leads to the right rep at the right priority level. That's where lead scoring comes in.
Before a lead is routed, assign it a score or segment tag based on form responses. This score determines which routing tier applies: enterprise leads with high scores go immediately to senior AEs, mid-tier leads route to SDRs for a qualification call, and low-priority leads enter an automated nurture sequence.
Define scoring weights for each criterion based on what actually correlates with closed deals in your pipeline. Company size typically carries significant weight. Budget range and purchase timeline are strong indicators of near-term intent. Role and seniority matter because a VP of Sales evaluating a tool is further along in the buying process than an analyst doing research.
The key is to base your weights on your own historical data, not assumptions. Look at your closed-won deals from the past year. What firmographic and behavioral patterns do they share? Let that data inform your lead scoring methodology rather than building it from scratch based on intuition.
Use your form builder's qualification layer or submission logic to calculate scores automatically. When a lead submits, the system evaluates their responses against your scoring rules and tags the record with a tier before it ever reaches your CRM. Orbit AI's platform includes built-in lead qualification logic that handles this at submission, so you're not relying on post-submission CRM workflows to do the scoring work.
Create clear segment buckets with defined thresholds. Three tiers is the right starting point: High Priority (route immediately to a senior rep), Mid-tier (route to an SDR for a qualification call), and Low Priority (enter automated nurture). Resist the urge to create five or six tiers before you have the data to support that level of segmentation. Start simple, and refine based on actual conversion outcomes.
Step 4: Configure Your Routing Rules in Your CRM or Routing Tool
This is where your routing matrix becomes executable logic. The goal is to translate every row in your documentation into a working if/then rule in your system.
First, decide where your routing logic lives. Your options are: natively in your CRM (Salesforce assignment rules, HubSpot workflows), a dedicated lead routing tool layered on top of your CRM, or your form builder's automation layer for simpler setups. Each has tradeoffs. Native CRM routing is tightly integrated but can be rigid. Dedicated routing tools offer more flexibility but add another system to maintain. Form builder automation works well for straightforward routing but may not handle complex multi-condition logic.
Build your if/then rule sets to mirror your routing matrix exactly. The structure looks like this:
IF company_size = "500+" AND industry = "SaaS" AND region = "North America" THEN assign to Enterprise AE team, notify via Slack and CRM task, set SLA timer to 5 minutes.
IF company_size = "1-50" AND timeline = "Just exploring" THEN add to SMB nurture sequence, assign to nurture queue owner.
Every rule needs an explicit action: who gets assigned, how they're notified, and what SLA applies.
Set up round-robin distribution within segments to balance workload. If five AEs handle enterprise accounts in North America, leads should distribute evenly across them. Most CRMs support round-robin natively or through workflow tools. Without it, you'll find certain reps getting buried while others have empty queues.
Configure fallback rules. This is non-negotiable. Every routing system has edge cases: leads that partially match criteria, leads from unexpected geographies, leads with blank fields. Without a fallback rule, those leads land in an unassigned state and sit there. Your fallback might be a "routing review" queue owned by a sales ops manager, or a default rep who handles overflow. The destination doesn't matter as much as the fact that one exists.
Set SLA timers and notification triggers so assigned reps receive immediate alerts on new assignment. Slack notifications, email alerts, and CRM tasks all serve different purposes. Use at least two channels to ensure the rep sees the alert quickly.
Step 5: Connect Your Forms to Your CRM and Automate the Handoff
Your routing rules are only as good as the data that reaches them. The connection between your form and your CRM is where many technically sound routing systems quietly fail, and it almost always comes down to field mapping.
Map every form field to its corresponding CRM field before you do anything else. This sounds obvious, but the failure mode is subtle. Your form might have a company size dropdown with the option "51-200 employees." Your CRM routing rule might be looking for "51-200." If there's a space difference, a capitalization difference, or a formatting difference, the rule won't fire. The lead arrives in your CRM with no assignment and no notification.
Use native integrations where available. Orbit AI forms connect directly to major CRMs, which means field mapping is handled through a structured interface rather than manual configuration. For custom or less common connections, middleware tools like Zapier or Make can bridge the gap, but they add a step where things can break, so document those connections carefully.
The data flow you're building looks like this: form submission triggers CRM record creation, CRM record creation triggers routing rule evaluation, routing rule evaluation assigns the rep, assignment triggers rep notification. Each step depends on the previous one completing correctly.
Test field mapping with a live test submission before going live. Submit the form yourself with values that should trigger a specific routing rule. Check the CRM record that gets created: do the field values match exactly what your routing rules expect? Does the correct rep get assigned? Does the rep notification fire?
For multi-step forms, verify that all step data passes on final submission. A common mistake is building a multi-step form where routing-critical fields live on step one, but only step three's data gets sent to the CRM on submission. Your form builder should be configured to pass all collected data, not just the final step.
Enable duplicate detection at the CRM level. When a known lead re-submits a form, you don't want to create a new record and re-route them as if they're a new prospect. Duplicate detection ensures the existing record gets updated and the appropriate re-engagement workflow fires instead.
Step 6: Test Every Routing Path Before Going Live
The most common testing mistake is submitting one form with your own email address, seeing a CRM record appear, and calling it done. That tests one path. Your routing system has as many paths as you have rows in your routing matrix, and each one needs verification.
Create a test submission for every routing scenario in your matrix. If you have twelve routing rules, you need twelve test submissions. Use a spreadsheet to track each test: the criteria combination you submitted, the expected destination, and the actual result. Any mismatch is a bug that needs fixing before launch.
Test edge cases explicitly. What happens when a lead partially matches criteria? For example, the company size matches the enterprise tier, but the industry field is blank. Does the fallback rule catch it? What happens when a lead matches multiple rules? Your CRM should have a rule priority order that determines which assignment wins. Verify that priority order is correct.
Check rep notification delivery across all channels. Confirm that the Slack notification fires, the email alert arrives, and the CRM task appears on the assigned rep's queue. Don't assume that because the assignment is correct, the notification is also working. These are separate systems and can fail independently.
Consider running a shadow period of one to two weeks where both your old assignment process and your new routing system run in parallel. Compare the assignments they produce. If they diverge on a lead, investigate why. This parallel run catches routing automation challenges that only appear with real lead data.
Involve two or three sales reps in user acceptance testing. Give them test scenarios and ask them to evaluate whether the assignments make sense from a practical sales perspective. They'll identify issues your technical setup misses: a rep who handles a specific named account being excluded from a territory rule, a product interest category that doesn't map to the right specialist.
Step 7: Monitor Performance and Refine Routing Logic Over Time
A routing system isn't a one-time build. It's an operational layer that needs regular attention as your team, your ICP, and your pipeline evolve.
After launch, track these metrics consistently: lead response time by segment, conversion rate by routing destination, rep workload distribution, and the percentage of leads hitting your fallback rules.
Response time tells you whether the routing is actually creating speed-to-lead improvements. If response times haven't changed, the routing may be working but reps aren't acting on notifications. That's a process problem, not a routing problem.
Conversion rate by routing destination is the most important signal. If leads routed to senior AEs convert at roughly the same rate as leads routed to SDRs, your scoring model isn't differentiating effectively. If a particular routing destination consistently underperforms, investigate whether the criteria matching to that destination are actually predictive of quality.
Rep workload distribution tells you whether your round-robin logic is functioning and whether certain segments are generating disproportionate volume. Imbalanced workloads lead to rep burnout and slower response times in overloaded queues.
Your fallback rate is a diagnostic metric. A high percentage of leads hitting fallback rules signals that your primary criteria definitions are too narrow, your form fields aren't capturing data cleanly, or lead behavior has shifted in ways your routing rules don't account for. Investigate the leads in your fallback queue regularly and use patterns there to refine your primary rules.
Review your routing logic on a quarterly cadence. Sales team structure changes. Territories get redrawn. Your ICP definition evolves as you accumulate more closed-won data. Routing rules that were accurate when you built them may be misaligned six months later. A quarterly review keeps the system calibrated to your current reality.
Add new routing criteria as you identify patterns in your conversion data. If leads from a specific industry consistently close faster and at higher values, create a dedicated routing path for them rather than letting them flow through a generic segment. Your smart lead routing software should get smarter over time, not stay static.
Putting It All Together
Lead routing based on criteria isn't a one-time setup. It's an operational system that compounds in value as your pipeline grows. The seven steps above give you a complete framework: from defining routing logic and building smarter intake forms, to scoring leads at submission, configuring CRM rules, and monitoring performance over time.
Start with Step 1 even if you already have forms live. Most routing problems trace back to unclear criteria definitions, not broken technology. Once your routing matrix is documented, the technical implementation becomes straightforward.
Use this checklist to confirm you're ready to go live:
Routing criteria matrix documented: Every routing scenario has a defined destination, including a fallback.
Form fields mapped to routing signals: Every rule in your matrix has a corresponding structured form field feeding it.
Lead scoring tiers defined: Three tiers maximum to start, based on criteria correlated with closed deals.
CRM routing rules configured with fallbacks: If/then rules mirror your matrix, with a catch-all for edge cases.
Form-to-CRM field mapping verified: Dropdown values in your form match the exact values your CRM routing rules expect.
All routing paths tested: Every row in your matrix has a verified test result, including edge cases.
Performance metrics dashboard set up: Response time, conversion rate by destination, workload distribution, and fallback rate are all tracked.
Orbit AI's form builder is built for exactly this workflow: capturing structured lead data with conditional logic, qualifying leads at the point of submission, and connecting to your CRM so routing happens automatically. Start building free forms today and see how intelligent form design can turn your lead capture into a fully automated routing engine.
