Deduplicate Leads Across Branches Without Deleting Legitimate Repeat Enquiries

Duplicate records and repeat customers are not the same thing

A person can submit the same form twice because the page stalled, enquire about two branches, return months later for a new service, or be referred by a family member using the same phone number. Automatically deleting every matching phone number may reduce the CRM count while destroying valid sales history.

Define the entity before defining the duplicate

Use separate identifiers for:

• Person or organisation: who is enquiring, if reliably identified.
• Enquiry: one request for a specific service or need.
• Branch assignment: the team responsible at a given time.
• Interaction: each call, form, message or appointment event.

Two branch records for one enquiry may need to merge into one enquiry with two routing events. Two enquiries from one person may need to remain separate if they concern different services or occur at different times.

Use tiers of match confidence

High confidence: same source submission ID or idempotency key; same enquiry timestamp window and same request. Merge or suppress duplicate ingestion automatically if the business has validated the rule.

Medium confidence: same normalised phone/email, same service and close submission times. Place in a review queue; do not delete automatically.

Low confidence: shared household number, incomplete details, different service, or a long time gap. Keep separate until an authorised reviewer decides otherwise.

These tiers are a suggested internal policy, not a universal CRM standard. Define time windows from real submission behaviour and audit them before automation.

Preserve attribution through a merge

When two records are merged, retain original source, campaign, branch page, first-touch and latest-touch fields, plus a link to the surviving record. If a lead transfers from branch A to branch B, log the transfer as an assignment event; do not rewrite the original source to make branch B appear to have generated it.

This distinction matters when importing qualified leads into advertising platforms. Google Ads' offline conversion guidance emphasises consistent conversion actions and provides deduplication rules for supported uploads; your CRM still needs its own identity policy before sending data. See the offline conversion FAQ.

Test with a labelled sample

Take a recent sample and label pairs as duplicate, same person/new enquiry, branch transfer, or uncertain. Compare your automated matching result with human review. Measure false merges as carefully as duplicate reduction. A high merge rate is not a success if it erases legitimate demand.

Operating safeguards

Restrict who can merge records, retain a reversible audit trail, and avoid exposing customer data in shared spreadsheets. Agree on a retention period and the fields needed for matching. Where a customer asks not to be contacted, ensure suppression status survives merges and transfers.

Success measures

Track duplicate ingestion rate, false-merge rate, review-queue age, transfer rate and downstream conversion reconciliation. The purpose is one trustworthy view of each enquiry—not one permanent record per phone number.