Outbound

Free cold calling script and objection handling generator

By Charles Summers · Updated · Free, no signup

Short answer

This builds a full B2B cold calling script: an opener, a permission-based hook, a 3-question discovery ladder that escalates from situation to problem to implication, and ready-to-use responses for the 5 most common objections (no time, no budget, already have a vendor, send me an email, not interested). Each objection response is built on a named, real framework, and each one lists exactly what not to say, since the wrong response to the right objection is what actually kills the call.

Use the cold calling scriptwriter

What does this tool actually do?

This builds a full B2B cold calling script: an opener, a permission-based hook, a 3-question discovery ladder that escalates from situation to problem to implication, and ready-to-use responses for the 5 most common objections (no time, no budget, already have a vendor, send me an email, not interested). Each objection response is built on a named, real framework, and each one lists exactly what not to say, since the wrong response to the right objection is what actually kills the call..

It runs entirely in your browser. Nothing you type is sent to a server, no account is required, and there is no usage limit, because there is no cost per run to control.

The first ten seconds are a different conversation from the rest

When a stranger picks up the phone, they are not evaluating your product. They are resolving an interruption. Whatever they say in the opening seconds is a reflex aimed at ending the interruption, and treating it as a considered judgement on your offering is how reps lose calls they had already half won. The opener therefore has one job, which is to buy thirty seconds. Not a meeting, not interest, thirty seconds.

Two openers reliably do that. The honest-upfront version names the situation and hands over control: this is a cold call, you can hang up or give me thirty seconds. The reason-first version states plainly why this person and no other. Conversation analytics vendors publishing from very large transcript sets have repeatedly found that asking whether you caught someone at a bad time underperforms, which makes sense, since it offers a scripted exit before you have said anything worth staying for.

Say your full name and company clearly, because vagueness at this point reads as a scam call and everybody who owns a phone now recognises the pattern. Then give the reason, and make it about them rather than your category: what separates a call that survives from one that does not is usually whether the second sentence could have been said to anybody. Note too that the talk ratio has to invert. You talk during the opener, which is the opposite of good discovery, and hand the airtime over the moment permission is granted.

Reflexes are not objections, and they are handled differently

A reflex arrives before information. A genuine objection arrives after it. If someone says not interested at second five, they cannot possibly mean it, because nothing has yet been proposed for them to be uninterested in. Meeting that with a rehearsed rebuttal escalates the interaction, and the caller ends up arguing with a person who has no idea what the argument is about.

The pattern that works is short and the same every time: acknowledge without agreeing, add one sentence of concrete relevance, ask one question, then stop talking. The silence is the part everybody skips and it is the part that does the work, because it makes answering easier than hanging up. Two further rules. Never handle more than two objections on a first call, since a third means they are being polite. And never handle one at speed.

  • Not interested, said instantly. Means you interrupted me. Reply that they have not heard anything yet, name the specific problem in one line, ask one question about it.
  • Send me an email. Usually a polite exit. Agree immediately, then ask what to put in it, because the answer tells you whether there is anything real here and gives the email a reason to be opened.
  • We already use something for that. The most useful sentence they could offer. Never attack the incumbent. Ask what they have had to build or work around it, which is where every genuine gap lives.
  • No budget. Almost always means no priority, or no authority. Ask when budgets are set and who sets them, and you leave with a date or a name.
  • Call me next quarter. A soft no unless something is scheduled to change. Ask what is different next quarter. If nothing is, calling back changes nothing either.
  • How did you get my number. A trust question, not an objection. Answer honestly in one sentence, without defensiveness, and move on.

The numbers that tell you whether the script or the list is broken

Track five stages and each failure diagnoses itself: dials, connects, conversations lasting over a minute, meetings booked, meetings held. Most teams report only the first and the last, which is exactly the pair that explains nothing, because a bad ratio between them has at least four causes and they demand opposite responses. Splitting the funnel takes one extra CRM field and settles most of the arguments a sales floor has about the script.

