B2B Cold Calling Script: 3 Annotated Examples for SDRs

A good B2B cold calling script isn’t something an SDR reads word for word. It’s a structure: a short opener that earns the next 30 seconds, a specific reason for calling, two or three discovery questions, prepared answers to the objections you’ll hear every day, and a clear ask. The script gives a new rep confidence and gives the team a shared baseline to improve.

This post covers that structure, three annotated cold calling script examples for different situations, a voicemail script, and how SDR ops should manage scripts so they get better over time instead of drifting.

Why Most Cold Calling Scripts Fail

Most scripts fail for one of three reasons:

They’re about the seller. “We’re a leading platform that helps companies…” The prospect hears a pitch and starts looking for an exit.
They’re too long. A script that takes 90 seconds before asking a question is a monologue. Cold calls are won or lost in the first 20-30 seconds.
They’re generic. A script that would work equally well for any company in any industry gives the prospect no reason to believe you’ve thought about their situation.

The fix for all three is the same: build the script around a specific problem a specific persona has, and get to a question quickly.

The Structure of a B2B Cold Calling Script

1. Opener (5-10 seconds)

Say who you are, acknowledge the interruption honestly, and ask for a short window. Two openers that work in B2B:

Permission-based: “Hi Dana, it’s Alex from Company. I’m calling out of the blue. Can I have 30 seconds to tell you why, and then you can decide if it’s worth continuing?”
Problem-based: “Hi Dana, Alex from Company. I work with sales leaders who are struggling to get their SDRs ramped in under a quarter. Is that on your radar at all?”

Avoid “How are you today?” as an opener. It signals a sales call before you’ve said anything useful.

2. Reason for the call (10-20 seconds)

This is where research pays off. Tie the call to something specific: a trigger (new funding, a hiring spree, a new leader), their role’s typical problem, or a peer company’s situation. One sentence of context, one sentence of problem.

3. Discovery (1-3 minutes)

Two or three open questions that test whether the problem exists. Good discovery questions are specific enough to answer quickly:

“How are you handling X today?”
“What happens when Y breaks?”
“If you could change one thing about Z this quarter, what would it be?“

4. Objection handling

Prepare for the five objections you’ll hear most. We cover them below.

5. The ask

Ask for a specific next step with a specific time: “Would it be worth 20 minutes on Thursday to look at how other teams handle this? I have 10 a.m. or 2 p.m.” Vague asks (“Can I send you some information?”) produce vague outcomes.

Cold Calling Script Example 1: Trigger-Based Call

Situation: the prospect’s company just posted several SDR job openings. You sell SDR onboarding or operations software.

Rep: Hi Jordan, it’s Sam from Company. I’m calling out of the blue. Do you have 30 seconds for me to explain why?

Prospect: Sure, quickly.

Rep: I saw you’re hiring four SDRs at once. When teams add that many reps in a quarter, the thing that usually breaks first is ramp: managers end up spending most of their week onboarding instead of coaching. Is that something you’re planning around?

Prospect: Yeah, it’s a concern.

Rep: How are you onboarding reps today? Is it mostly shadowing, or do you have a structured program?

Prospect: Mostly shadowing, honestly.

Rep: That’s common. How long does it usually take a new rep to book their first meeting?

Prospect: Six or seven weeks, maybe.

Rep: Got it. We help teams shorten that with a structured first-30-days setup. Would it be worth 20 minutes on Thursday to walk through what that looks like? I’ve got 11 or 3.

Why it works:

The trigger (four SDR openings) proves research and gives a reason for this call, today.
The problem statement is about a consequence the prospect cares about (manager time), not a feature.
The discovery questions are concrete and answerable in one sentence.
The ask offers two specific times.

Cold Calling Script Example 2: Role-Based Call (No Trigger)

Situation: no specific trigger, but you’re calling heads of sales ops at mid-market software companies about forecasting.

Rep: Hi Priya, Taylor from Company. I’ll be honest, this is a cold call. Can I take 30 seconds and you tell me if it’s relevant?

Prospect: Go ahead.

Rep: I talk to a lot of sales ops leaders, and the complaint I hear most is that the forecast call turns into a debate about whose spreadsheet is right. Does that sound familiar, or have you got that solved?

Prospect: We’re mostly fine, but week-over-week changes are hard to track.

Rep: When a deal moves from commit to best case, how do you find out today?

Prospect: Usually in the call itself.

Rep: So no warning beforehand. If you had a daily view of what changed, would that change how you run the call?

Prospect: Probably.

Rep: Would it be worth 20 minutes next week to see how a couple of teams set that up? Tuesday or Wednesday morning work?

Why it works:

