How Valley Prevents Duplicate Outreach Across Campaigns

Valley's deduplication operates continuously in the background, checking every prospect addition and campaign action against workspace-wide activity.

The Deduplication Check Process:

When any team member attempts to add a prospect to a campaign, Valley executes instant verification: checks prospect's email and LinkedIn URL across all workspace campaigns, identifies any existing or recent contact attempts, verifies territory ownership rules, checks account-level assignment if applicable, and references workspace DNC lists and exclusions.

This check completes in under one second, providing immediate feedback before the prospect enters any campaign.

Deduplication Scope:

Valley tracks prospects across multiple identifiers to catch duplicates even when data varies slightly: LinkedIn profile URL (primary identifier), email address (secondary identifier), full name + company combination (tertiary identifier), and phone number when available.

Example: If Rep A has "john.smith@company.com" in a campaign and Rep B tries to add "j.smith@company.com" at the same company, Valley flags the potential duplicate despite different email formats.

Deduplication Time Windows:

Configure how long prospects remain "locked" after contact: 30-day lockout (aggressive re-engagement allowed), 60-day lockout (moderate restriction), 90-day lockout (standard best practice—Valley default), 180-day lockout (conservative, relationship-focused), or permanent lockout (once contacted, never again unless manually released).

Most B2B teams use 90-day windows: after initial outreach sequence concludes, prospect becomes available for different campaign types after 90 days, allowing re-engagement without appearing spammy.

Status Indicators:

