Building a cold call script in 4 blocks

A cold call script written out word for word doesn’t survive the first call. The prospect says something that wasn’t planned, the SDR hunts for their line, and the silence is audible.

What holds up is a structure. Four blocks, each with a clear goal and an exit. The SDR knows where they are and what they need to get before moving to the next one. The words themselves change with every call.

Block 1: the first fifteen seconds

The goal of this block isn’t to convince. It’s to get permission to continue.

Three things need to fit in it: who you are, why you’re calling this person in particular, and an explicit request to continue. The second is the one everyone rushes. “I’m calling because you’re hiring salespeople right now” has nothing to do with “I’m calling to introduce our solution”. The first shows you actually looked; the second announces a sales pitch.

The request to continue matters just as much. A short, honest question that leaves a real option to refuse: “Do you have two minutes, or should I call you back?” A prospect who says yes has mentally agreed, and the call changes in nature.

What doesn’t work in this block: fake familiarity, the loaded closed question, and announcing a call length you don’t stick to.

Block 2: qualification, in two questions

You’re not there to run through a questionnaire. You’re trying to find out whether this person has the problem you solve, and whether they can do something about it.

Two questions are usually enough. One about the current situation, one about what’s stuck. “How many of you are making calls today?” then “what’s holding you back right now, the number of contacts or the time available?”

The classic mistake is stringing five questions in a row. By the third, the prospect feels like they’re filling out a form and cuts it short. Ask one, listen, build on what was said.

This block is also where you decide to stop. If the person doesn’t have the problem, the call is over, and saying so plainly earns you time and credibility.

Block 3: what you offer, in one sentence

One sentence. Not a paragraph. It has to connect what the person just said to what you do.

That’s why this block comes third and not first. A pitch made before listening is generic by necessity. Made after, it picks up the prospect’s words, and that’s what makes it credible.

Avoid the feature list. Name the concrete change: what the person will do differently, or what they’ll stop doing.

Then stay quiet. The silence that follows a pitch is the most useful moment of the call, and it’s the one SDRs fill fastest. Let it last. The prospect’s reaction tells you whether to move forward, dig into an objection, or get out.

Block 4: the exit

A call ends on a decision, not on a pleasantry.

Three possible exits, and all of them are acceptable. A meeting with a precise date in the calendar, booked right there during the call. A callback with a clear reason, if the timing is wrong. Or a straight no, which you note and respect.

The fourth exit, the one to refuse, is vagueness: “I’ll discuss it internally”, “get back to me whenever”. Those are the entries that clog a pipeline for months. One question settles it: “shall we set something up now, or do I leave it with you to come back to me?”

Log the exit immediately, with the matching status. A call that isn’t qualified while it’s fresh is a call lost for what comes next.

Keeping the script alive

A script isn’t a document you write once. It’s an object you correct every week with recordings.

The simplest method is to listen to the first fifteen seconds of twenty calls. You’ll see right away which openings hold and which ones make people hang up, and you’ll fix block 1 for the whole team rather than one person at a time.

Do the same for block 3, listening only to what follows the pitch. That’s where you see the difference between an SDR who listened and an SDR who’s just running through the script.

At Ubic, calls are recorded and transcribed and statuses flow back into the CRM, which lets you find the sessions worth replaying instead of digging around at random. The reports are there to spot the week or the SDR where something shifted, never to grade people.

As for the phrases that keep coming back at you, we’ve listed the most frequent ones in 10 cold call objections and how to answer them.

Frequently asked questions

How long should a cold call last?

As long as it takes to reach one of the three exits. A forty-second call that ends on a clear no is a good call. A ten-minute call with no decision is not.

Do you need a different script per persona?

The blocks stay the same. What changes is the reason for calling in block 1 and the two questions in block 2. The rest adapts on its own if the SDR listens.

Should a new SDR read from their script?

At first, yes, but read the structure and the questions rather than ready-made sentences. What should be learned by heart is the order of the blocks and the goal of each one.

Where does the product demo go?

Nowhere in this call. The goal of a cold call is to get a meeting, not to sell. An SDR who starts demoing has already lost the thread of block 4.