Building a Dial Block That Survives Past 10:40am

The block doesn't die at minute ninety. It dies at minute forty.

Go and watch a rep dial. Not a highlight reel, not a call you were invited to review — sit behind someone for a full block and watch the clock instead of the phone.

The first twenty minutes look great. Energy is up, the first few dials go out fast, there's a bit of momentum. Then a gatekeeper shuts it down. Then a VP picks up and says "not interested" before the second sentence. Then three voicemails in a row. Then somewhere around the forty-minute mark, something quiet happens: the rep opens a browser tab.

That's it. That's the death of the block. Not a dramatic collapse, not a rep storming off. A tab. They go and check whether the account they just called has a new funding round. They notice the contact's title is wrong in the CRM and fix it. They see a Slack message. They log the last four calls properly, with nice notes, because they're behind on notes and this feels productive.

By 10:40 the block is over. The timer says another fifty minutes to go and the calendar block says "Power Hour" but the rep is doing data entry with a headset on. They'll finish the hour, log something like eighteen dials, and tell their manager the list was bad.

The list was probably fine. The block wasn't built to survive contact with rejection.

So this is the mechanical version. Not motivation. Not "embrace the no." Just how to construct ninety minutes so that the forty-minute wobble has nowhere to go.

Everything that isn't dialling happens before the timer starts

The single biggest structural mistake I see is reps building the block inside the block. They sit down at 10:00, open the CRM, run a filter, look at the first account, read a bit about it, find a number, dial. Then repeat. Research, dial, research, dial.

That pattern feels efficient because there's no idle time. It's actually the reason the block fails, because it hands you a legitimate, work-shaped excuse to stop dialling every ninety seconds. When the fourth rejection lands and you don't feel like picking the phone up again, you don't have to make a decision to quit. You just spend a little longer on the next account's research. Then a little longer. The exit ramp is built into the design.

Build the queue the night before. All of it. I mean a finished, ordered list of accounts and contacts and numbers sitting in front of you, so that when the timer starts the only physical action available to you is dialling.

Queue more than you can get through

For a ninety-minute block, I want a queue that you cannot possibly exhaust. If you run dry at minute seventy you will not go and build more queue — you'll stop. So overbuild it. Enough accounts that even on your fastest, most connect-free day you're still looking at unworked rows when the timer goes.

The queue has to be flat. One list, one screen, one row per attempt. Company, contact, title, direct number, switchboard number as a fallback, and one line — one line — of why you're calling them specifically. Not a dossier. One line you can read in two seconds while the phone is ringing.

If your one line takes longer than two seconds to read, it's not a queue, it's homework, and you'll do the homework instead of the calling.

Batch the research the night before, in a different mental gear

Research and dialling are different jobs and they use different parts of your brain. Researching is slow, curious, tolerant of tangents. Dialling is fast, repetitive, and requires you to not care very much about any individual outcome. Switching between them every ninety seconds is the most expensive thing you can do with a block.

So do the research in its own session, the evening before or first thing, with a stopwatch. Two minutes an account, maximum. You're looking for one hook. A new location, a job posting, a change in leadership, a customer they just announced, something in their world that makes a first sentence make sense. If you can't find one in two minutes, write "none" in the hook column and call them anyway with a generic opener. A generic opener on a good-fit account beats a beautiful opener on an account you never got to.

The rule I hold to: no browser tabs open during the block except the dialler and the queue. Nothing else. If a question comes up mid-call — what do they actually make, who owns that function, is this the right site — you write the question down and move on. You do not look it up. Looking it up is how the block ends.

Load the script before the timer starts

The other thing that should already be on the screen is the words. Not a full script you read verbatim, but the opener, the two or three lines you actually want to land, and the objection handles for the three things you know you'll hear today.

This matters more than people admit, because at minute fifty-five your improvisation gets worse. The reps who hold quality across a full block are not the ones with better willpower, they're the ones who have less to invent under fatigue. If you're calling into software leadership, have the SaaS cold call script for reps dialling CROs, VPs of Sales and RevOps leaders sitting beside the queue so the opener is a read, not a decision. If you're calling plants, the manufacturing script built around earning twenty minutes with a plant manager works the same way — it's there so you don't have to think about the first ten seconds at minute seventy.

Same goes for the harder desks. Freight is the clearest example, because the person you're calling has heard four versions of your pitch this month and the opener has to acknowledge that rather than pretend otherwise, which is exactly the thing you will stop doing well when you're tired. The freight and 3PL script for getting past "I've heard this pitch four times" exists for that specific fatigue. Pick yours, load it, don't edit it during the block.

The shape of a ninety-minute block

Here's the structure I'd give a rep starting Monday.

Minutes 0 to 10 — the throwaway ten. You start with the accounts you care least about. Not junk, but the bottom of your list. The purpose is to get the first three or four dials out of your system while your voice is still warming up and your first opener is still clumsy. Nobody's first call of the day is their best call of the day. Stop spending it on your best account.

Minutes 10 to 60 — the main run. Top of the queue down. No re-ordering, no skipping, no "I'll come back to that one." The order was decided last night by a calmer version of you who wasn't looking for reasons to avoid a specific company. Trust that person.

Minutes 60 to 80 — the callback run. More on this below.

Minutes 80 to 90 — the tail. Back to the queue, whatever's left, and you dial until the timer goes. Not until you feel finished. Until the timer goes.

Minutes 90 to 105 — admin. Outside the block. This is where notes get written, CRM gets updated, tasks get set, and follow-up emails go out. Fifteen minutes, immediately after, non-negotiable. If you don't protect this slot, you'll do the admin during the block and we're back where we started.

