Link Leads Blog · November 9, 2026

How to divide an aged insurance lead list among multiple agents without double-dialing

A batch you buy once doesn't come pre-split by producer. Hand the same CSV to four agents and every one of them inherits the whole file — and the same cell number gets called by two or three different people before anyone notices.

Why the overlap happens on an aged list specifically

A live-transfer lead arrives pre-assigned — the platform routes the call to one agent the moment it connects, so ownership is built into the delivery. An aged batch has no equivalent. It's one CSV, deduplicated against itself, delivered once to whoever placed the order. Nothing in the file says "agent A's leads" versus "agent B's leads." If a sales manager loads the same export into four separate dialer accounts or four separate CRM logins so everyone can get started the same afternoon, every agent now owns the entire batch. The file's own internal dedupe — one row per phone number — does nothing to stop four different people from dialing that same row four separate times in one week, which is also roughly when the first annoyed callback or opt-out comes in.

Three ways to actually split it

Sequential split. Sort the file however it arrived and cut it into equal blocks — the first quarter to agent one, the second quarter to agent two, and so on. No overlap, no judgment calls, and it works on any file regardless of what's in it. The tradeoff is that it ignores anything about the agents themselves: a bilingual producer and a multi-state-licensed one both get a random slice instead of the slice that fits them.

Geographic split. Assign states or ZIP ranges to each agent instead of row ranges. This keeps a producer licensed in only some states on the right subset, and lets someone who knows a market work it specifically. The catch: states don't carry equal record counts, so a geographic split usually needs a second pass that rebalances by volume within each agent's assigned states, not just by state count.

Capacity-weighted split. Don't split evenly across agents — split proportional to how many dials or texts each one can realistically clear inside the campaign window. A full-time agent running a power dialer clears a lot more volume per day than a part-time producer working manually, and an even split just means the slower agent is still working week-one leads while the faster one has moved on to a second batch.

Whichever method fits the team, the rule that matters most is simpler than any of the three: pick one method, run the split once, and never let the same record exist in two agents' active working files at the same time.

Lock the split before it leaves the spreadsheet

Splitting a CSV into separate files is the easy part. The gap opens the moment those files load into separate dialer or CRM accounts with no shared record of who owns what. Add an owner column — agent name or ID — to every row before the split, and keep the whole batch in one shared CRM or dialer list with that field intact, rather than four disconnected spreadsheets that nobody but the sales manager can see. A phone-number lookup should always return who's actually working that record, not just who was handed it on day one.

If the team runs on separate individual dialer logins instead of one shared platform, a master spreadsheet with an owner column is the only thing standing between a clean split and a double-dial. Treat that sheet as the source of truth, and check it before anyone manually adds a number to their own list that didn't come through the split.

What happens when a record needs to move

Agents don't clear their slice at the same rate. Someone finishes a lighter geographic assignment early, or takes a day off mid-campaign, and the remaining records need to move to someone still working. When that happens, update the owner field on the shared record — don't copy it into a new agent's spreadsheet while leaving the old entry untouched, which just recreates the overlap you split the list to avoid. This is the same principle behind a clean disposition-code system: a record's status and its current owner should live in one place, not in whichever file someone happens to have open that day.

Reassigning unworked records is fine at any point in the campaign. Reassigning a record someone already called or texted days ago, without flagging that history to the new owner, just produces the same wasted contact attempt — and it reads worse to the lead the second time, since now a different stranger is calling about the same thing.

A worked example

Take a 10,000-lead batch split across four agents: two full-time, two part-time. A flat 2,500 each ignores how fast each person actually works. A full-time agent clearing roughly 300 dials a day on a power dialer finishes a 2,500-record slice in about eight working days; a part-time producer managing 80–100 dials a day needs closer to three weeks for the same slice. Split by capacity instead: roughly 3,400 records to each full-timer and 1,600 to each part-timer, and all four finish in close to the same window — instead of two agents idle in week two while the other two are still working week-one leads.

This is separate from the vendor's resale rest

Worth keeping distinct: dividing a batch across your own team has nothing to do with the resale rest a vendor applies before the same record can be sold to a different buyer. That clock protects you from accidentally re-buying leads you already own on a reorder — see how to reorder without buying the same record twice — but it says nothing about which of your own agents is allowed to work which number this week. Keep the two systems separate: one tracks what the vendor already sold you, the other tracks who on your team currently owns it.

Build the list, then split it

None of this matters without a clean batch to divide in the first place. Link Leads sells SMS and email lead lists at a flat $0.012 per lead (monthly plans run $0.01/lead), minimum order 5,000 leads, filterable by state and the 18–64 age band, deduplicated and delivered as an instant CSV. Build an order in the order builder, or pull a free 100-row sample first to test an owner-field split on your own CRM before committing a full batch to the team.

These are aged data leads (not consented insurance-form leads) and are not DNC-scrubbed. Buyers are responsible for DNC scrubbing and dialing/texting compliance.