lead-triage

name	lead-triage
description	Prioritize and route leads; never use opaque scores.
metadata	{"short-description":"Prioritize and route leads transparently"}

Lead Triage

Outcome

A reviewable lead queue with reasons, duplicates, missing evidence, and recommended ownership.

CRM-neutral operating contract

• Discover available CRM, communication, calendar, knowledge, and file capabilities before choosing a retrieval plan. If no live CRM is available, use user-supplied exports when that still satisfies the request; never imply a live write is possible.
• Map records by meaning, not vendor labels: organization, person, lead, opportunity, activity, product, service record, user or team, and knowledge item. Inspect schemas and custom fields, preserve native IDs, stages, currencies, timezones, and fiscal periods.
• Keep observed facts, derived conclusions, and missing information distinct. Anchor consequential claims to record IDs, fields, timestamps, or named sources, and state access or freshness limits.
• Start read-only. Before creating, updating, assigning, sending, or scheduling, show the exact proposed action and obtain confirmation unless the current request already authorized that exact mutation.
• Obey connected-system permissions, resolve ambiguous records or people instead of guessing, check for duplicates before creation, and report partial failures without repeated retries.

Workflow

1. Resolve the user, target records, requested scope, reporting window, timezone, and business objective. Ask only for missing details that materially change the result.
2. Retrieve the minimum authorized evidence needed from the following inputs: Lead records, source, consent and suppression status, engagement, fit attributes, territory, existing people and accounts, routing rules, ownership, and capacity.
3. Normalize relevant entities and fields while retaining native record identifiers and source timestamps.
4. Apply the analysis rules below. When evidence conflicts, show the conflict rather than averaging it away.
5. Deliver the required output in a compact form suited to the scope. Put urgent or decision-relevant items first.

Analysis rules

1. Check eligibility, suppression, duplicates, existing account ownership, and active opportunities before prioritization.
2. Apply the organization's configured scoring and service-level rules when available; otherwise propose transparent factors rather than inventing cutoffs.
3. Separate fit, intent, urgency, and data quality so one signal does not dominate silently.
4. Explain routing conflicts, stale leads, and uncertain matches.

Required output

• Priority queue
• Reason codes and evidence
• Duplicate or ownership conflicts
• Recommended route and timing
• Exceptions needing human review

Actions and boundaries

Assignment, conversion, disqualification, or outreach requires explicit confirmation of the affected records.