Duplicate Check in a VICIdial Drop List

Repeat droppers are normal. A caller who hangs up in your queue once will often ring back and hang up again before you reach them. Run a Drop List on a schedule and, without protection, that one person becomes two leads, then three, and your agents end up calling the same number over and over. The Duplicate Check setting is what stops that.

It is a single field on the Drop List with three choices, and it decides whether a gathered drop gets inserted or skipped based on whether that phone number is already present. The default is the one that surprises people, so it is worth understanding all three.

The three settings

NONE is the default. It does no duplicate checking at all, so every qualifying drop is inserted as a new lead even if that exact number is already in the target list. Run a job often enough on a stubborn caller and NONE will happily insert them repeatedly.

LIST checks for duplicate phone numbers within the leads already in the specified target list. If the number is already there, the new drop is skipped. This is the setting most operators actually want, since it keeps the callback list clean of repeats.

LIST_CAMPAIGN_LISTS widens the check to every list assigned to the campaign that the target list belongs to. If the number exists in any of those lists, the drop is skipped. Use this when a caller might already be a lead somewhere else in the same campaign and you do not want to dial them from two files at once.

How the check decides

flowchart TD
  A[Drop gathered] --> B{Duplicate Check setting?}
  B -->|NONE| C[Insert as new lead]
  B -->|LIST| D{Number in target list?}
  B -->|LIST_CAMPAIGN_LISTS| E{Number in any campaign list?}
  D -->|Yes| F[Skip]
  D -->|No| C
  E -->|Yes| F
  E -->|No| C

The chart shows the branch each drop takes. NONE goes straight to insert. LIST and LIST_CAMPAIGN_LISTS both run a lookup first and only insert when the number is not already found, the difference being how wide they look. The matching is by phone number, so the same caller from a different number still slips through as a distinct lead.

Choosing the right scope

Pick LIST when the callback list stands alone and you just want to avoid re-inserting the same number into it. Pick LIST_CAMPAIGN_LISTS when the same caller could already be a Lead in another file under the same campaign, and you want to avoid the awkward situation of two agents working the same person. The wider check costs a little more lookup time but prevents cross-list double-dialing.

This is the same family of Duplicate check logic you meet when loading leads from a file, just applied automatically to gathered drops. If the broader idea is new to you, duplicate checking on load walks through the wider set of options, including campaign-wide and system-wide scopes.

Why repeat-calling a dropper matters

Beyond wasted agent time, dialing the same person several times a day is the kind of behavior that draws complaints and regulatory attention. Recovering a dropped caller once is a service; calling them five times because your Drop List kept re-inserting them is harassment. Each recovered Lead should appear once, get worked once, and then follow your normal callback and DNC (do not call) rules.

For the full set of Drop List fields and where dedup fits the lead workflow, see the lists and leads guide.

Keep your callback list clean by default

Duplicate Check is a small setting that saves you from a lot of bad calls. On VICIfast you control every Drop List field on a dedicated box provisioned in under 40 seconds. See our pricing to start.