Start with the operating decision
Resolve Duplicate Prospects Before Sequencing begins with a bounded question: decide whether records represent one person, related contacts, or distinct people who must stay separate. For this workflow, write that question on the duplicate prospect resolution queue before anyone edits a record or sends a message.
Resolve Duplicate Prospects Before Sequencing treats a notification, import, or vendor file as an input rather than proof. For this workflow, the accountable owner should be able to trace candidate record IDs, account domain, verified email, source lineage, owner, active sequence, merge decision, and retained evidence and see which fact remains unknown before trying to decide whether records represent one person, related contacts, or distinct people who must stay separate.
Define the evidence packet
Resolve Duplicate Prospects Before Sequencing uses a compact evidence packet. For this workflow, capture candidate record IDs, account domain, verified email, source lineage, owner, active sequence, merge decision, and retained evidence. Preserve the source wording beside normalized values so later reviewers can reconstruct the decision.
Resolve Duplicate Prospects Before Sequencing keeps every material conflict visible. For this workflow, consider this concrete case: two contacts share a name and employer but use different verified addresses after a regional team split. Retain both observed states and the person responsible for resolving the difference.
Separate preparation from judgment
Resolve Duplicate Prospects Before Sequencing assigns repeatable preparation to the support role. For this workflow, the assistant may gather candidate record IDs, account domain, verified email, source lineage, owner, active sequence, merge decision, and retained evidence, apply documented codes, and prepare the duplicate prospect resolution record, while policy exceptions remain with the named owner.
Resolve Duplicate Prospects Before Sequencing does not turn silence into permission. For this workflow, missing evidence that blocks the decision to decide whether records represent one person, related contacts, or distinct people who must stay separate 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
Resolve Duplicate Prospects Before Sequencing moves through capture, verification, decision, and reconciliation. For this workflow, for duplicate prospect resolution, each stage has an entry condition tied to candidate record IDs, account domain, verified email, source lineage, owner, active sequence, merge decision, and retained evidence, a completion signal, and a return path for incomplete work.
Resolve Duplicate Prospects Before Sequencing limits the first pass to decisive facts. For this workflow, check the evidence most capable of resolving whether to decide whether records represent one person, related contacts, or distinct people who must stay separate before spending time on optional enrichment or formatting.
Handle exceptions without losing lineage
Resolve Duplicate Prospects Before Sequencing uses named exception codes. For this workflow, the highest-risk exception is when an automatic merge discards an active owner, suppression, or opportunity relationship. Give that condition a stop state, named reviewer, and evidence requirement rather than routing it through a generic error queue.
Resolve Duplicate Prospects Before Sequencing records temporary work safely during an outage. For this workflow, issue a duplicate prospect resolution key that can later reconcile candidate record IDs, account domain, verified email, source lineage, owner, active sequence, merge decision, and retained evidence; restrict storage, log every action, and compare the temporary record with the recovered system.
FTC: Start with Security provides public guidance that can help test workflow assumptions.
Review quality with a useful sample
Resolve Duplicate Prospects Before Sequencing reviews a risk-weighted sample. For this workflow, include the scenario where two contacts share a name and employer but use different verified addresses after a regional team split, plus recent exceptions and manual overrides, rather than checking only easy duplicate prospect resolution completions.
Resolve Duplicate Prospects Before Sequencing measures acceptance rather than motion. For this workflow, track false merges, false splits, and retained relationship counts in the reviewed sample. Explain the denominator and preserve rejected records so improvement is not created by hiding difficult cases.
Protect people and communication rights
Resolve Duplicate Prospects Before Sequencing applies approved privacy and outreach controls. For this workflow, collect only the parts of candidate record IDs, account domain, verified email, source lineage, owner, active sequence, merge decision, and retained evidence needed to decide whether records represent one person, related contacts, or distinct people who must stay separate; restrict access, honor suppressions, and keep sensitive evidence out of free-text notes.
Resolve Duplicate Prospects Before Sequencing sets a firm operating boundary. For this workflow, never merge merely because normalized names match when identity evidence conflicts. Route uncertainty to the reviewed duplicate prospect resolution path before any external action is taken.
Close with an auditable handoff
Resolve Duplicate Prospects Before Sequencing ends with a clear disposition. For this workflow, record whether the team can decide whether records represent one person, related contacts, or distinct people who must stay separate, plus the owner, evidence links, false merges, false splits, and retained relationship counts in the reviewed sample, unresolved limits, next review date, and reversal condition.
Resolve Duplicate Prospects Before Sequencing supports the decision to decide whether records represent one person, related contacts, or distinct people who must stay separate. For this workflow, a reviewer should be able to reconstruct the duplicate prospect resolution result from candidate record IDs, account domain, verified email, source lineage, owner, active sequence, merge decision, and retained evidence without relying on private memory.
Common questions
Who owns exceptions in duplicate prospect resolution?
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