Approve a scoring policy
Approve a scoring policy.
4 stages · 1 approval
Roles and responsibilities
-
Step 1Configure lead policy
Consent NumberLeadChannelDecisionPhone
-
Step 2Approve scoring model
Rule CodeNameVersionCategoryDemographic
-
Step 3Calculate lead priority
Run NumberLeadRule ScoreApplied Score
-
Step 4Review funnel quality
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.
Approval required
Approve scoring model
Marketing Operations submits immutable rule and optional model versions with permitted features, point caps and expiry windows. Admin independently approves the prepared version before its effective time. Protected feature exclusions are enforced before any model request; model suggestions do not make qualification decisions.
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.
Review funnel quality
Compare qualification and acknowledged conversion outcomes with the policy version that prioritized each lead. Distinguish missing outcomes from rejected leads. Marketing Operations proposes a new rule version rather than changing historic score explanations; validate it against representative records before approval.
Approvals and controls
1 approval required in this process
-
Approve scoring model
Admin signs · calculate lead priority waits
ScoringRules, ScoringRuleValues, ScoringModels - 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.
Explainable lead scoring. A scored lead displays the rules and evidence contributing to its rank. Repeated, expired or reversed evidence cannot inflate the score.
AI-assisted prioritization. A model suggestion is traceable to its version and scoring run. Reject disallowed features, unapproved models and automatic SQL decisions.
Records and postings
| Stage | Records | Effect |
|---|---|---|
| 1 Configure lead policy | LeadSourcesLeadSettingsConsentEvents | Retain the stated outcome and its source evidence |
| 2 Approve scoring model | ScoringRulesScoringRuleValuesScoringModels | Record an independent decision on the submitted revision |
| 3 Calculate lead priority | ScoringRunsScoringEventsPriorityAlerts | Retain the stated outcome and its source evidence |
| 4 Review funnel quality | ScoringRunsLeadsLeadAssignmentsPriorityAlerts | Retain the stated outcome and its source evidence |
Process reports
All reportsLead Funnel
Lead intake through independent qualification and acknowledged CRM conversion by source.
Scoring 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.
Assignment Coverage
Eligible owner coverage, unmatched leads and dated reassignment reasons.
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.
Conversion Reconciliation
Pending, unknown and failed CRM handoffs with original request references.
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
› approve a scoring policy · configure lead policy on LeadSources, LeadSettings, ConsentEvents
✓ Define acquisition sources, permitted contact purposes and qualification criteria.
› approve a scoring policy · approve scoring model on ScoringRules, ScoringRuleValues, ScoringModels
⏸ approval · waiting for the admin
# 2 more stages after approval: calculate lead priority, review funnel quality