A good cold call script isn't something you recite, it's a framework you follow. Here's the structure that works in B2B, sample lines for every step and answers to the objections you'll hear this week.
What a call script is for, and what it isn't
A lot of reps flinch at the word "script." They picture a text read word for word, in that call-center voice everyone recognizes within three seconds. That's not what we mean.
A good cold call script is a framework. It sets the order of the steps, the two or three lines you don't want to miss, and the answers to objections that come up all the time. For everything else, the rep uses their own words.
It does three jobs:
keeps you steady when the prospect picks up and you have four seconds to hook them
keeps the message consistent across the team, especially when you hire junior reps
lets you compare and improve: when everyone starts from the same base, you quickly see what works
It does not replace listening. If your prospect brings up a specific problem ten seconds in, skip the next step of the script and dig into what they just said.
The five-step structure of a good script
Most effective B2B scripts follow the same backbone and fit in a few minutes:
Opening: who you are, plus a permission request
Hook: why you're calling this specific person
Discovery: two or three questions to check there's a real need
Close: a specific next step, usually a meeting
Exit: confirm, thank, log
Each step has one goal: earning the right to move to the next. The opening isn't there to sell, it's there to get thirty seconds. The hook isn't there to present your product, it's there to trigger a response. Keeping that in mind stops you from dumping everything in the first minute, the most common mistake beginners make.
The opening: the first few seconds
The prospect wasn't expecting you. They were busy with something else, and their first instinct is to figure out how to hang up politely. Your opening needs to be short, clear and honest.
A direct opening
"Hi Mark, it's Julie from [your company]. I'll be upfront, this is a cold call. Can you give me thirty seconds to tell you why, and then you decide if we keep going?"
An opening with context
"Hi Emma, Julie from [your company]. I saw you're hiring three sales reps right now, that's why I'm calling. Got two minutes?"
What to avoid
"Is this a bad time?": you're handing them the exit
"How are you doing today?": everyone recognizes the telemarketing line
a three-sentence company intro before you've even said why you're calling
Speak a bit slower than usual, and leave real silence after your question. That's the moment the prospect decides whether to give you the next part.
The hook: give them a reason to listen
The hook is the line that justifies the call. It should be about a problem, not a feature, and that problem should look like the one your prospect has.
A structure that works well: "I work with [role] at [type of company] who [concrete problem]. I wanted to see if that's something you're dealing with too."
Three examples by persona:
For a sales director: "I talk to a lot of sales directors whose teams spend a big chunk of the day dialing numbers and hitting voicemail instead of talking to prospects."
For a small business owner: "I speak with owners of service businesses who struggle to book enough meetings without spending their own evenings on it."
For an HR manager: "I work with HR managers at fast-growing companies who spend more time chasing candidates than actually meeting them."
Always end the hook with a question. If they say "yeah, a bit," you've earned the right to dig. If they say "no, not at all," you've saved time, and you can ask what is a priority for them right now.
Discovery: questions that get people talking
On the phone, you can't run through a twenty-line questionnaire. Two or three well-chosen questions are enough to know whether a meeting makes sense.
A few questions that open things up:
"How do you handle this today?"
"What takes up the most time in that process?"
"What have you already tried?"
"If you could change just one thing, what would it be?"
"Who else is involved when you make this kind of decision?"
The golden rule: after each question, stop talking. Play back what you heard before moving on: "So if I get it right, the real issue is the time lost on follow-ups, is that it?" The prospect feels heard, and you check you understood.
One more tip: write down the exact words your prospects use. They often become your best hooks the following week.
Closing for a meeting
The goal of a prospecting call is rarely to sell. It's to get a concrete next step: a meeting, a demo, a callback with the right person.
Offer specific slots
"Here's what I suggest: let's take twenty minutes to look at this together. Tuesday at 10 or Thursday at 3, which works better?"
Two specific slots beat "when are you free?", which pushes all the work back to the prospect.
Lock it in
confirm date, time and format (video or phone)
double-check the email for the invite
say in one sentence what you'll cover
send the invite while you're still on the line if you can
If the timing is wrong
"Got it. When should I call you back?" and log the date in your CRM. A "call me in January" honored to the letter usually goes down better than expected, because almost nobody actually does it.
Common objections and what to say
An objection isn't a wall. It's often a request for information or a defensive reflex. The method: acknowledge, ask, suggest a small step.
"Send me some information"
"Sure. So I send you something actually useful, what matters most to you on this topic?" Then suggest a quick call to discuss once they've read it.
"I don't have time"
"Totally fair, I caught you at a bad moment. Should I call back tomorrow afternoon or Thursday morning?"
"We already have a solution"
"Great, that's a good sign. What do you like about it, and what would you want it to do better?"
"I'm not the right person"
"Thanks for telling me. Who would be? Can I mention you pointed me their way?"
"No budget"
"Understood. Is it something for later this year, or really not a priority?" The answer tells you whether to schedule a follow-up or close the file.
"Where did you get my number?"
Answer simply and honestly about where your data comes from. If they don't want to be called again, tell them it's noted and actually do it: under GDPR, that's their right to object.
Gatekeepers and voicemail: two mini-scripts
Not every call will reach the decision-maker directly. Have two short variants ready.
With the receptionist or assistant
Be brief, polite and confident. "Hi, Julie from [your company]. Could I speak with Mark Durand, please?" If they ask what it's about: "It's about how his sales team is organized. Do you know when he's easiest to reach?" The assistant is a potential ally, not an obstacle: nobody knows the calendar better.
On voicemail
Twenty seconds max, one idea. "Hi Mark, Julie from [your company]. I was calling about the meetings your sales team books. I'll send you a short email and try again Thursday. My number is ..."
Don't leave a message every time. One message every two or three attempts is enough, otherwise your name becomes noise. That's also why many teams prefer a tool that only connects them to people who pick up, such as a parallel dialer: time lost on voicemail shrinks, and the script finally gets used where it matters, in real conversations.
Keep your script alive
A script is never finished. The one that works in January can run out of steam by June, because the market moved or competitors started using the same lines.
A simple routine to keep improving it:
every week, listen back to three or four calls: a booked meeting, a fast rejection, a badly handled objection
find the exact line where the call turned, one way or the other
test one change at a time (a new hook, a different question) over a full session
keep what works and add it to the team's shared script
Call recording and transcription make this much easier: you can skim a call in two minutes instead of replaying it all, and jump straight to the key moments. In Flunter, calls made with the power dialer or the parallel dialer are recorded, transcribed and summarized, so every session becomes raw material for the next coaching session.
One last tip: have the people who make the calls write the script. A script handed down from above gets recited. A script the team builds gets used.
Frequently asked questions
Yes, as long as it is a framework rather than a text you read out. The script sets the order of the steps, the two or three key lines and the answers to common objections, and the rep says the rest in their own words. It keeps you steady when the prospect picks up, keeps the team's message consistent and lets you compare what works.
Most effective B2B scripts follow five steps: the opening (who you are and a request for permission), the hook (why you are calling this person), discovery (two or three questions), the close (a specific next step, usually a meeting) and the exit (confirm, thank, log). Each step only has to earn you the right to move on to the next one.
Keep it short, clear and honest. For example: “Hi Mr Durand, it's Julie from [your company]. This is a cold call. Can I have thirty seconds to tell you why I'm calling?” Avoid “is this a bad time?”, which hands them the exit, and “how are you today?”, which everyone recognizes as a sales line. Then leave a real pause.
As with any objection, acknowledge it and offer a small next step instead of pushing. For example: “I understand, I've caught you at a bad moment. Shall I call you back tomorrow late afternoon, or Thursday morning?” Then log the agreed date in your CRM and stick to it.
Twenty seconds at most and a single idea: who you are, what it is about and when you will call back. For example: “I was calling about the meetings your sales team books. I'll send you a short email and try you again on Thursday.” Don't leave a message on every attempt: one every two or three calls is enough.