Source Quality
Qualification outcomes by source and scoring-policy version, with unknown outcomes separate.
Route and qualify prospects
Route and qualify prospects.
3 stages · 1 approval
Roles and responsibilities
-
Step 1Route the lead
Record NumberLeadAssigned ToAssigned From
-
Step 2Work the lead
Activity NumberSubjectLeadOwner
-
Step 3Review qualification
Lead NumberCompanyOwnerAssigned AE
Process steps
Follow the process from start to finish. Select a step to see who acts and what changes.
Route the lead
Submit new routing rules for independent Admin approval. Apply approved rules by explicit priority and deterministic ties. Choose an active eligible owner in the territory with an atomic round-robin cursor; otherwise retain an unassigned lead. Every initial assignment or reassignment appends LeadAssignments with its reason.
Work the lead
Contact only through permitted channels, record meetings with bounded start and end times and update the follow-up outcome. An acknowledged priority alert does not qualify its lead. Withdrawing a contact purpose blocks new outreach even when a list membership or previous score remains active.
Approval required
Review qualification
The SDR submits qualification evidence and an eligible AssignedAE using Status: MQL → Submitted. That AE independently accepts the handoff into SQL or returns it to Working with a reason. The decision checks the same revision, current contact policy and territory assignment; a score alone cannot mark a lead SQL. Record QualificationSubmittedBy at submission and require it to differ from QualifiedBy, even after reassignment.
Approvals and controls
1 approval required in this process
-
Review qualification
Account Executive signs · closes the process
Leads - 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.
Engagement tracking. A completed interaction appears on the lead and eligible score explanation. Reject duplicate imported events or treating an open pixel as qualification.
Territory routing. A permitted lead receives one eligible owner and an assignment history entry. Concurrent routing cannot allocate twice or choose an inactive user.
Records and postings
| Stage | Records | Effect |
|---|---|---|
| 1 Route the lead | RoutingRulesLeadAssignmentsLeads | Retain the stated outcome and its source evidence |
| 2 Work the lead | LeadActivitiesLeadNotesListMembershipsPriorityAlerts | Retain the stated outcome and its source evidence |
| 3 Review qualification | Leads | Record an independent decision on the submitted revision |
Process reports
All reportsLead Funnel
Lead intake through independent qualification and acknowledged CRM conversion by source.
Assignment Coverage
Eligible owner coverage, unmatched leads and dated reassignment reasons.
Follow-up Aging
Open alerts and due activities by permitted owner and territory.
Duplicate Decisions
Reviewed merges, rejected clusters and the retained survivor 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
› route and qualify prospects · route the lead on RoutingRules, LeadAssignments, Leads
✓ Submit new routing rules for independent Admin approval.
› route and qualify prospects · work the lead on LeadActivities, LeadNotes, ListMemberships, PriorityAlerts
✓ Contact only through permitted channels, record meetings with bounded start and end times and update the follow-up outcome.
› route and qualify prospects · review qualification on Leads
⏸ approval · waiting for the account executive