A low connect rate is a data problem, never a copy problem. Direct dials and mobile numbers connect several times better than switchboards, and the gap is wide enough that buying better data usually beats coaching. If you connect on fewer than one call in twenty, stop rewriting the opener and look at where the numbers came from. Check your caller ID too: high volumes from a single number get flagged by carriers, and a number displaying as spam is not answered however good the first line is.

Good connects with conversations dying inside twenty seconds is an opener problem. Conversations that run for minutes and produce nothing is a relevance problem, meaning you are reaching people who are pleasant but not accountable for the outcome. Meetings booked but not held is a commitment problem: cold-booked meetings no-show far more than inbound ones, commonly a third to a half, because the commitment was made in ninety seconds under mild social pressure.

Writing a script a human can actually say out loud

A word-for-word script sounds dead by line three, because reading and speaking use different rhythms and the person on the other end can hear the difference immediately. Write the first two sentences verbatim, since the opener is the only place exact wording earns its keep, then write everything after it as a decision tree of bullets. The rep improvises the words and follows the structure, which is the reverse of how most scripts are built.

Then read it aloud, standing up, and delete anything you would not say to a colleague in a corridor. Abstract nouns are the tell. Solutions, leverage, streamline, optimise and space (as in "the marketing automation space") all signal that the sentence came from a website rather than a person, and each one costs you a fraction of the attention you spent the opener buying.

Voicemails need their own short script: twenty to twenty-five seconds, name and number spoken twice and slowly, one line on why you called, no pitch and no question. Voicemail on its own converts close to nothing. Voicemail followed within the hour by an email whose first line references it converts respectably, because each touch explains the other and the email arrives with a reason to exist.

Improve it one variable at a time. Change the opener for a week and hold everything else steady, because moving the opener, the list and the calling hours together tells you nothing. And keep a file of the exact sentences that made someone say go on. Those are worth more than any framework, and they are the first thing lost when a rep leaves.

Numbers worth knowing

MetricTypicalWhat it means
Connect rate on direct dials and mobiles10% to 20%Switchboard-only lists run several times lower. Below about 5 percent overall, the problem is your data, and no amount of script work will move it.
Conversations per hour of focused dialling3 to 8With a decent list and without a dialler. This is why blocked calling time works and dialling in gaps between meetings does not.
Meetings booked per 100 dials1 to 3Varies hugely with seniority and market, so use it to read your own trend rather than to judge a rep. Held meetings are the number that matters.
No-show rate on cold-booked meetings30% to 50%Much higher than inbound, because the commitment was made in ninety seconds. Sending the invite while still on the call is the single cheapest fix.

Mistakes that quietly cost you results

Pitching before you have permission to speak
The prospect spends your first thirty seconds looking for a way out instead of listening. Buy the time first with a short, honest opener, then earn the right to describe anything.
Rebutting the first objection as though it were considered
Not interested at second five is a reflex to being interrupted, and arguing with it turns a neutral call hostile. Acknowledge it, give one concrete line, ask one question, then be quiet.
Reading the script word for word
It is audible within two sentences and it signals that this call is one of two hundred. Script the opener exactly, then work from bullets so the rep sounds like a person following a structure rather than a page.
Opening with whether you have caught them at a bad time
You have handed them a prepared exit before saying anything worth staying for, and large transcript analyses show it correlates with worse outcomes. Use an honest-upfront or reason-first opener instead.
Blaming the script when the list is the problem
Connect rate, conversation length and meeting rate fail for different reasons. Measure all three before rewriting anything, or you will spend a month polishing an opener that nobody stayed on the line to hear.

What does the output look like?

This is the exact output the tool produces from the example inputs. It is generated by the same code that runs when you click the button, so what you see here is what you get.

