lead-routing-rules

Score and route new HubSpot leads to sales reps using territory, segment, and round-robin rules.

20.2k|3.4k|Updated Oct 5, 2024
One-click install
npx skills add https://github.com/kortix-ai/suna --skill lead-routing-rules
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lead-routing-rules
Source: https://github.com/kortix-ai/suna/tree/main/packages/starter/templates/marketplace/runtime/skills/lead-routing-rules
Command: npx skills add https://github.com/kortix-ai/suna --skill lead-routing-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

New inbound leads sit unassigned in HubSpot while reps wait, and manual assignment is slow, inconsistent, and prone to favoritism or missed high-intent buyers. This Skill runs a recurring sweep that scores each unrouted lead for intent, matches it against territory and segment rules, falls back to a stateless round-robin pool, and writes the assignment back to HubSpot with a Slack notification.

Core Features & Use Cases

  • Intent Scoring: Flags leads as high-intent when they clear two or more signals (VP-level title, enterprise company size, in-quarter budget/timeline, pricing-page or demo-request engagement) so reps work them first.
  • Rule-Based Routing: Resolves assignment through a territory map, then segment specialists, then a stateless round-robin pool computed from each rep's current weekly lead count in HubSpot.
  • Safe Escalation: Leads with missing data, map gaps, or genuine ties are posted to an escalation channel and flagged in HubSpot instead of being guessed at.
  • Use Case: A 15-minute sweep finds five new leads; three route by territory, one by enterprise segment, and one with no region data is escalated to a human — each with the owner, reason, and timestamp written back to HubSpot.

Quick Start

Ask the agent to check HubSpot for new unrouted leads and assign each one to the right rep using the routing rules.

Frequently Asked Questions about lead-routing-rules

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically route new HubSpot leads to sales reps?

Run a sweep that queries HubSpot for contacts on the target lifecycle stage without a routing marker, scores each for intent, then matches territory, segment, and round-robin rules in order. The assigned owner and routing reason are written back to the HubSpot record.

How does round-robin lead assignment work without stored state?

The pool is stateless: each sweep counts every pool rep's currently owned leads created this week in HubSpot and assigns the new lead to the rep with the fewest. Ties break alphabetically, so no rotating pointer needs to persist between sessions.

What happens when a lead cannot be matched to any routing rule?

Unresolvable leads are escalated, never guessed. The lead is posted to the escalation channel with what was checked, and its kortix_routing_status is set to flagged so it is not reprocessed on later sweeps.

Does this lead routing modify or delete HubSpot records?

No. The only HubSpot writes are the owner field and the kortix_routing_status property with its reason and timestamp. The skill never deletes, merges, or bulk-updates lead records under any circumstance.

How are high-intent leads handled differently in routing?

High-intent status does not change who receives the lead; it changes the notification. Leads clearing two or more intent signals (senior title, enterprise size, in-quarter budget, demo or pricing engagement) are flagged in the Slack notification so the assigned rep works them first.