The notes rule: you do not leave the block to write anything

This is the rule that saves the most time and the one reps push back on hardest, because writing notes feels like diligence.

During the block, every call gets a single code and nothing else. I use something like: NA for no answer, VM for voicemail left, GK for stopped at the gatekeeper, N for reached them and got a no, CB plus a time for a callback, M for meeting booked. Six symbols. You type two characters and you're on the next row.

That's it. No sentiment, no "seemed busy, may be worth trying Q3," no tidying the contact record. Those thoughts go in a scratch column at the end of the row in three or four words, and they get turned into real CRM entries in the fifteen minutes after the block, while it's all still fresh.

The reason is simple. Writing a proper note takes maybe forty seconds, but the cost isn't forty seconds. The cost is that writing prose puts you in a completely different gear, and coming back out of that gear to make a cold call is the hardest transition in the whole hour. Do it a few times and the block is finished. One rep I watched did it after every single connect. Her call quality was excellent and her volume was a third of what it should have been, and she genuinely believed she'd had a busy morning.

Two characters. Move on.

The callback list is a trap unless you fence it off

Callbacks are the most seductive form of avoidance available to a rep, because they're real work with warm people in it. "Call me back at two" is a much nicer thing to do than dial a stranger who's never heard of you.

So callbacks get their own fenced window inside the block, and they don't leak.

When someone says "call me back later," you write CB and a time and you keep going. You do not stop the run to check whether it's nearly that time. And you do not sprinkle callbacks through the main run, because every callback you make is a cold dial you didn't make, and the callback list is finite while the cold list is not.

If a callback time falls inside your main run, either take the hit and make it — it's a commitment, honour it — or plan the block so the callback window sits where most of your promised times land. Usually that's later in the hour anyway, because people say "try me this afternoon."

The other half of the fence: a callback that doesn't answer is just a dial. Two characters, next row. Reps treat a missed callback as a bigger emotional event than a cold no-answer and I have no idea why. Same outcome, less effort spent.

The expected-value frame, and why stopping is the only real failure

Here's the mental model that holds the whole thing together, and I want to be careful with it because it's usually taught with a made-up number attached.

I'm not going to give you a benchmark conversion rate. I don't know yours and any figure I invented would be worse than useless, because you'd anchor to it. Go and get your own. Open your CRM, pick the last full quarter, and pull three numbers: dials made, conversations had, meetings booked. Divide the meetings by the conversations and you've got your connect-to-meeting rate. Divide meetings by dials and you've got the number that actually matters.

Now flip it. If you know your own meetings-per-dial, you know how many dials one meeting costs you. And if you know roughly what a meeting is worth in your pipeline — your average deal size multiplied by your own close rate, again from your own data, not mine — you can divide that by the dials-per-meeting and get a figure for what a single dial is worth.

Do this on paper once. It takes four minutes and it changes how the forty-minute wobble feels.

Because the point of the number isn't precision. The point is that the value attaches to the dial, not to the outcome. Every dial in the block is worth the same amount before it connects. The no-answer is worth it. The gatekeeper block is worth it. The guy who hangs up mid-sentence is worth it. They all paid, because the value was in making the attempt, and the attempt is the thing you can control.

Which means there is exactly one way to lose a block: stop dialling. Not "get rejected." Not "have a bad opener." Stop. A rejection is a paid dial. A dial you didn't make is the only zero on the board.

I find this frame more useful than any pep talk, because it doesn't require me to feel good. On the mornings I felt terrible I could still do arithmetic, and the arithmetic said pick the phone up.

One more thing that follows from it: when you book a meeting at minute thirty-five, keep dialling. The temptation to bank the win and go do something else is enormous, and it's the same failure as quitting after rejection, just wearing a nicer outfit. The dials after the win are worth exactly what the dials before it were worth.

What a bad block actually looks like

A well-built block can still be a grim ninety minutes. You'll have days with no connects at all. Days where three people are rude in a row. Days where the numbers in your queue are wrong and you spend a run of dials hitting dead lines.

The test of the structure isn't whether the day goes well. It's whether at minute eighty-five, with nothing to show, you are still making dials into a queue that hasn't run out. If you are, the block worked. The result was bad and the process was fine, and those are different things — which is exactly why the two-character notes matter, because the log tells you the truth about what you did rather than how you felt.

And when it's genuinely the list, you'll know, because the pattern shows up in the codes. A wall of GK means your contact strategy is off. A wall of NA on direct lines means your data is stale. A wall of N on connects means the opener isn't earning the next sentence. Those are three different problems with three different fixes, and you can only see them because you logged a symbol instead of a paragraph. If it's the last one and you're calling into agencies, going back to something like the staffing and recruiting script for reaching VPs of recruiting and branch managers and rebuilding the first fifteen seconds is a better use of tomorrow than adding twenty more names.

What I'd do this week

Tonight, build one queue. Overbuild it, two minutes of research per account, one hook line each, script loaded in a second window. Tomorrow, set a ninety-minute timer, start on the accounts you care least about, use six symbols for notes, fence the callbacks into their own twenty minutes, and don't open a browser tab. Then take fifteen minutes afterwards and write the real notes.

Do that four days running and you'll have a better read on your own numbers than any benchmark could give you.

The part most reps still get wrong is the opener under fatigue, because you can't practise that at your desk with a live prospect on the line. That's the gap we built DrillCall for — reps run the same opener and the same three objections against an AI buyer until the words are automatic, so that at minute seventy the script is muscle rather than a decision. If your blocks are holding but the quality sags in the back half, that's where I'd point the next hour of your time.