Lead Scoring and Automatic Assignment

Problem addressed

After leads enter a CRM, the bottleneck is often not lead volume but mixed signals around quality, territory, assignee capacity, and response time. Low-priority leads can consume senior sales time, out-of-territory leads can be assigned to the wrong owner, and hot leads can exceed SLA due to uneven workload. lead-routing treats these as operational workflow problems by separating scoring, qualification, territory mapping, assignment, workload balancing, and escalation into auditable routing strategies.

How it works

The skill organizes routing around several strategies:
- Rule-based routing: apply eligibility checks using industry, company size, region, and intent fields;
- AI scoring: produce score, fit_score, intent_score, and tier, with reasoning;
- Territory mapping: assign leads to the corresponding sales region or responsible team;
- Round-robin distribution: spread eligible leads to avoid concentrating work on one owner;
- Workload balancing: adjust assignment based on current capacity;
- SLA monitoring: trigger reminders or escalation for overdue or high-priority leads.
The example output marks a CTO-level lead from a 500-person SaaS company as A tier, then generates recommended_action and a first outreach email draft.

Boundaries

It is most useful as a design reference for sales operations, CRM automation, and lead assignment flows, especially when integrated with HubSpot, Salesforce, or n8n templates. Before sending, publishing, deleting, paying, deploying, or writing to external systems, confirm the target and impact. Credentials should be used only for the specified official service and must not be echoed or forwarded. Commands and code are reference implementations; they do not install dependencies, change system permissions, or create persistent tasks automatically. For help and more skills, follow Jianshi AI or search for Jianshi AI on SkillHub.