Skill Tracer
Skills › Marketing Skills › sales-enablement › cold-call-scripts.md

cold-call-scripts.md

68 lines · skills/sales-enablement/references/cold-call-scripts.md at 88c79f6

Open on GitHub

Most marks come from matching words in the file, so treat them as pointers.

1# Cold Call Scripts
2
3Scripts for the first 30 seconds of a cold call, voicemails, and the pushback that comes right after the opener. Internalize the structure and say it in your own words. Prospects can hear reading.
4
5For where calls fit in a multichannel cadence (timing, attempts, which tiers get calls) and the rules on Do Not Call lists and AI voice, see the cold-email skill's multichannel cadence reference and the prospecting skill's compliance reference.
6

Cold Call Scripts

Scripts for the first 30 seconds of a cold call, voicemails, and the pushback that comes right after the opener. Internalize the structure and say it in your own words. Prospects can hear reading.

For where calls fit in a multichannel cadence (timing, attempts, which tiers get calls) and the rules on Do Not Call lists and AI voice, see the cold-email skill's multichannel cadence reference and the prospecting skill's compliance reference.

Raw lines 1 to 6
Names a skill cold-email :5
Names a skill prospecting :5
7## The first 30 seconds
8
9Four beats: who you are, why them, permission, a question.
111. **Name and company**, plainly. No "How are you today?"
122. **The reason for this call**, specific to them: the signal, the trigger, or the problem their segment has.
133. **Permission**: acknowledge it's a cold call and ask for a short window.
144. **One question** about their situation, so the call becomes a conversation.
16> Hi Priya, it's Sam from Acme. This is a cold call; can I take 30 seconds to tell you why I picked up the phone, and you tell me if it's worth continuing?
18> [yes]
20> You're hiring two SDRs this quarter. Teams scaling outbound like that usually find their bounce rate climbing before anyone notices, and it quietly hurts every inbox the new reps send from. How are you checking lists before they go into sequences today?

The first 30 seconds

Four beats: who you are, why them, permission, a question.

  1. Name and company, plainly. No "How are you today?"
  2. The reason for this call, specific to them: the signal, the trigger, or the problem their segment has.
  3. Permission: acknowledge it's a cold call and ask for a short window.
  4. One question about their situation, so the call becomes a conversation.
Hi Priya, it's Sam from Acme. This is a cold call; can I take 30 seconds to tell you why I picked up the phone, and you tell me if it's worth continuing? [yes] You're hiring two SDRs this quarter. Teams scaling outbound like that usually find their bounce rate climbing before anyone notices, and it quietly hurts every inbox the new reps send from. How are you checking lists before they go into sequences today?
Raw lines 7 to 21
22### Openers to use and avoid
24| Use | Avoid |
25|-----|-------|
26| A permission-based opener ("This is a cold call, can I have 30 seconds?") | "Did I catch you at a bad time?" (invites "yes"; call-analysis data ranks it among the worst openers) |
27| A specific reason ("You just opened two growth roles") | "How are you today?" (signals a salesperson immediately) |
28| Mentioning a peer company they'd recognize, if true | Pretending you've met, or "following up" on a conversation that didn't happen |

Openers to use and avoid

UseAvoid
A permission-based opener ("This is a cold call, can I have 30 seconds?")"Did I catch you at a bad time?" (invites "yes"; call-analysis data ranks it among the worst openers)
A specific reason ("You just opened two growth roles")"How are you today?" (signals a salesperson immediately)
Mentioning a peer company they'd recognize, if truePretending you've met, or "following up" on a conversation that didn't happen
Raw lines 22 to 29
30### When they say yes to 30 seconds
32Deliver the reason in two sentences and ask the question. Then listen. If there's a real problem, the goal of the call is a meeting, not a sale:
34> Sounds like it's worth a proper look. Would 20 minutes on Thursday work to go through how you're doing it now?

When they say yes to 30 seconds

