score-leads

Resolves sales leads and returns Hot/Warm/Cold tiers with response-time SLAs.

4|5|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/Zoominfo/zoominfo-mcp-plugin --skill score-leads
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: score-leads
Source: https://github.com/Zoominfo/zoominfo-mcp-plugin/tree/main/skills/score-leads
Command: npx skills add https://github.com/Zoominfo/zoominfo-mcp-plugin --skill score-leads

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Score and prioritize sales leads or cold contacts so reps know who to call first, how quickly to respond, and why each lead belongs in its Hot/Warm/Cold tier.

Core Features & Use Cases

  • Deterministic lead resolution: Resolves leads from ZI person IDs, emails, or name+company rows with strict validation (typo’d emails fail explicitly; ambiguous matches are not auto-accepted).
  • Four-axis lead scoring: Computes a composite tier using person fit, account fit, source signal, and trigger/intent drivers with configurable weights and thresholds.
  • Use-case tuned response SLAs: Applies different SLA bands for inbound routing, event follow-up, PQL triage, and content follow-up so prioritization matches the motion.
  • Trust-first per-lead explanations: Provides a scannable row with a specific “why now” snippet anchored to the strongest axis driver, plus a concrete next action and verified contact data for Hot leads.

Quick Start

Use score-leads to tier a mixed list of lead emails into Hot/Warm/Cold with inbound-routing SLAs and a recommended next action per lead.

Frequently Asked Questions about score-leads

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

FAQPage Schema
How do I score and prioritize sales leads into Hot Warm and Cold tiers?

Lead scoring prioritizes contacts using a four-axis model of person fit, account fit, source signal, and intent triggers. This computes Hot Warm and Cold tiers with use-case-specific response-time SLAs so reps know exactly who to call first.

What is the best way to route inbound leads with SLA response times?

SLA routing for inbound leads assigns response-time bands based on the lead's computed tier. By resolving identifiers into verified records and applying use-case-tuned SLAs, the system ensures prioritization matches your specific sales motion.

How does lead resolution handle incorrect emails or ambiguous company names?

Lead resolution uses deterministic validation without silent fallbacks. Typo'd emails fail explicitly and ambiguous name+company matches are not auto-accepted, ensuring your lead scoring operates only on strictly verified contact records.

Can I use mixed input formats like person IDs and name+company rows for lead triage?

Lead triage supports mixed inputs by resolving ZoomInfo person IDs, emails, or name+company rows into verified records. This allows you to process diverse lead lists for MQL or PQL triage without standardizing the input format beforehand.

Why does my lead scoring need a specific why-now rationale for each contact?

A why-now rationale anchors the lead score to the strongest axis driver, such as an intent trigger. Providing a scannable explanation with a concrete next action and contact data ensures reps can execute immediate, contextual follow-up on Hot leads.

Does lead scoring work for event follow-up and content download responses?

Lead scoring applies use-case tuned response SLAs for event follow-up and content follow-up. By adjusting the scoring weights and thresholds for these specific motions, the system accurately prioritizes leads based on the context of their engagement.