Scripts get a bad name because most of them are written to be read aloud. A useful script is a decision tree: fixed at the four points where reps improvise badly, open everywhere else.
The four points worth fixing are the opener, the permission line, the one-sentence reason, and the objection responses. Everything between those is a conversation.
The structure
- Opener, 5 seconds. Name, company, honest acknowledgement that the call is cold.
- Permission, 3 seconds. Ask for thirty seconds. Then actually take thirty.
- Reason, one sentence. Specific to them, and ideally tied to something observable: a hire, a launch, a post, a change.
- Question, not a pitch. One question about how they handle the thing you fix.
- Ask for the meeting. Two concrete times, not “does next week work”.
The opener matters more than the pitch. “I know I am calling out of the blue, can I take thirty seconds and you can tell me to go away” outperforms every clever alternative, because it is true and it hands them control.
By persona
Founder or CEO, small company. They answer their own phone and they decide in one call. Lead with the outcome and a number, skip the discovery theatre. “I know this is out of the blue. Thirty seconds: we help agencies your size add pipeline without hiring an SDR, usually two to four meetings a week within a month. Is adding meetings something you are actively working on, or is this a bad time entirely?”
VP Sales or Revenue. They are measured on a number and they are pitched daily. Lead with the metric and a peer reference. “Thirty seconds and then I will get out of the way. Teams your size usually have reps spending half a day a week building lists rather than calling. Is that roughly true for yours?”
Operations or RevOps. They care about the stack and the mess. Lead with the mess. “You are probably running a sequencer, a data vendor, a dialer and a warmup tool. The reason I am calling is that stitching those four together is where most of the reporting breaks. Is that a live problem or already solved?”
Marketing. They care about attribution and brand risk. Never promise volume. “Quick one: when your sales team runs outbound, do you have visibility into what is actually being sent under your brand? That is usually the question I get asked, and it is the reason for the call.”
The four objections, and what actually works
“Send me an email.” Usually a polite exit. Accept it and extract one thing: “Happy to. So I send something relevant rather than generic, is the priority this quarter more pipeline or better conversion on what you have?” Then send it within the hour, referencing the call in the first line.
“We already use [competitor].” Do not attack the incumbent. “Good, that means the problem is real. Most teams we talk to keep it and add us for the part it does not cover, which is usually the phone and LinkedIn side. Where does it fall short for you, if anywhere?”
“Not interested.” One question, then leave gracefully. “Understood. Just so I do not call you again about the wrong thing: is it not a priority, or not a fit?” Log the answer as a disposition. It is worth more than the call.
“No budget.” Almost never about money at the price point of most sales software. “Fair. Is it that there is no budget line at all, or that this would need to displace something already in it?”
Gatekeepers
Be honest and be brief. “Hi, I am hoping you can point me in the right direction. I am trying to reach whoever owns outbound sales. Is that [name], or someone else?” Asking for direction rather than access works because it gives them a role other than blocking you. Do not claim to be returning a call.
Voicemail, and the pair that makes it work
Twenty seconds, three parts, no pitch: who you are, one specific reason, and that you will follow up by email. Then send that email the same hour with a subject line referencing the voicemail.
“Hi [name], Ravi at Outboundry. Calling because you are hiring two SDRs, and that is usually when list building becomes the bottleneck. I will send a short email so you have it in writing, no need to call back.”
The pair works because the voicemail makes the email recognised and the email makes the voicemail actionable. Either alone is half a touch.
What to do after the call
Log an outcome that means something. “No answer”, “not interested” and “callback” are not enough to explain a pipeline, and the fix is designing the outcome list backwards from your stages: see disposition design. The other half is that a call outcome should trigger the next touch automatically, including a WhatsApp voice note after a no-answer where the region and role make that normal.
Next: what these calls cost per meeting, or what you can legally dial.
Frequently asked questions
Should I use a script on a cold call?
Use a structure, not a script. Fixed wording makes you sound like a recording and collapses the moment someone answers differently. What should be fixed is the opener, the permission line, the one-sentence reason, and your responses to the four objections you will hear every day.
What is the best cold call opener?
Name, company, and an honest acknowledgement that the call is unexpected, followed by a request for thirty seconds. Pretending to have a prior relationship is the single fastest way to lose the call.
How long should a cold call be?
The average connect runs about a minute and a half, and that is enough. The goal is a booked meeting, not a demo on the phone.
Should I leave a voicemail?
Yes, and pair it with a one-line email referencing it the same hour. The voicemail on its own converts poorly; the pair converts well because it gives your name two contexts.
How many attempts before I stop?
Six to eight touches on the phone across two to three weeks, mixed with email and LinkedIn, and stop the whole sequence the moment they reply anywhere.