Honest framing lowers the defensive reaction.
“Does that sound familiar, or have you got that solved?” gives the prospect an easy way to disagree, which keeps the conversation going either way.
The rep narrows from a broad pain to a specific moment (finding out about forecast changes during the call).

Cold Calling Script Example 3: Referral or Peer-Based Call

Situation: you’ve worked with a similar company, or a colleague of the prospect suggested you call.

Rep: Hi Chris, it’s Morgan from Company. Your colleague Jamie in marketing suggested I give you a call. Do you have a minute?

Prospect: About Jamie? Sure.

Rep: Jamie mentioned your inbound leads sometimes sit a day or two before an SDR picks them up. Is that accurate from your side?

Prospect: It happens, mostly when we’re busy.

Rep: When it happens, is it a routing issue, or just volume?

Prospect: Some of both.

Rep: Makes sense. Would it be useful to spend 20 minutes looking at where the delay comes from? Thursday at 10 or Friday at 1?

Why it works: the referral earns the first 30 seconds on its own, so the rep spends them on a specific problem rather than on credibility. Only use a referral if it’s real; a made-up referral destroys trust the moment the prospect checks.

Handling the Five Most Common Objections

Prepare responses, but treat them as conversations, not rebuttals. The goal is to keep talking, not to win the argument. Our objection handling playbook goes deeper.

“I’m not interested.” “Fair enough. Is that because you’ve already solved X, or because it’s not a priority right now?” This separates “solved” from “not now,” which are very different follow-ups.
“Send me an email.” “Happy to. So I send something useful rather than a brochure, what’s the one thing you’d want it to cover?”
“We already use [competitor].” “Good to know. How’s it working for X? Teams that switch to us usually do it because of Y, so if that’s fine for you, I won’t take more of your time.”
“We don’t have budget.” “Understood. Is this something you’d look at next planning cycle? When does that start?”
“I’m busy right now.” “Of course. Is there a better 10 minutes later this week? I can call Thursday at 9.”

Voicemail Script

Most cold calls go to voicemail. Keep it under 25 seconds, give one specific reason, and tie it to an email you’re about to send:

“Hi Dana, it’s Alex from Company. I’m calling because you’re hiring four SDRs this quarter and I had an idea about ramp time. I’ll send you a short email with the details, subject line ‘SDR ramp.’ My number is 555-0100. Again, Alex, 555-0100.”

The voicemail’s job isn’t to get a callback, which is rare. It’s to make the email that follows more likely to be opened.

What Most People Get Wrong: Treating the Script as Fixed

Here’s our opinion: the script is a team asset that should change every few weeks, and most SDR teams don’t manage it at all. Reps start with the onboarding script, drift to their own versions within a month, and nobody knows which version performs best.

SDR ops should run scripts like any other part of the system:

Version them. Keep the current script in one shared place with a version number and date.
Tie them to outcomes. Track connect-to-conversation and conversation-to-meeting rates by script version where your dialer or call notes allow.
Review calls weekly. Pick five recorded calls (good and bad), listen as a team, and agree on one change to try.
Change one thing at a time. A new opener or a new discovery question, not a rewrite. Otherwise you can’t tell what worked.
Keep persona variants. One script per persona (for example, sales leader vs sales ops vs CRO) beats one script for everyone.

The cold call script framework template is a good starting format, and our post on why cold calling still works for modern SDRs covers how calling fits alongside email and LinkedIn.

Compliance Note

Rules on cold calling vary by country and by whether you call business landlines or mobile numbers. In the US, automated dialing and texting to mobile numbers are restricted under the Telephone Consumer Protection Act; in the UK, businesses can register with the Corporate Telephone Preference Service. Check the rules for every country you call into, and keep do-not-call lists synced across your dialer and CRM.

Where GTMStack Fits

Script management works best when call outcomes are logged consistently. GTMStack’s SDR operations features track calls, conversations, and meetings by rep and campaign, so you can compare script versions with real data, and workflow automation can trigger the follow-up email after a voicemail. The scripts themselves are still your team’s work.

FAQ

How long should a cold calling script be?

The scripted part (opener plus reason for calling) should take 20-30 seconds to say. The rest is a set of discovery questions and objection responses the rep uses as needed.

Should SDRs read cold calling scripts word for word?

No. New reps can stay close to the script for their first few weeks, but the goal is to internalize the structure and sound natural. Prospects can hear reading.

What’s the best opening line for a cold call?

There isn’t one universal line. Openers that acknowledge the cold call honestly and ask for a short window tend to work better in B2B than fake familiarity or “How are you today?”

How often should we update our cold calling script?

Review it at least monthly based on recorded calls and conversion data, and change one element at a time so you can see what helped.

Next Steps

Write one script per persona, version it, and review five calls a week as a team. If you want help setting up the tracking behind it, contact us.