When checking prospects, Valley shows clear status: "Available" (not contacted recently, safe to add), "In Active Campaign" (currently being contacted by colleague), "Recently Contacted" (within lockout window), "Responded Positively" (in active conversation with team member), "DNC List" (explicitly excluded organization-wide), "Territory Conflict" (belongs to different team member's territory).

These indicators provide instant clarity on prospect availability.

Override Capabilities:

Sales managers can override deduplication restrictions when warranted: high-value account requiring multi-threading, different stakeholder at same company (VP vs. Director), significantly different campaign approach or timing, explicit prospect request ("Talk to my colleague about X").

Overrides require manager approval, maintaining control while allowing flexibility.

What Territory-Based Rules Prevent Outreach Conflicts?

Clear territory ownership represents the foundation of duplicate prevention. Valley's territory system ensures prospects automatically route to correct owners.

Geographic Territory Configuration:

Define regional assignments with precision: Rep A: United States and Canada, Rep B: United Kingdom, Ireland, Western Europe, Rep C: Eastern Europe, Middle East, Africa, Rep D: Asia-Pacific, Australia, New Zealand.

Valley uses company headquarters location to assign prospects automatically. Prospect from London routes to Rep B, prospect from Singapore routes to Rep D—no manual assignment needed.

Industry Vertical Territories:

Assign reps to specific industries: Rep A: Financial Services (banking, insurance, fintech), Rep B: Healthcare (providers, payers, life sciences), Rep C: Technology (SaaS, infrastructure, dev tools), Rep D: Professional Services (consulting, agencies, law).

Valley classifies prospect companies by industry and routes accordingly. Prospect from healthcare SaaS company might create conflict—this gets flagged for manager decision.

Company Size Segmentation:

Divide market by employee count or revenue: SDR Team: 10-100 employees (SMB segment), Mid-Market Team: 100-500 employees, Enterprise Team: 500+ employees.

Valley checks company size during prospect enrichment and routes to appropriate team tier automatically.

Named Account Assignment:

Strategic accounts get dedicated ownership: Enterprise AE has 50 named accounts assigned explicitly, any signal from these accounts (any employee, any signal type) routes to that AE immediately, no other team member can contact these accounts without approval.

Valley's named account feature provides air-tight protection for your most valuable relationships.

Conflict Resolution Logic:

When prospects match multiple territory criteria, Valley applies hierarchy: Named accounts override all other rules (explicit assignment wins), Company size segmentation comes second (enterprise accounts to enterprise reps), Geographic territory third (within size segment, geography determines owner), Industry specialization fourth (tie-breaker between reps).

Example: Prospect from 800-person fintech company in New York that's also a named account routes to: Named account owner (rule 1), not enterprise team (would be rule 2), not US geographic owner (would be rule 3), not fintech specialist (would be rule 4).

How Does Valley Handle Account-Level Deduplication?

Individual prospect deduplication prevents messaging the same person twice. Account-level deduplication ensures coordinated engagement across all employees at a company.

Account Locking Mechanism:

When a team member begins engaging a company, Valley can lock that entire account: All employees at ABC Company assigned to Rep A, Rep B cannot add any ABC Company employees to campaigns, Prevents multiple reps contacting different stakeholders uncoordinated, Maintains single point of contact unless multi-threading approved.

This account-level control supports account-based selling strategies.

Multi-Threading Coordination:

For strategic accounts requiring multiple stakeholders engagement, Valley enables coordinated multi-threading: Manager approves multi-threading for specific accounts, Primary owner (AE) coordinates overall strategy, Secondary owners (SDRs) engage specific stakeholders, Valley tracks all activity across stakeholders in one view, Team sees comprehensive account engagement picture.

Example Multi-Threading Scenario:

Enterprise account (500+ employees) evaluated for $200K deal. AE owns relationship with VP Sales (economic buyer), Sales Engineer engages with VP Engineering (technical buyer), SDR reaches out to Director of Sales Ops (champion/influencer).

Valley shows all three threads in unified account view, preventing fourth team member from randomly contacting someone else at the company.

Account-Level Visibility:

Team members see complete account context: Who from our team has contacted this company?, Which employees have been reached?, What responses have we received?, When was last contact?, What's the current deal stage?.

This visibility prevents embarrassing situations where prospects mention "I already talked to your colleague" and the rep has no idea.

Account Reassignment:

When territories change or reps leave, Valley enables bulk account reassignment: Manager selects all accounts in specific territory, reassigns to new owner in one action, all active campaigns and prospect relationships transfer, historical activity preserved for context.

How to Configure Workspace-Wide DNC Lists in Valley?

Do Not Contact (DNC) lists represent the ultimate deduplication—prospects who should never receive any outreach from anyone on your team.

DNC List Categories:

Valley supports multiple exclusion types: Existing customers (don't prospect active accounts), Competitors (organization-wide exclusion), Partners and resellers (maintain channel relationships), Closed-lost deals recent period (avoid premature re-engagement), Explicit opt-outs (respect prospect preferences), Employees and contractors (don't prospect your own people), Legal holds (compliance requirements).

Adding to DNC Lists:

Any team member can add prospects to workspace DNC: Manual addition (one by one), Bulk CSV upload (large lists), Automatic rules (CRM sync for customers), API integration (external systems).

Example: When deal closes in CRM, Valley automatically adds all contacts at that account to "Customers" DNC list, preventing any outreach.

DNC List Transparency:

Team members see why prospects are excluded: "This prospect is on DNC: Existing Customer - Added by Sarah on 2/1/26", "This company is on DNC: Competitor - Added by workspace admin on 12/15/25".

This transparency prevents confusion about why qualified prospects can't be contacted.

Temporary DNC:

Some exclusions should be temporary: Closed-lost deal: DNC for 6 months, then eligible for re-engagement, Unresponsive prospect: DNC for 90 days, then retry with different approach, Timing pushback: DNC until specified date ("contact me in Q3").

Valley supports time-based DNC that automatically expires, making prospects available again at appropriate times.

DNC Overrides:

Occasionally prospects on DNC should be contacted: Customer contact for upsell/cross-sell (different conversation than prospecting), Closed-lost re-engagement after material changes (new use case, product evolution), Explicit prospect request ("I know they're a partner, but they asked me to contact them").

Overrides require documentation explaining rationale, creating audit trail for compliance.