Duplicate Leads in VICIdial: How They Happen and How to Stop Them

Duplicate leads are a quiet tax on a call center. The same person gets dialed twice by two different agents, you look disorganized, and you may be calling someone you already disposed as not interested or do-not-call. The frustrating part is that VICIdial does not deduplicate by default. If you do not tell it to check, it will happily load the same number a hundred times.

The fix is to understand where duplicates come from and to turn on the right checks at the right moment. Almost all of it happens at load time, so that is where most of your prevention lives.

Where duplicates come from

• Loading the same file twice. Re-uploading a lead file you already loaded is the classic source.
• Overlapping vendor files. Two lead vendors sell you the same numbers, and you load both into the same campaign.
• A number that already exists in another list. The phone is fine in its old list, but you import it again into a new one.
• Drop Lists with no dedupe. A recovery Drop list can re-insert the same dropped caller across multiple runs if Duplicate Check is left at NONE.

Catch them at load time

The lead loader has a Lead Duplicate Check option that runs as it imports. You choose the scope: check within the same list only, within all of a campaign's lists, or system-wide across every list. The wider the scope, the more thoroughly it catches dupes, at some cost in load time. There are also options that check only against leads loaded within the last 90 days, which is useful when you intentionally recycle old data but do not want to re-load anything recent. For the full set of choices, see duplicate checking on load.

flowchart TD
  A[Load lead file] --> B{Duplicate Check set?}
  B -->|No check| F[All rows inserted]
  B -->|Within list| C[Compare to this list]
  B -->|Campaign lists| D[Compare to campaign lists]
  B -->|System-wide| E[Compare to all lists]
  C --> G{Match found?}
  D --> G
  E --> G
  G -->|Yes| H[Skip the row]
  G -->|No| I[Insert the row]

Scoping the status, not just the number

You can narrow duplicate checking to specific statuses. This lets you say: only treat a number as a duplicate if the existing copy is in one of these statuses. A related feature, the Status Mismatch Action, handles the in-between case where a lead dupes by phone number but does not dupe against your chosen statuses. You can have those not-quite-duplicate leads moved into the list you are loading, either the most recent occurrence or all of them. It is powerful and it can move a lot of leads at once, so handle it carefully. See the status mismatch action for the mechanics.

Dedupe your Drop Lists too

Load-time checks do not cover leads that arrive through other paths. A Drop List has its own Duplicate Check field: LIST checks within the destination list, and LIST_CAMPAIGN_LISTS widens it to the campaign. Default is NONE, so set it deliberately or you will accumulate repeat callers over time. Each Lead you call should be one real person once, and that discipline starts with every insertion path having a Duplicate check in place. None of this touches your DNC (do not call) obligations, which are a separate filter, but clean dedupe makes those easier to reason about.

Wrap-up

Duplicates are not inevitable. Turn on duplicate checking at load with a scope that matches your operation, dedupe your Drop Lists, and understand the Status Mismatch Action before you flip it. For everything that touches how leads enter your system, start with the VICIdial lists and leads guide.

A managed VICIdial server gives you a clean, properly configured loader so your dedupe settings actually take effect from the first import. New dialers go live in under 40 seconds. See our pricing.