Cold call script template
A permission-based opener, discovery questions in order, and objection paths that branch instead of dead-ending.
- HubSpot / CRM
- Dialer
- Google Docs
- Slack
Write a cold call script for Heads of Growth at B2B SaaS companies. Ask is a 20-minute working session.
- Pulled ICP and positioningPersona priority: output volume without headcount
- Built the opener13 seconds, names the hiring trigger, asks for 30 seconds
- Ordered discovery5 questions: process, volume, bottleneck, cost, ownership
- Mapped objection pathsNot interested, no budget, using another tool, send an email
Script opens on the hiring trigger and asks for thirty seconds. Five discovery questions move from process to cost. Each objection path leads to a smaller ask — a recorded walkthrough instead of the working session — so the call ends with something rather than nothing.
A cold call script template that reads like a monologue gets abandoned in the first ten seconds. This one is built as a branching structure: a short permission-based opener, discovery questions ordered so each earns the next, and named paths for the four objections you will actually hear.
What is a cold call script template?
A structure rather than a screenplay: how to open, what to ask in which order, how to handle the common objections, and how to close for a next step. Word-for-word scripts fail because the call branches after your second sentence.
Open without pretending
- Permission-based opener under fifteen seconds
- A specific reason for calling this account
- A graceful path if the timing is wrong
Structure discovery
- Questions ordered from process to consequence
- Prompts that surface cost without interrogating
- Notes on what to skip because research already answered it
Branch on objections
- Named paths for the four most common objections
- One testing question per objection
- A smaller next step to offer when the full ask fails
What do you say at the start of a cold call script?
Name yourself, state plainly why you are calling this person specifically, and ask for a short window of attention. Pretending it is not a cold call wastes the goodwill you need for the next thirty seconds.
What discovery questions belong in a sales call script template?
Questions about their current process and its cost, ordered from easy to consequential. Ask how something works before asking what it costs them, and never ask what you could have looked up — that spends credibility for information you already had.
How should a sales call script handle objections?
With a named path per objection: not interested, no budget, already have a vendor, send me an email. Each path acknowledges the objection, asks one question that tests whether it is real, and offers a smaller next step. Rebuttal scripts that argue tend to end the call.
How the cold call script template works across your stack
The agent pulls account research and the ICP definition so the reason for calling is specific, and takes objection responses from your positioning and proof points in workspace Knowledge. Scripts export to your CRM or dialer as call notes, and the objection paths stay consistent with what your email sequences claim.
- HubSpot / CRM
- Dialer
- Google Docs
- Slack
Who uses this cold call script template
- SDRs
- Have a path ready for the objection instead of improvising it.
- Founders making their first calls
- Get a structure that does not require sounding like a telemarketer.
- Sales managers
- Standardize openers and discovery order across a team.
How to run this cold call script template in Metaflow
Name the persona and the account type
The agent uses your ICP and positioning to build a specific reason for calling.
Confirm your next-step ask
A meeting, a technical call, or something smaller — this shapes the closing paths.
Review the branches
Opener, discovery order, and four objection paths, each with a testing question.
Take it into the dialer
Export as call notes, then update the objection paths as you learn what you actually hear.
What you provide
- Persona and account type
- Your next-step ask
- Proof points and positioning
What you get back
- Permission-based opener
- Ordered discovery questions
- Four objection paths with testing questions
- Closing options including a smaller next step
Why use this cold call script template?
Branching structure rather than a monologue nobody follows
Discovery questions ordered so each earns the next
Objection paths test whether the objection is real before responding
Consistent with the claims in your email sequences
Cold call script template FAQs
What is a good script for cold calling?
One that opens by asking permission, gets to a question within twenty seconds, and has a defined path for each common objection. If it reads as something you could deliver without listening, it is not a call script — it is a voicemail.
What do you say during a cold call?
Say who you are, why you called this person, and ask for a moment. Then ask about their current process before making any claim about yours. Claims land better after they have described the problem in their own words.
What is the 80/20 rule in cold calling?
Commonly read as spending most of the call listening rather than talking. In practice, if you are speaking more than a third of a discovery call, you are pitching instead of qualifying.
What are the biggest mistakes in cold calling?
Pitching before qualifying, asking questions the internet already answered, arguing with objections, and stacking multiple asks at the close. The script structure is designed to prevent all four.
Similar cold email and outbound templates
Key takeaways
- Ask permission and be honest that it is a cold call
- Order discovery from process to consequence
- Test whether an objection is real before responding to it