Skip to content
‹ Back to Agent Factory
LEAD_CAPTURE

Qualification & routing

Every inbound lead gets scored against your ICP, qualified against your buying-readiness rules, and routed to the rep who should own it, in the seconds it takes the form to submit. No round-robin spreadsheet, no Slack triage, no good leads sitting in the wrong rep's queue.

Overview

Routing is where most inbound funnels quietly bleed out. The lead arrives, the form fires, and somewhere downstream a routing rule written in 2022 sends a Series C VP of Engineering to an SDR who covers small-business dental practices. By the time anyone notices, the prospect is on a discovery call with a competitor.

This agent qualifies and routes every inbound lead the moment it lands. It scores against your ICP, evaluates buying-readiness signals, applies your ownership logic, territory, vertical, deal size, account ownership, round-robin balancing, and assigns the lead to the rep who should actually work it. The CRM gets created or updated in the same motion. The rep gets a clean handoff with full context. Routing stops being the thing your RevOps lead has to babysit and starts being the thing that just works.

Capabilities

  • Scores every inbound lead against your ICP definition the moment it arrives, with no delay between submission and routing decision
  • Applies multi-dimensional routing logic: territory, vertical, company size, deal stage, named account ownership, and round-robin load balancing, all in one pass
  • Evaluates buying-readiness signals (page visits, content downloads, intent data, prior touches) to separate hot leads from research traffic
  • Creates or updates the CRM record in the same motion, so the rep walks into a clean account, not a mystery
  • Posts a structured handoff to the assigned rep with the lead's score, fit signals, and recommended next action
  • Logs the routing decision and the rules that produced it, so RevOps can audit, tune, and prove the logic when leadership asks

Example Output

Inbound trigger

"Contact sales" form submitted at 2:14pm Tuesday by Daniel Park, Director of Engineering at Vanta Bio (Series B biotech, ~210 employees, San Francisco).

Agent decision, completed in 4 seconds:

Lead: Daniel Park, Director of Engineering, Vanta Bio

ICP fit score: 91/100

Buying-readiness score: 82/100 (visited pricing page twice in last 7 days, downloaded technical whitepaper, attended last week's webinar)

Routing decision: Enterprise West territory · Biotech vertical · Mid-market deal band ($75K-$250K projected ACV)

Owner identified: Priya Shah (Enterprise AE, West, biotech specialist), currently below sequence load cap, no conflicting account ownership

CRM action: New account created for Vanta Bio. Daniel Park added as primary contact. Lead status set to "MQL, Sales Accepted." Opportunity stub created at $150K projected ACV.

Handoff posted to Priya in Slack:

Daniel Park, Director of Engineering at Vanta Bio, just submitted a contact-sales form. ICP fit 91, buying-readiness 82. He's been on the pricing page twice in the last week and pulled the technical whitepaper Friday. Vanta Bio is Series B, ~210 employees, biotech. No prior account in CRM. Recommended next action: respond inside the five-minute window with a calendar link, lead with the technical whitepaper context. Full record in Salesforce.

Rules applied (logged for audit): Territory_v3.2 · ICP_BiotechMidMarket_v1.4 · BuyingReadiness_Inbound_v2.1 · OwnershipBalancing_RoundRobin_v1.0

Agent Workflow

Step 01

Receive the inbound

The agent triggers the moment a lead enters the funnel through any connected source: web forms, demo requests, chat, gated content downloads, webinar registrations, or partner referrals. Latency from submission to qualification is typically under five seconds.

Step 02

Score against ICP

The agent applies your ICP definition, firmographic, technographic, role-level, and produces a fit score with the underlying signals attached. Reps see why a lead is high-fit, not just that it is. RevOps can audit and tune the model without touching code.

Step 03

Evaluate buying-readiness

The agent layers behavioral and intent signals on top of fit: pricing page visits, content depth, prior touches, third-party intent feeds, time-on-site patterns. A high-fit lead with no buying signal is treated differently from a high-fit lead actively shopping.

Step 04

Apply routing logic

The agent walks your routing rules in order: named account ownership, territory, vertical, deal-size band, round-robin load balancing across reps inside the matched segment. Conflicts and tie-breakers resolve to a single owner before the agent moves on.

Step 05

Identify the owner

The agent confirms the assigned rep is available, below their lead-load cap, and not on PTO or coverage. If the primary owner is unavailable, the agent applies your fallback rule, backup rep, manager queue, or held-pending, based on what you've configured.

Step 06

Create or update the CRM record

The agent writes to the CRM in the same motion: new account if needed, contact appended, lead status set, opportunity stub created if the deal-size band warrants it. The rep never inherits a half-built record.

Step 07

Hand off with context

The assigned rep gets a structured Slack or email handoff with the lead's name, role, company, fit score, buying-readiness signals, recent behavior, and a recommended next action. The brief is short enough to read on a phone and complete enough to act on.

Step 08

Log the decision

Every qualification score, every rule applied, every routing decision is logged with version-stamped rule sets. RevOps can audit any lead's path through the funnel, prove the logic to leadership, and tune the rules with full history.

Go live in days

AI for work, that just works.