SDR time management: how much is four hours of calls, really?

“My SDRs do four hours of calls a day.” We hear that sentence in every conversation with a Head of Sales, and it means almost nothing.

Four hours blocked in a calendar is not four hours on the phone. And four hours on the phone is definitely not four hours of conversation. Most of the subject sits between the two.

What a call block actually contains

Take a two-hour slot billed as calling time and look at what’s inside.

There’s the start-up: opening the list, checking who has already been called, finding where you left off. There are the interruptions, which exist even with a headset and a closed door. There’s the logging after each call, a few dozen seconds that add up fast. There are the breaks, which are legitimate: nobody strings together difficult conversations for two hours without coming up for air.

And there’s pure waiting time. The ringing, the voicemails, the numbers that never answer. It’s the biggest item and the most invisible one, because it looks like work: the SDR is on the phone, headset on, listening to a ringing tone.

In an ordinary session, most of the time spent on the phone leads to no one. That’s the starting point for everything else.

Break it down instead of estimating

The only number that matters is actual conversation time, and it can’t be estimated.

You need three data points, and your tool has to report them automatically: the number of attempts, the number of calls connected to a human, and the cumulative duration of those conversations. If any of the three comes from manual entry, the measurement is worthless.

From there, breaking down a slot becomes simple. Time blocked, time actually on the phone, time in conversation. The gap between the first and the third number is what you’re trying to shrink, and it’s almost always wider than the team imagines.

Watch out for one measurement trap: if your tool counts voicemails as connected calls, your conversation time is wrong. Check how statuses get assigned before you steer by them.

The twenty minutes that change the day

There’s one block of time nobody counts, and it weighs a lot: list preparation.

An SDR who starts a session without knowing who they’re calling spends the first minutes of every call reading a record. Multiply that by sixty calls and it becomes a significant share of the day, and it shows in the quality of the conversations.

Twenty minutes of preparation the evening before, or first thing in the morning, change everything that follows. The list is sorted, the records are up to date, the scheduled callbacks are in the right order. The SDR starts the session and never has to step out of it.

It’s probably the only piece of organizational advice that produces a measurable effect without changing anything else.

What a tool can recover, and what it can’t

A tool recovers waiting time. That’s exactly what a parallel dialer does: the ringing and the voicemails are absorbed by the machine, and the SDR only receives the calls where someone picked up. For the same session length, the share spent talking goes up.

It also recovers logging time. Duration, technical status, recording, transcription, attachment to the right record: all of that should flow back without any intervention. What stays on the SDR’s plate is the useful note and the qualification, and that’s how it should be.

On the other hand, no tool recovers time from a bad list. Calling wrong numbers faster simply produces errors faster. And no tool makes up for a chopped-up calendar: three forty-minute slots are not worth two hours in a row, because of the restart cost each one carries.

The honest quota

A quota expressed in dials pushes the wrong behavior. The SDR optimizes what you ask for, so they dial. They redial easy numbers, they cut calls short, they inflate the counter.

A quota expressed in conversations is fairer, but it depends on the list: on a degraded file, the SDR no longer controls their ability to hit it.

The formulation that works best combines the two: a target on conversations, and a commitment on session time actually spent on the phone. The first measures the result, the second measures what the person really controls.

The subject deserves its own treatment, and we give it one in building an SDR quota that doesn’t break the team.

Frequently asked questions

How much calling time per day is realistic for an SDR?

Less than what usually gets announced. Two serious slots in the day, protected and prepared, produce more than four theoretical hours scattered around. What counts is the conversation time you get, not the time blocked.

Should call slots be blocked in the calendar?

Yes, and defended. A call slot cancelled for a meeting is a slot that never gets made up. Picking the slot deserves some work too, and we cover it in when to call.

How do you measure conversation time without a dedicated tool?

With difficulty, and that’s the problem. Manual entry gives an optimistic estimate that’s no use for decisions. If you don’t have the data automatically, consider that you’re not measuring it.

Is multitasking while the phone rings a good idea?

No. An SDR who works through email between two rings starts their conversations without context, and you can hear it. Better to remove the waiting than to fill it.