Lead Routing Agent

Adam's take

The highest-stakes agent in the launch set. Run it in shadow mode longer than feels necessary; a misrouted lead is annoying, a suppressed customer getting prospected is a fire.

Required tools

Optional tools

Expected value

Speed-to-lead in minutes; SLA discipline; correct ownership without manual triage

Deployable workflow pack

The full pack includes the agent spec, deployment guide, architecture diagrams, n8n workflow skeleton, Clay template, HubSpot properties, JSON schemas, OpenAPI spec, cost and ROI calculators, demo data, QA checklist, and governance notes.

How to deploy this agent

Lead routing looks simple until you actually build it. A lead from an existing customer’s domain shouldn’t create a new deal. A named account should reach its assigned AE, not round-robin. A suppressed contact shouldn’t be routed anywhere at all. This agent runs every inbound lead through those checks in a strict, documented order — and it runs in shadow mode before it ever touches a live queue.

Core signals

Input schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://deploytheagent.com/schemas/agent-008-input.schema.json",
  "title": "Agent #008 Lead Routing Agent Input",
  "type": "object",
  "required": [
    "record_id"
  ],
  "properties": {
    "record_id": {
      "type": "string",
      "description": "CRM record ID (company/contact/deal depending on agent)."
    },
    "domain": {
      "type": "string"
    },
    "config_version": {
      "type": "string",
      "description": "Versioned config used for this run."
    }
  },
  "additionalProperties": true
}

Output schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://deploytheagent.com/schemas/agent-008-output.schema.json",
  "title": "Agent #008 Lead Routing Agent Output",
  "type": "object",
  "required": [
    "record_id",
    "routing_status",
    "routing_matched_rule",
    "routing_timestamp",
    "routing_exception_reason"
  ],
  "properties": {
    "record_id": {
      "type": "string"
    },
    "routing_status": {
      "type": "string",
      "description": "Agent #008 output field."
    },
    "routing_matched_rule": {
      "type": "string",
      "description": "Agent #008 output field."
    },
    "routing_timestamp": {
      "type": "string",
      "description": "Agent #008 output field."
    },
    "routing_exception_reason": {
      "type": "string",
      "description": "Agent #008 output field."
    }
  },
  "additionalProperties": false
}

Scoring / classification logic

Anything that fails all six rules, or matches two rules ambiguously (say, an open-opportunity match and a named-account match pointing to different owners), routes to a human-reviewed exception queue instead of a best guess. That design decision — ambiguous is safer slow than wrong fast — is the whole point of this agent.

HubSpot CRM properties

n8n workflow skeleton

The Lead Routing Agent routes every inbound lead through suppression, existing-customer, open-opportunity, named-account, and territory checks before falling back to round-robin — with a documented exception queue for anything that doesn't cleanly resolve. It runs in shadow mode before it ever touches a live queue. Configure every node marked CONFIGURE before enabling the trigger.

1. Trigger
   CONFIGURE: set cadence per agent-spec.md's What It Does section. Leave disabled until Step 6 of deployment-guide.md.
2. Load versioned config
   CONFIGURE: replace with your versioned config built from real data (see deployment-guide.md Step 1).
3. Fetch source data
   CONFIGURE: {{HUBSPOT_CREDENTIAL}}. Pull the fields listed in agent-spec.md's Inputs table.
4. Validate + gate records
   Drops records missing required inputs or failing suppression/gate checks defined in agent-spec.md. Logs every drop.
5. Apply workflow logic
   Implements the Workflow Logic table from agent-spec.md. Writes model/config version alongside every derived value for auditability.
6. Write agent-owned CRM fields
   CONFIGURE: {{HUBSPOT_CREDENTIAL}}. Writes only: routing_status, routing_matched_rule, routing_timestamp, routing_exception_reason. Never writes sales-owned fields.
7. Route to human review / alert
   CONFIGURE: {{SLACK_CHANNEL}}. Fires for records requiring human review per agent-spec.md's Governance section.

Cost calculator

ROI calculator

Governance notes

• Shadow mode is mandatory before production: routing decisions are logged and reviewed against real leads for a minimum of two weeks or 100 leads before the toggle is flipped to live.
• Every routing decision logs its matched rule and timestamp, so any routing outcome is fully auditable after the fact.
• Ambiguous or unresolved leads always go to a human exception queue — never a confident best-guess assignment.
• Suppressed contacts are never routed anywhere, checked before any other rule runs.

Failure modes

• Existing customer routed as a new logo: prevented by running the domain-match check unconditionally before round-robin — a QA test asserts a customer-domain lead never reaches the fallback rule.
• Named account routed to the wrong rep: usually caused by a stale named-account list — QA includes a staleness check on the list’s last-updated date.
• An ambiguous lead routed confidently anyway: a QA test deliberately constructs a lead matching two rules and asserts it lands in the exception queue, not auto-routed.
• Shadow mode skipped under launch pressure: the deployment checklist makes shadow-mode sign-off a hard gate before production goes live — not a suggestion.

QA checklist

FAQ

Related agents