Deliver the reason in two sentences and ask the question. Then listen. If there's a real problem, the goal of the call is a meeting, not a sale:

Sounds like it's worth a proper look. Would 20 minutes on Thursday work to go through how you're doing it now?
Raw lines 30 to 35
36## Pushback in the first minute
38| They say | Respond |
39|----------|---------|
40| "I'm busy" | "Totally understand. Is there a better time this week, or should I send a two-line email instead?" |
41| "Just send me an email" | "Will do. So I send something useful, is [the problem] on your plate this quarter or not really?" (The answer qualifies them either way) |
42| "We already use [competitor]" | "Makes sense, most teams we talk to do. Out of curiosity, how's it handling [the one situation where you're stronger]?" |
43| "Not interested" | "Fair enough. Is that because [the problem] isn't a priority, or you've got it covered?" Ask once, then let them go politely |
44| "How did you get my number?" | Tell them the actual source, and offer to remove them. Then do it |
45| "Who are you again?" | Restart with the name and the one-sentence reason, slower |
47Never argue past a second no. Log the reason; it's useful for the weekly sequence review.

Pushback in the first minute

They sayRespond
"I'm busy""Totally understand. Is there a better time this week, or should I send a two-line email instead?"
"Just send me an email""Will do. So I send something useful, is [the problem] on your plate this quarter or not really?" (The answer qualifies them either way)
"We already use [competitor]""Makes sense, most teams we talk to do. Out of curiosity, how's it handling [the one situation where you're stronger]?"
"Not interested""Fair enough. Is that because [the problem] isn't a priority, or you've got it covered?" Ask once, then let them go politely
"How did you get my number?"Tell them the actual source, and offer to remove them. Then do it
"Who are you again?"Restart with the name and the one-sentence reason, slower

Never argue past a second no. Log the reason; it's useful for the weekly sequence review.

Raw lines 36 to 48
49## Voicemail
5120–30 seconds. The goal is to make the follow-up email recognizable. A callback is a bonus.
53> Hi Priya, Sam from Acme. I'm calling because you're scaling the SDR team, and I had one idea on keeping new reps' lists clean before they start sending. I'll send a short email with it. Again, Sam from Acme.
55Then send the email within minutes, with a subject line tying it to the call ("my voicemail").

Voicemail

20–30 seconds. The goal is to make the follow-up email recognizable. A callback is a bonus.

Hi Priya, Sam from Acme. I'm calling because you're scaling the SDR team, and I had one idea on keeping new reps' lists clean before they start sending. I'll send a short email with it. Again, Sam from Acme.

Then send the email within minutes, with a subject line tying it to the call ("my voicemail").

Raw lines 49 to 56
57## Gatekeepers
59Be direct and polite: name, company, who you're trying to reach, and a one-line reason. Ask the assistant for advice ("Is Priya the right person for outbound tooling, or is that someone else?"). They often know exactly who owns what.

Gatekeepers

Be direct and polite: name, company, who you're trying to reach, and a one-line reason. Ask the assistant for advice ("Is Priya the right person for outbound tooling, or is that someone else?"). They often know exactly who owns what.

Raw lines 57 to 60
61## Reviewing calls
63Record calls where it's legal in both parties' locations (some US states and many countries require everyone's consent), and review a few each week:
64- How long until the prospect spoke?
65- Did the reason sound specific to them?
66- Was there a clear next step?
68Track dials, conversations, meetings, and the reasons people gave for saying no. The no-reasons tell you more about the offer than the meetings do.

Reviewing calls

Record calls where it's legal in both parties' locations (some US states and many countries require everyone's consent), and review a few each week:

  • How long until the prospect spoke?
  • Did the reason sound specific to them?
  • Was there a clear next step?

Track dials, conversations, meetings, and the reasons people gave for saying no. The no-reasons tell you more about the offer than the meetings do.

Raw lines 61 to 68