Skip to content

Cold call script: a structure and three B2B examples

A cold call script structure for B2B SDRs, three worked examples for different situations, and when to put the script down and follow the prospect.

Updated 12 October 20267 min readTypeGuide
on call · Vantage Group02:47

Paul Hendry · CFO

+44 20 7946 0731 · Vantage Group

Calling from
+44 20 7946 0002
Number owner
Agency · assigned to Shelley L.
Client
Kestrel Ltd
recordingbrowser

logged on the lead

  • Call · 2m 47s · answeredrecorded · transcript queued
  • Callback · Fri 11:00set from the call
  • Inbound call-back · matchedrouted to this lead and SDR
Illustrative example — sample data, not a customer screenshot.

A cold call script is not something to read aloud. It is a map of the call: what to say first, what to ask, where the objections usually come, and how to ask for the meeting. Reps who read word for word sound like it. Reps with no script ramble, forget to ask, and end calls without a next step.

The goal is a structure the rep knows well enough to leave and come back to.

The structure

Five parts of a B2B cold call

  1. 1

    Opener

    Who you are and why you are calling, in two sentences.

  2. 2

    Reason to listen

    One specific problem people in their role tend to have.

  3. 3

    Question

    Ask about their situation. Then listen.

  4. 4

    Answer or objection

    Respond briefly to what they said, then ask again.

  5. 5

    The ask

    A specific meeting time, and confirm the details.

Most weak calls skip step three. The rep pitches straight after the opener, the prospect has nothing to respond to except “not interested”, and the call ends.

Example 1: the straightforward opener

For a known decision maker, with a clear problem the offer solves.

SDR: Hi Laura, this is Sam from [agency] calling on behalf of [client]. I will be brief. I’m calling because finance leads at companies your size often tell us month-end close drags on because invoices arrive in five different formats. Is that something you deal with, or is it under control?

Prospect: It’s a bit of a mess, honestly.

SDR: What does it look like today, who handles the invoices when they come in?

(listen, ask one follow-up)

SDR: That’s the situation [client] works on. Rather than explain it over the phone, would a 20-minute call with their specialist next Tuesday at 10 or Thursday at 2 work better?

Note the shape: one problem, one question, then an ask with two specific times.

Example 2: the referral or trigger

When there is a concrete reason to call this company now: a new hire, an expansion, a public announcement.

SDR: Hi Daniel, Sam from [agency], calling for [client]. I saw you are opening a second warehouse this spring. Usually when teams add a site, scheduling drivers across both gets harder before it gets easier. How are you planning to handle that?

The trigger replaces the generic reason to listen. It only works if the trigger is real and recent; a guessed one sounds worse than none.

Example 3: the wrong person who knows the right one

Many calls reach someone who is not the buyer. Do not pitch them. Ask for help.

SDR: Thanks, that’s useful. Who on your team would normally look at how invoices are processed? … Would it be fair to say I’m calling from your side, or would you rather I mention I reached you first?

A named referral inside the company is often worth more than a meeting with the wrong person.

The voicemail

Keep it under twenty seconds: name, company, one-line reason, your number twice, and that you will try again on a given day. Do not try to pitch on a voicemail. Its job is to make the next call familiar.

When to put the script down

The script is for the first thirty seconds and the ask. In between, follow the prospect.

  • They start talking about a problem. Stop and ask about it. Do not jump back to the next line.
  • They ask a direct question. Answer it honestly and briefly. If you do not know, say so and offer the meeting as the place to get the answer.
  • They are clearly the wrong fit. Thank them and end. A bad meeting costs the client more than no meeting.
  • They are busy right now. Ask for a specific time to call back, and log it.

Script lines that hurt

Lines that end calls

  • "How are you today?"
  • "Do you have a minute?"
  • A two-minute product pitch after the opener
  • "Would you be open to a chat sometime?"

What to say instead

  • Name, company and reason in the first breath
  • State that you will be brief and get to the point
  • One problem, then a question about their situation
  • Two specific times, then confirm email and attendees

These are habits, not laws. If your own recordings show an opener working, keep it. That is the point of testing.

Test the script, do not argue about it

Every team has opinions about openers. Settle them with data: run two versions on the same client, split the leads between them, and compare meetings booked per lead called. Give it enough calls before deciding; a few dozen dials prove nothing either way.

Objections get their own page: objection handling for SDRs. For the tooling side of calling, see cold calling software: what to look for.

Where Dialbrew fits

In Dialbrew the call script lives in each client project, grouped by category (openers, objection handling, voicemail and more), and is open while the SDR calls from the lead. Two script versions can be A/B tested against each other, with meetings tracked per version. Calls are placed from the browser through the sales dialer, recorded and transcribed, so you can hear how a script actually sounds on the phone.

Book a walkthrough

Put every client on one floor

A walkthrough on your own roster, clients and commission model — from an imported list to a sent invoice. Judged on your operation, not a demo dataset.

One booked meeting pays for an SDR's seat for the month.

EU-hosted · eu-central-1 · integrates the CRM, calendar and telephony you already run