COLD CALL SCRIPT: a scheduling tool for field service teams -> Operations Manager OPENER Hi, [Your Name] here from [Your Company]. Quick one: is now a terrible time, or just a bad one? PERMISSION HOOK Short version: a scheduling tool for field service teams is built for Operations Managers who [problem it solves]. If that is not you, say so and I am off the phone. If it is, I have three quick questions. DISCOVERY LADDER (ask in this order, do not skip a rung) 1. SITUATION: Walk me through how your team currently handles [the process a scheduling tool for field service teams touches] today. 2. PROBLEM: Where does that process usually slow down or fall apart on you? 3. IMPLICATION: When that breaks down, what does it end up costing you: time, missed [outcome], or the team redoing work? OBJECTION HANDLING (your top one, plus the two that usually follow it) 1. "We do not have budget for this" [THE ONE YOU HEAR MOST] Framework: Cost of Inaction Reframe Say: Understood, and I am not asking you to find new budget today. The sixty-second question worth asking is what this is already costing you unsolved, because most teams we talk to are paying for the problem anyway, it just does not show up as a line item. Avoid: Do not immediately offer a discount. That confirms the objection is about price when it is usually about priority, and it teaches the prospect to negotiate before you have shown any value. Context: Operations Manager hear this pitch often, so the response has to sound unlike the last five calls they took. 2. "We already have a vendor for this" [commonly follows] Framework: The Wedge Say: Good, that means you already know this is worth solving, that is half the conversation done. Most switches we see happen because of one specific gap, not because the whole vendor is bad. What is the one thing your current setup does not do that you wish it did? Avoid: Do not trash the incumbent vendor. Criticizing a tool your prospect chose puts them in a position to defend their own decision instead of questioning it. 3. "Not interested" [commonly follows] Framework: Labeling (Chris Voss, mirror the objection back) Say: Fair enough, sounds like this is either not a priority right now, or something you have already tried to solve and it did not work. Which is it? Avoid: Do not argue or launch straight into a pitch. Reflecting the objection back as a question, not a rebuttal, is what gets people to explain the real reason, so you can respond to the actual objection instead of the brush-off. NOT COVERED HERE "I do not have time", "Just send me an email". Re-run with one of those selected to get the script for it. Three responses you can actually recall beat five you cannot. WHY THIS ORDER The situation question is low-effort and gets them talking. The problem question finds the crack. The implication question gets them to size the crack in their own words, which is far more persuasive than you sizing it for them. Your most common objection, "We do not have budget for this", is first so it is the one you have freshest in your head when the call starts.

Frequently asked questions

What is the best cold calling opener?

One that names the fact that it is a cold call and asks for a small, specific amount of time. Pretending the call is not an interruption is the single most common mistake, and prospects can tell within two seconds anyway. Naming it and asking permission is disarming precisely because it is honest, and it is the opener this tool defaults to.

How do you get past "I do not have time" on a cold call?

You do not push past it, you shrink the ask. This tool uses the 10-Second Permission Ask: instead of arguing that it is worth their time, you ask for ten seconds specifically, deliver one sentence of value, and let them decide. Fighting the objection just proves you are going to take more time than you promised, which confirms the exact thing they were worried about.

Should you ever email instead of calling when someone asks?

Only after you have qualified whether it is worth sending. "Just send me an email" is usually a polite way to end the call, not a real request, and an unqualified cold email gets ignored at close to the same rate as an unqualified cold call. Ask one question first, get one specific detail for the subject line, then send it.

How many discovery questions should you ask on a cold call?

Three is usually enough on a first call, and they should escalate, not repeat. This tool uses situation, problem, implication in that order, because asking about impact before establishing the problem exists produces a vague, unconvincing answer, while asking in order lets the prospect talk themselves into the size of the problem.

Related free tools

Some links on this site are affiliate links, which means Hacking Demand may earn a commission if you buy through them at no extra cost to you. This does not influence which tools are listed. The tools on this page are free and have no affiliate relationship of any kind.