A phone number may be shared by branches, related brands, a call center, answering service, franchise group, or data error. An address may be a real staffed location, coworking site, registered office, mailbox, or virtual office. Neither field alone proves that two business records represent the same prospect.

VISUAL LESSON

What you will learn

  1. 01Classify shared phone and address patterns.
  2. 02Build an evidence-based relationship map.
  3. 03Apply campaign-level merge rules safely.
Several business records sharing one phone hub and one building address separate through evidence checks into verified, review, and exclude paths
Shared contact points require a relationship map before they can support a merge or assignment decision.

ILLUSTRATIVE WORKED EXAMPLE

Resolve an illustrative 20-record collision cluster

Records in clusterIllustrative review
20
Distinct operating businessesIndependent evidence
12
Related locations or brandsPreserved hierarchy
5
UnresolvedManual review
3
Illustrative example—not a benchmark. Replace every sample value with your own campaign, market, and measurement data.

PRACTICAL INTERFACE MAP

Investigate a shared-contact collision

Cluster01Group without merging

Collect records sharing normalized phone, address, suite, domain, name, or provider and preserve their original IDs and sources.

Evidence02Map the relationship

Compare official sites, location pages, legal names where appropriate, domains, phone context, suites, categories, ownership disclosures, and dates.

Decision03Apply the campaign account rule

Choose separate, parent-location link, alias, duplicate merge, service-provider relationship, exclude, or unresolved; preserve reason and approver.

Conceptual walkthrough. Labels, controls, and availability can vary by account, region, plan, and interface version; verify the current screen before acting.

STEP-BY-STEP LESSON

Shared field cluster → independent evidence → relationship map → campaign decision

ClusterDo not merge yet
ResolveEntity and location
DecideSeparate, link, merge

THE LEAD ATLAS METHOD

Lead Atlas Data can research a campaign-specific business-contact list by market, locations, and categories while preserving shared-phone and address ambiguity for transparent review instead of unsafe merging.See how custom list research works ↗
01

Define the campaign's prospect unit

Decide whether one prospect means a legal entity, brand, franchisee, operating company, property, branch, practitioner, or service location. Document when related locations should remain separate and when a parent relationship matters.

Duplicate detection cannot be correct without this unit. The same two rows may be duplicates for corporate procurement but distinct prospects for a territory service.

02

Build collision clusters without merging

Normalize phones with country context and extensions, and parse addresses into country-aware components while preserving raw values. Group possible collisions by phone, address, suite, domain, name, and source, but keep all record IDs and outreach history intact.

A switchboard, answering service, headquarters number, coworking reception, building phone, or virtual-office provider can create legitimate shared values across unrelated or related businesses.

03

Collect independent public evidence

Review official websites, contact and location pages, footer identities, directories linked from the official site, public registries where appropriate, map context, phone labels, suite details, categories, ownership disclosures, and access dates.

Classify an address as staffed operating location, registered office, shared workspace, mailbox, service area, headquarters, branch, historical, or unknown only when evidence supports it. Do not use one platform's eligibility rule as universal legal proof.

04

Map the relationship and confidence

Create nodes for entities, brands, operators, locations, domains, phones, and addresses, with dated source edges. Score strong and weak evidence separately and send contradictions to a reviewer.

Choose separate entities, parent-location relationship, verified alias, likely duplicate, shared provider, excluded record, or unresolved. Never transfer opt-outs, notes, ownership, or contact details across rows until the relationship is verified.

05

Apply and audit the decision

Merge only at the defined campaign unit, retain aliases and provenance, redirect downstream references safely, and reconcile counts before and after. Sample both merged and separated decisions, especially clusters with shared phone or workspace addresses.

Deliverable: prospect-unit definition, raw and normalized fields, collision report, source ledger, entity-location graph, confidence rules, decision reasons, approver, merge and split audit, preserved suppressions, exception queue, and recheck date.

LEAD ATLAS WORKBOOK

Turn this lesson into a research brief.

Apply “Shared Phone Numbers and Virtual Offices: Resolve B2B Identity Before Merging” to one campaign before requesting or using a list.

  1. 01Market boundary

    Name the locations and business categories this decision applies to.

  2. 02Fit evidence

    Write the public signals that would make a business relevant enough to review.

  3. 03Exclusions

    List the business types, markets, and records that should not enter the campaign.

  4. 04Outreach use

    State who will review the list, personalize the message, and record outcomes.

THE TAKEAWAY

Use shared phones and addresses as relationship signals, not deterministic keys; preserve every entity and location, collect independent evidence, and merge only when the campaign's account rule is satisfied.

OFFICIAL REFERENCES

Check the platform’s current instructions.

Platform labels, eligibility, and workflows can change. These official help pages were used to validate this lesson.