Start with the operating decision
Qualify Prospect Sources Before Enrichment begins with a bounded question: decide whether a source may populate approved CRM fields or should remain a research lead. For this workflow, write that question on the prospect source qualification queue before anyone edits a record or sends a message.
Qualify Prospect Sources Before Enrichment treats a notification, import, or vendor file as an input rather than proof. For this workflow, the accountable owner should be able to trace source URL, publisher identity, observed date, stated coverage, account match, field-level evidence, and reviewer disposition and see which fact remains unknown before trying to decide whether a source may populate approved CRM fields or should remain a research lead.
Define the evidence packet
Qualify Prospect Sources Before Enrichment uses a compact evidence packet. For this workflow, capture source URL, publisher identity, observed date, stated coverage, account match, field-level evidence, and reviewer disposition. Preserve the source wording beside normalized values so later reviewers can reconstruct the decision.
Qualify Prospect Sources Before Enrichment keeps every material conflict visible. For this workflow, consider this concrete case: a directory lists a headquarters address copied from an older acquisition page while the company site shows a different legal entity. Retain both observed states and the person responsible for resolving the difference.
Separate preparation from judgment
Qualify Prospect Sources Before Enrichment assigns repeatable preparation to the support role. For this workflow, the assistant may gather source URL, publisher identity, observed date, stated coverage, account match, field-level evidence, and reviewer disposition, apply documented codes, and prepare the prospect source qualification record, while policy exceptions remain with the named owner.
Qualify Prospect Sources Before Enrichment does not turn silence into permission. For this workflow, missing evidence that blocks the decision to decide whether a source may populate approved CRM fields or should remain a research lead receives an explicit unknown state, a next check, and a review deadline.
Use the related specialist service as a starting point for scope and evidence.
Run the workflow in controlled stages
Qualify Prospect Sources Before Enrichment moves through capture, verification, decision, and reconciliation. For this workflow, for prospect source qualification, each stage has an entry condition tied to source URL, publisher identity, observed date, stated coverage, account match, field-level evidence, and reviewer disposition, a completion signal, and a return path for incomplete work.
Qualify Prospect Sources Before Enrichment limits the first pass to decisive facts. For this workflow, check the evidence most capable of resolving whether to decide whether a source may populate approved CRM fields or should remain a research lead before spending time on optional enrichment or formatting.
Handle exceptions without losing lineage
Qualify Prospect Sources Before Enrichment uses named exception codes. For this workflow, the highest-risk exception is when an archived or syndicated page is mistaken for a current first-party source. Give that condition a stop state, named reviewer, and evidence requirement rather than routing it through a generic error queue.
Qualify Prospect Sources Before Enrichment records temporary work safely during an outage. For this workflow, issue a prospect source qualification key that can later reconcile source URL, publisher identity, observed date, stated coverage, account match, field-level evidence, and reviewer disposition; restrict storage, log every action, and compare the temporary record with the recovered system.
FTC: CAN-SPAM compliance guide provides public guidance that can help test workflow assumptions.
Review quality with a useful sample
Qualify Prospect Sources Before Enrichment reviews a risk-weighted sample. For this workflow, include the scenario where a directory lists a headquarters address copied from an older acquisition page while the company site shows a different legal entity, plus recent exceptions and manual overrides, rather than checking only easy prospect source qualification completions.
Qualify Prospect Sources Before Enrichment measures acceptance rather than motion. For this workflow, track the share of sampled fields reproducible from their recorded URLs. Explain the denominator and preserve rejected records so improvement is not created by hiding difficult cases.
Protect people and communication rights
Qualify Prospect Sources Before Enrichment applies approved privacy and outreach controls. For this workflow, collect only the parts of source URL, publisher identity, observed date, stated coverage, account match, field-level evidence, and reviewer disposition needed to decide whether a source may populate approved CRM fields or should remain a research lead; restrict access, honor suppressions, and keep sensitive evidence out of free-text notes.
Qualify Prospect Sources Before Enrichment sets a firm operating boundary. For this workflow, never convert a plausible inference about headcount, revenue, or ownership into a verified fact. Route uncertainty to the reviewed prospect source qualification path before any external action is taken.
Close with an auditable handoff
Qualify Prospect Sources Before Enrichment ends with a clear disposition. For this workflow, record whether the team can decide whether a source may populate approved CRM fields or should remain a research lead, plus the owner, evidence links, the share of sampled fields reproducible from their recorded URLs, unresolved limits, next review date, and reversal condition.
Qualify Prospect Sources Before Enrichment supports the decision to decide whether a source may populate approved CRM fields or should remain a research lead. For this workflow, a reviewer should be able to reconstruct the prospect source qualification result from source URL, publisher identity, observed date, stated coverage, account match, field-level evidence, and reviewer disposition without relying on private memory.
Common questions
Who owns exceptions in prospect source qualification?
The named accountable owner decides policy exceptions; support staff prepare the evidence and route the record.
What should a reviewer inspect first?
Start with the source, observation time, current system state, and the evidence supporting the proposed decision.
When is the workflow complete?
Completion requires a recorded disposition, owner, evidence trail, and reconciliation of any temporary or conflicting state.
Turn the guidance into a controlled role
Bring the workflow, systems, current owner, and known exceptions. We will help shape a focused first handoff.
Plan a consultation