Organizing your team's calling days right (and working through your lead lists)

A list has an expiry date

A freshly imported contact is far easier to reach than one dialed for the sixth time three weeks later. Reachability decays with time and with the number of attempts. Treating a list as non-perishable stock, telling yourself you will get through it eventually, means accepting that its value melts while it waits.

The practical consequence is clear. A list must be sized to be worked through within its freshness window, not stockpiled. If you import more contacts than the team can call while hot, you manufacture waste at the source, before the first call.

Calculate real calling capacity

Before allocating lists, you need to know the team's real capacity, not the theoretical one. It comes from three elements:

• Effective calling hours per SDR per day. Rarely more than 4 to 5 hours of net dialing once prep, call reports and breaks are removed.
• Contacts workable per hour, which depends on connection rate and average exchange duration.
• The number of SDRs actually available in the window, net of leave and training.

The product of the three gives the volume of contacts the team can call while hot over the period. It is that number, not optimism, that should drive list imports.

An illustrative worked example

Take a fictional team of 5 SDRs. Each does 4 hours of net dialing a day and works 15 contacts per hour, so 60 contacts per day per SDR. Over a 5-day week, that is 60 times 5 times 5, or 1,500 contacts callable while hot. These numbers are invented, they only serve to set up the reasoning.

Importing a 3,000-contact list for that week guarantees half will go cold before being called. The right decision is to import around 1,500 contacts, or to add capacity if the list is valuable. The calculation avoids the most common mistake, importing on optimism then noticing the waste a month later.

Align calling windows with the target

Not all hours are equal. Depending on the target, SMB owners, support functions, independent professionals, reachability windows differ sharply. Smart staffing concentrates capacity on the slots where the target picks up, rather than spreading effort evenly across the day.

This alignment often does more for connection rate than a list change. Calling the right target at the wrong time is like calling a dead list. For each target type, document the slots that pick up, and make it a staffing rule rather than an individual hunch.

Steer the inventory continuously

Staffing is not a start-of-month decision frozen for thirty days. It is continuous steering. A list depleting faster than expected, an absent SDR, a connection rate dropping on one list, each of these events should reallocate capacity in real time. Without consolidated visibility on list status and SDR activity, these trade-offs are made by guesswork.

This is where measurement helps. Tracking each list's completion rate, its reachability and remaining capacity lets you decide each morning where to send effort, and which lists to set aside before they burn hours. Here are the indicators to keep in view:

• Each list's completion rate, to spot the ones dragging and going cold.
• Reachability per list, to set aside in time the lists that no longer pick up.
• The team's remaining capacity in the window, to size the next import.
• The average number of attempts per contact, to avoid exhausting a list by over-dialing it.

The most expensive staffing mistakes

• Importing on theoretical rather than real capacity, and letting the surplus go cold.
• Spreading calls across the whole day without regard for the slots where the target picks up.
• Keeping a tired list by dialing it again, instead of setting it aside and moving to fresh.
• Freezing staffing at the start of the month and never reopening it despite absences and reachability drops.

Pace your follow-ups without exhausting the list

A contact is almost never reached on the first call, but dialing them ten times only burns time and scorches the number. Between the two lies a follow-up cadence that maximizes reachability without exhausting the list. A few principles hold up:

• Set a cap on attempts per contact, often four to six, beyond which you stop calling and mark the contact as unreachable.
• Space attempts out and vary the slots, rather than dialing three times in the same morning. A contact unreachable in the morning may be less so at the end of the day.
• Treat a ringing-no-answer number and an invalid number differently. The latter should leave the list immediately.
• Track the average number of attempts per useful meeting, to spot when persistence costs more than it returns.

A clear cadence protects two resources at once, the SDR's time and the list's value. Without it, teams swing between dropping hard contacts too early and grinding too long on dead numbers, two ways to waste.

In short

• A list has an expiry date. Its reachability melts with time and attempts.
• Size imports on real calling capacity, not theoretical.
• Set up the math on an example: capacity equals net hours times contacts per hour times available SDRs.
• Align calling windows with the hours your target picks up. Often the first connection lever.
• Steer the inventory continuously. Reallocate capacity as soon as a list depletes or a rate drops.