Capture and prioritize leads
Capture and prioritize leads.
3 stages · 0 approvals
Roles and responsibilities
-
Step 1Configure lead policy
Consent NumberLeadChannelDecisionPhone
-
Step 2Capture and deduplicate
Lead NumberCompanyOwnerScore
-
Step 3Calculate lead priority
Run NumberLeadRule ScoreApplied Score
Process steps
Follow the process from start to finish. Select a step to see who acts and what changes.
Configure lead policy
Define acquisition sources, permitted contact purposes and qualification criteria. Record contact-policy evidence without treating an imported address as consent. Sales Manager defines territory coverage and eligible routing pools; inactive or absent staff cannot receive work.
Capture and deduplicate
Capture stable source identifiers and preserve the acquisition evidence. Proposed duplicate groups stay separate until Sales Manager independently resolves the submitted cluster. A merge preserves source references, restrictions and the stricter contact policy; it cannot move private notes into a wider scope. Freeze candidate membership and CandidateRevision in DuplicateMembers; a changed candidate invalidates the proposed resolution.
Calculate lead priority
Evaluate the approved policy against an exact lead revision. Count each source event once within its version and time window; expiry and reversals recompute the score. Commit a run only if its input revision is current. Optional model output is recorded with version and explanation, bounded by the approved contribution policy. Emit a threshold alert once per qualifying transition.
Approvals and controls
0 approvals required in this process
- Record ownershipKeep every reference and attachment in the authorized workspace and the acting person’s permitted scope. A copied link cannot grant access to another customer’s record.
- Current decisionsReview the latest saved state before changing work. If someone changes protected facts after approval, send the revised record through its required review again.
- Repeated actionsA retry returns the original result when the same action has already been accepted. Keep an uncertain external outcome visible until its original request is reconciled.
- CorrectionsRetain the earlier decision and the reason for correcting it. A report or automation should not hide a reversal by deleting the original evidence.
Follow the outcome
The receiving team needs the current owner, the next action and a traceable result. Use the linked operating records when investigating a delay rather than treating a status label as the complete explanation. If a required person is unavailable, route the decision through an authorized replacement who remains independent of its preparer. Resolve missing evidence before closing the handoff. A locally completed action may still require a confirmed response from its configured destination.
Lead capture. A repeated web-form event resolves to the same lead. Reject foreign-workspace references and imports without a stated source.
Priority alerts. The owner receives one actionable alert for the threshold crossing. A replay cannot create another alert or silently reassign the lead.
Duplicate resolution. A reviewed merge retains acquisition and scoring references. Reject self-approved merges or widening note/contact access.
Records and postings
| Stage | Records | Effect |
|---|---|---|
| 1 Configure lead policy | LeadSourcesLeadSettingsConsentEvents | Retain the stated outcome and its source evidence |
| 2 Capture and deduplicate | LeadsDuplicateClustersLeadNotesDuplicateMembers | Retain the stated outcome and its source evidence |
| 3 Calculate lead priority | ScoringRunsScoringEventsPriorityAlerts | Retain the stated outcome and its source evidence |
Process reports
All reportsScoring Explanations
Applied score, contributing rules, model version and excluded or expired evidence for each run.
Source Quality
Qualification outcomes by source and scoring-policy version, with unknown outcomes separate.
Duplicate Decisions
Reviewed merges, rejected clusters and the retained survivor references.
Lead Funnel
Lead intake through independent qualification and acknowledged CRM conversion by source.
Follow-up Aging
Open alerts and due activities by permitted owner and territory.
Contact Policy Audit
Channel and purpose decisions, withdrawals and blocked outreach outcomes.
Assignment Coverage
Eligible owner coverage, unmatched leads and dated reassignment reasons.
Run by an agent
Agent support
An agent acts within the current user or service scope. It cannot provide its own independent human approval, restore a withdrawn contact purpose or turn an unknown external response into a confirmed result.
# Example after configuration
$ curl -fsSL https://www.erp.ai/skill.md | paste into your agent
› capture and prioritize leads · configure lead policy on LeadSources, LeadSettings, ConsentEvents
✓ Define acquisition sources, permitted contact purposes and qualification criteria.
› capture and prioritize leads · capture and deduplicate on Leads, DuplicateClusters, LeadNotes, DuplicateMembers
✓ Capture stable source identifiers and preserve the acquisition evidence.
› capture and prioritize leads · calculate lead priority on ScoringRuns, ScoringEvents, PriorityAlerts
✓ Evaluate the approved policy against an exact lead revision.