The short answer
A B2B cold call script is a call outline tailored to the buyer's role and the size of the deal. Executives hear outcomes and a short ask, managers hear team and process problems, and end users hear daily workflow pain. For larger deals, the script also opens new threads by asking each contact who else should be involved.
On this page
- Match the B2B Cold Call Script to the Persona
- The Executive Cold Call Script
- The Manager Cold Call Script
- The End-User Cold Call Script
- Adjusting the B2B Script for Deal Size
- Multi-Threading an Account on the Phone
- Running Persona Scripts Across an Account
- Write a B2B cold call script for any account in three steps
- FAQ
Key takeaways
Persona sets the message: Executives buy outcomes, managers buy process fixes, end users buy a better day. Write one script for each.
Deal size sets the ask: Small deals can close on a demo. Enterprise first calls aim for one more conversation and one more name.
Thread on every call: Ask each contact who else cares about the problem, and get permission before you mention them.
Keep the story consistent: Everyone at the account should hear the same core problem, framed for their role.
Match the B2B Cold Call Script to the Persona
Different roles at the same company feel the same problem in different ways. Your script should name the version they feel.
| Persona | What they care about | Lead with | Ask for |
|---|---|---|---|
| Executive (VP, C-level) | Revenue, cost, risk, strategy | One observation and one outcome | 15 minutes, or a pointer to the owner |
| Manager or director | Team output, process, targets | A process problem their team has | A 20 to 30 minute call |
| End user or practitioner | Their day: tasks, tools, frustrations | A workflow pain they live with | Their view, then an intro to their manager |
One problem, three framings. Say Northwind sells a freight quoting tool to Kestrel Logistics. The COO hears "margin on spot loads", the pricing manager hears "quote turnaround" and the analyst hears "copying rates between three spreadsheets".
The Executive Cold Call Script
Executives decide fast. Give them a sharp observation, one outcome and an easy exit. If the problem isn't theirs to own, they'll point you to who does, and that's a warm thread.
Hi [Name], [You] at [Company]. I'll be brief.
[Account] has [observation: added two new regions this year].
Companies in that spot often see [outcome at risk: margin slip on spot work]
because [cause]. Is that on your radar, or is it someone else's to own?
If they redirect you, ask: "Thanks. When I reach [name], may I say you suggested we speak?" Then use it only if they say yes.
- Don't open with your title or company history. Executives decide in the first sentence whether you're worth the next one.
- Don't explain features. Name the outcome and let them ask how.
- Don't fight a hand-off. A referral from the top is worth more than ten minutes with an executive who isn't listening.
Likely pushback: "Talk to my team." Reply: "Will do. Who specifically, and what would make it worth their time?" Now you know the owner and the bar.
The Manager Cold Call Script
Managers own the process and the targets. Talk about their team's week, not the company strategy.
Hi [Name], [You] at [Company]. I'm calling because teams like yours
at [type of company] tell us [process problem: quotes back up when
volume spikes]. How is your team handling that right now?
Follow up with the cost question: "What happens to the team when that goes wrong?" The answer is the business case you'll take to their boss. Pull more follow-ups from our discovery call questions bank.
Likely pushback: "We don't have budget for that." Reply: "Makes sense, it isn't in anyone's budget until it's a known cost. If it turned out to be costing the team real hours, who would you take that to?" Managers rarely own the budget, but they know who does.
The End-User Cold Call Script
End users rarely sign, but they know exactly where the pain is and will often tell you. Ask for their expertise, then for an introduction.
Hi [Name], [You] at [Company]. You're probably closer to [task] than
anyone I could call, so I'd value your take: how long does
[task: building a spot quote] take on a busy day?
Then ask up: "Who would care most if that took half the time?" Thank them, and mention them to their manager only with permission.
Likely pushback: "I don't make those decisions." Reply: "I know, and I'm not asking you to. I'm asking because you'd know whether it's a real problem. Is it?" End users who feel heard often become your first internal advocate.
Adjusting the B2B Script for Deal Size
The bigger the deal, the more people decide and the smaller your first-call ask should be. Change the goal of the call before you change the words.
| Deal size | Who decides | First-call goal | Typical close line |
|---|---|---|---|
| Small business | Often one person | A demo or a trial | "Can I show you on Thursday?" |
| Mid-market | A manager plus a budget owner | A discovery call | "Can we take 30 minutes to map how you do this today?" |
| Enterprise | A buying group | One more conversation and one more name | "Who else should be in the next conversation?" |
Enterprise calls are reconnaissance. You won't close a six-figure deal on the phone. You will learn who matters, what's at stake and when budgets get set. Our account research guide helps you prepare for those calls.
Multi-Threading an Account on the Phone
One contact is a single point of failure. Every call should add at least one name to your account map. These three lines thread without sounding pushy.
Thread sideways
Who else on your team runs into this? I'd rather hear it
from two people than guess.
Thread up, with context
Hi [Name], [You] at [Company]. I spoke with [Contact] on your [team]
last week about [problem]. They mentioned [detail they shared],
and suggested you'd see the bigger picture. Is that fair?
Only use a colleague's name and words with their permission. Breaking that trust ends the thread, and usually the deal.
Thread after a no
Understood, thanks for being straight with me. Before I go:
is this something [other team] deals with more than you do?
Log every thread as you go. A simple account map, updated after each call, keeps the story straight when you're on your fourth contact at the same company.
Account: [Account] Core problem: [one sentence]
Signal: [what changed] Next step: [date, who, what]
Name | Role | What they said | Permission to mention?
[Contact] | [Title] | [Their words on the pain] | [Yes / No]
[Contact] | [Title] | [Their words on the pain] | [Yes / No]
When the front desk stands between you and the next thread, use a gatekeeper script that names the problem, not the product.
Running Persona Scripts Across an Account
Multi-threading means three scripts per account instead of one, and each needs its own reason line. That's where prep time balloons.
Build the account story once. Write down the one problem and the one signal, then frame it per role. The email version follows the same logic; see B2B cold email for it.
Layer in the scenario. A referral from the manager changes how you open the executive call. The sales scripts for cold calling library covers each scenario.
The Edithly cold call script generator writes a script from each account's website. Add the contact's name, LinkedIn and a note on their role, and the draft starts closer to the person you're actually calling.
How Edithly does it
Write a B2B cold call script for any account in three steps
Edithly reads the prospect's website and writes a call script around their business and your offer. Add the contact's name, LinkedIn and a note on their role to point the script at the person you're calling.
- 1
Click the Cold Call Script tile
Open Home and pick Cold Call Script. Your pitch, proof points and positioning are already in your playbook, pulled from your website when you added your product.
- 2
Add the account and contact
Enter the company name and website, then the contact's name and LinkedIn. In Notes, say who they are, such as 'COO, owns margin' or 'pricing analyst'.
- 3
Click Generate cold call script
You get an opener, a permission ask, discovery questions with what to listen for, objection replies, a voicemail and a gatekeeper line, ready to copy.
Website
Ready
- Opener
- Permission ask
- Discovery questions
- Objections
- Voicemail
- Gatekeeper
- By hand
- 20 to 30 minutes per contact to research and adapt
- With Edithly
- A couple of minutes per contact
Frequently asked questions
What makes a B2B cold call different from B2C?
B2B calls reach people buying for a company, not for themselves. Several people are usually involved, decisions take longer and someone has to make a business case. So a B2B script focuses on the account's situation and the person's role, aims for a next conversation rather than a sale, and maps who else should be involved.
How do you cold call a C-level executive?
Be brief, be specific and lead with an outcome they own. Executives respond to a sharp observation about their business and a short ask. Skip features, say why you picked their company and ask one question. If they redirect you to someone on their team, ask whether you can mention that they sent you.
What is multi-threading in B2B sales?
Multi-threading means building relationships with several people at one account instead of relying on a single contact. If your only contact leaves, goes quiet or lacks authority, the deal survives because others know you. On the phone, it means asking each person who else cares about the problem and calling them with that context.
Should the script change for small and enterprise deals?
Yes. In small deals one person often decides, so a first call can end in a demo or even a trial. In enterprise deals, the first call aims for one more conversation and one more name. Longer cycles mean more stakeholders, so the script spends more time on discovery and mapping.
Can Edithly tailor a B2B cold call script to the person I'm calling?
Edithly writes the script from the prospect's website and your playbook, and you can add the contact's name, LinkedIn and a note on their role or the angle you want. The script includes discovery questions with what to listen for, objection replies, a voicemail and a gatekeeper line. You make the call yourself.