Every dial floor collects duplicates. A homeowner fills out a web form, then calls in, then gets knocked by a canvasser two weeks later. A purchased list overlaps with last year's storm list. A setter types "Jon" on Monday and another types "John" on Thursday. None of this is anyone's fault, and most of it is unavoidable once you have more than one lead source.
The damage doesn't come from the duplicate itself. It comes from how it gets cleaned up. Someone spots two rows for the same address, deletes the "older" one, and with it goes a porch note, a dated callback, and the setter who actually booked the first estimate. The homeowner gets a cold intro call from a rep who doesn't know they already got a quote. Credit gets argued about on Friday.
This post is a simple weekly routine for merging duplicate leads so nothing useful is lost: notes stay, ownership is clear, sourced-by credit is preserved, and the merged lead ends up with exactly one next call date.
Prevention helps, but you will still need a merge routine
The best fix for duplicates is catching them at entry, and we covered that in how to avoid duplicate leads across door and dial. Searching by phone and address before creating a row, normalizing phone formats, and using one shared list instead of private spreadsheets will stop most of them.
But prevention never gets to zero. List imports, typos, a spouse's cell number, a homeowner who moved and gave a new address: some duplicates will slip through. That's why the floor also needs a short, regular merge pass with rules everyone agrees on in advance. Merging is a judgment call, and judgment calls made under pressure at 4:45 p.m. on a busy day are where notes get lost.
What a "duplicate" actually means on a dial floor
Before anyone merges anything, agree on what counts. Not every match is the same lead.
- Same person, same property. Same phone or same address and same name. This is a true duplicate and should be merged.
- Same property, different person. Two spouses, or a landlord and a tenant. Often one lead with two contacts, not two leads. Merge into one lead and keep both phone numbers labeled.
- Same person, different property. A homeowner with a rental or a cottage. These are two separate opportunities. Don't merge; link them in the notes.
- Same phone, different everything. A recycled number or a bad list row. Not a duplicate. Mark the stale row as wrong number and move on.
Writing these four cases down takes five minutes and prevents most bad merges. When in doubt, the rule is simple: don't merge, flag it for the team lead.
The five things a merge must keep
When two rows become one, these are the fields that most often get lost. A merge isn't done until all five are accounted for.
1. Every note, in date order
Notes are the most valuable thing on a lead and the easiest to lose. Don't pick the "better" set of notes. Combine them, oldest first, with the date and the setter's name on each one. If the notes conflict (one says "not interested," a later one says "call back in March"), the later dated note wins for next steps, but the earlier one stays visible. A rep calling in March should know there was a "no" in October.
2. One owner
Two rows usually means two setters touched the lead. The merged lead needs one current owner, the person responsible for the next call. A fair default: the setter with the most recent meaningful conversation owns it. "Meaningful" means a real conversation logged with an outcome, not a voicemail. If both reps had real conversations, the team lead picks, and writes down why.
3. Sourced-by and booked-by credit
Ownership and credit are different things. The setter who owns the next call isn't always the one who generated the lead or booked the first appointment. Keep the original lead source (web form, canvass, referral, list) and the original booked-by setter on the merged lead, even if someone else owns it now. If you run spiffs, this is where merge mistakes turn into payroll arguments. Our post on attributing books versus closes fairly covers the credit rules; the merge routine just has to keep the data those rules depend on.
4. Exactly one next call date
Two rows often means two callbacks: one setter set a follow-up for Tuesday, another for next month. After the merge there should be one. Keep the date that matches the latest real conversation, and delete the other. Two live dues on the same homeowner means two calls in one week, and that's how you annoy someone who was ready to buy.
5. Appointment history
If either row had a booked, confirmed, showed, or no-show appointment, keep it on the merged lead. An estimator walking in should know this is the second visit. A setter calling should know there was a no-show before. Appointment history also keeps your show-rate and close-rate numbers honest; merging away a no-show quietly inflates them.
A 20-minute weekly merge routine
You don't need a data team for this. One person, usually the floor lead or ops manager, can run it once a week. Friday afternoon or Monday morning both work. If you already run a Friday call log cleanup, add this as one more step.
Step 1: Pull likely duplicates (5 minutes). Sort or filter by phone number, then by street address. Look for exact matches and near matches (same street number and name with different spelling). If your tracker flags possible duplicates, start with that list.
Step 2: Classify each match (5 minutes). Use the four cases above. True duplicate, same property with two contacts, separate opportunity, or bad row. Anything unclear goes into a "check with team" pile rather than getting merged on a guess.
Step 3: Merge true duplicates (8 minutes). For each one, combine notes in date order, set one owner, keep sourced-by and booked-by, keep one next call date, and keep appointment history. Add a short note on the merged lead: "Merged from duplicate row on Nov 22 — kept notes from both, owner set to Maya (latest conversation)." That one line saves an argument later.
Step 4: Tell the affected setters (2 minutes). If a setter lost ownership of a lead in the merge, tell them, either in standup or a quick message. Nobody should discover on Tuesday that their callback disappeared.
That's it. Twenty minutes a week keeps the list clean enough that setters trust it, which matters more than any single merge.
Common merge mistakes to avoid
- Deleting instead of merging. The fastest way to clean a list is also the fastest way to lose the note that said "wife makes the decision, call after 6."
- Keeping the newest row by default. Newer isn't better. The older row often has the real conversation; the newer one is a list re-import with nothing on it.
- Letting setters merge their own leads. It feels efficient, but it invites ownership grabs, even unintentional ones. One person running merges with written rules is fairer.
- Merging across campaigns without tagging. If a storm lead and a promo lead merge, keep both campaign tags so your reporting still shows where the lead came from.
- Forgetting do-not-call status. If either row was marked do not call, the merged lead is do not call. Always. This is a compliance issue, not a preference.
- Merging in the middle of a dial shift. Leads move while setters are on the phone. Run merges when the floor is quiet.
How merges fit into list hygiene
Duplicate merging is one part of a bigger habit: keeping the list worth dialing. Dead numbers, stale do-not-call flags, and wrong zip codes all drag down conversation rates in the same way. If you're building that habit from scratch, our guide to list hygiene for cold-calling teams walks through the rest of it.
The payoff isn't a prettier spreadsheet. It's that a setter can open a lead, read its whole history in thirty seconds, and make a call that sounds like the company remembers the homeowner. That's worth more than any script tweak.
Start with the template, or let the tracker do the heavy lifting
If your team is still running on spreadsheets, start with our free call log template. It has the columns this routine depends on: setter, lead source, outcome, notes, and next call date. Add a "merged from" column and you can run the weekly routine today.
When the spreadsheet starts to strain, Dialed Sales gives each rep their own seat, keeps notes and outcomes tied to the lead, and shows one due queue for who to call next, so merges are rarer and cleaner when they do happen. You can try it free with your own floor and see whether it fits how your team already works.