Skip to main content
Routing rules in Salesforce or HubSpot handle 80% of inbound leads. The other 20% are the edge cases that eat hours — accounts spanning multiple territories, ambiguous industries, parent-child company tangles, region overrides. A routing Agent reads each lead, applies your rules where they’re clear, and handles the judgment where they aren’t.

​
When this pays off

Routing rules are too brittle

Existing logic handles the easy 80%; the rest end up in a queue waiting for RevOps to manually route.

Region overlaps cause disputes

Reps argue over who owns a lead because firmographic data disagrees about region or segment.

Routing latency

Hours pass between lead landing and lead getting picked up because manual routing is the bottleneck.

Parent-child confusion

A new contact at a subsidiary lands without recognizing the parent already has an open opportunity.

​
The shape of this use case

A routing Agent takes a new lead and returns an assignment decision with reasoning.

Inputs

Lead record, account context, territory boundaries, current rep workload.

Sources

CRM, territory / segmentation rules, rep capacity data, parent-child account hierarchy, your routing playbook.

Output

A routing decision (rep / team, reasoning, confidence), with flags for edge cases that need human review.

Delivery

Applied directly in the CRM as owner, posted to Slack on edge cases for RevOps to confirm, logged with reasoning for audit.

​
Where to start

Two ways in, depending on whether you want something running today or built to your exact spec.

Clone a pre-built Agent

Open the CRM Agent. More in the Marketplace.

Build your own

Start from scratch in the builder, or by describing it in Claude Code or Cursor with Programmatic GTM.
Either way, these are prompts your team can use on day one:
  • “Where should this lead go? Acme Corp, contact at the German subsidiary, parent account owned by the US enterprise team.”
  • “This batch of 50 leads imported from a trade show — apply our routing rules and tell me which ones need a human decision.”
  • “Is this lead a re-engagement of an existing opportunity or a new prospect? Check parent-child and prior history.”

​
Where to take it

Once it’s running, deepen it in three moves:

Give it a playbook

Shape it with a prompt, your territory rules in Knowledge, and Bulk Schedule.

Automate it on signals

Wrap it in a workflow that fires on a trigger.

Let it improve

Feed back which routing held up into the Agent’s evals so edge-case handling tracks real outcomes.

​
Common pitfalls

Force the Agent to flag low-confidence decisions for human review rather than making a guess. Wrong assignments are expensive to undo.
Without hierarchy data in Knowledge, the Agent treats subsidiaries as net-new accounts. Document the parent-child structure explicitly.
Routing on rules alone overloads top reps. Have the Agent factor current pipeline volume into the routing decision.
Reps dispute routing decisions. Log every Agent decision with its reasoning so you can review later.