Lead Management, Imports, and Prospecting for Sales Teams

Campaign quality begins before the first call. A lead record needs enough provenance and context for a team to decide whether contact is appropriate and what a useful conversation would be.

Use this guide to design an approved workflow, test it on a defined segment, and let the next qualified action—not raw activity—decide what to change.

Map fields before importing

Define email, phone, account, owner, source, time zone, consent context, and lifecycle stage before a CSV enters the system; unknown data should remain visibly unknown.

• Map source and owner fields before import. (map fields before importing)
• Flag duplicate records for review. (map fields before importing)
• Keep consent context visible on the lead. (map fields before importing)

Deduplicate with a review path

Use matching rules to identify likely duplicates, but give an operator a way to resolve ambiguous records rather than silently merging valuable context.

• Map source and owner fields before import. (deduplicate with a review path)
• Flag duplicate records for review. (deduplicate with a review path)
• Keep consent context visible on the lead. (deduplicate with a review path)

Segment on fit and readiness

Build segments from ICP, source, role, engagement, and explicit exclusions. Avoid treating enrichment guesses as confirmed facts.

• Map source and owner fields before import. (segment on fit and readiness)
• Flag duplicate records for review. (segment on fit and readiness)
• Keep consent context visible on the lead. (segment on fit and readiness)

Preserve data responsibility

Your team remains responsible for the accuracy and lawful use of imported data. Capture corrections and suppressions where operators can audit them.

• Map source and owner fields before import. (preserve data responsibility)
• Flag duplicate records for review. (preserve data responsibility)
• Keep consent context visible on the lead. (preserve data responsibility)