An objection handling script is a sheet of prepared lines, one per objection, that keeps a rep asking instead of arguing.

What an objection handling script is

An objection handling script is a one-page sheet that pairs every objection your sales reps actually hear with three things: what that objection usually hides, one line to say back, and the question that follows the line.

It is not a list of rebuttals for sales objections. A rebuttal answers the words a prospect used. This sheet is built to find out what the words were standing in for, because the first thing a buyer says is almost never the reason they are saying it.

Handling sales objections well makes the rest of the conversation shorter. Once you know which part of the product, the price or the timing is in the way, you stop presenting things the prospect does not care about.

Reps do not read a sheet like this out loud on a call. They read it before the call, say the lines out loud once, and keep it open so the second objection does not catch them improvising.

This page covers the objections that recur in B2B calls and emails. For the openers, the voicemail and the six call situations they sit inside, see the cold calling scripts, and for the habits around the call, cold calling tips.

The script sheet: eight common sales objections at a glance

These are the common sales objections that recur across B2B segments. The middle column is the point of the sheet: the label a prospect reaches for is rarely the thing standing in your way.

Print eight objections, not forty. A sales rep who can find the right line in two seconds will use it, and a rep scrolling a long document of objections improvises instead.

Every line and question on this page was written for this page. Replace the wording with your own market's language before anyone dials, because borrowed phrasing is the fastest way to sound generic.

Objection or brush-off: the difference that decides your answer

A brush-off on a cold call is not an objection. It is a stranger asking you to go away before you have given them a reason to stay, and it arrives before they have processed anything you said.

Objections are a response to your content. They reference something specific: a vendor, a date, a number, a person, a constraint. A brush-off references nothing, because there was nothing to respond to yet.

Treating a brush-off as an objection is what makes cold calls unpleasant for both people. You answer an argument the prospect never made, and they harden the position to end the call.

You get one attempt to convert a brush-off into a conversation, and it is a reason, not a rebuttal: one specific thing about their company that you found before you dialed.

What to do with a brush-off

Give the prospect the exit and take it. "No problem, I will leave it there" costs three seconds and keeps the number usable, which is worth more than a conversation you were not going to get today.

Then change the reason, not the objection handling. Brush-offs cluster around openers that could have been read to any prospect on the list, so the fix lives in your list and your research rather than in a better line.

The one exception is when you have something specific and have not said it yet. Say it in a sentence, then stop, and let the prospect decide whether it earns ten more seconds of their time.

The response framework behind every line

Each line on the sheet follows the same four beats. The four beats matter more than the wording of any one line, because they are what keeps the call a conversation rather than a debate.

Beats two and three are where sales reps go wrong. They answer a concern the prospect never raised, and now there are two objections in the call: the original one, and the one the rep just invented.

Acknowledge without agreeing or arguing

"That is fair" and "good to know" both work. What does not work is "I understand, but", because everything before the "but" is discarded by the listener and the sentence becomes a contradiction.

Ask one question, then be quiet

This is the beat reps skip. The question converts a label into a reason: not budget but "budget is set in October", not too expensive but "expensive next to what we pay now".

Answer the concern, not the label

Once you understand the reason, the answer is usually two sentences, and one of them should use the prospect's own words. Long answers signal that you did not believe the first objection was resolvable, which tells the prospect it was not.

Check, then ask for a specific step

"Does that help, or is there more to it?" gives the prospect a clean way to raise the concerns underneath the first objection. Then ask for a date, not for interest, the same way a sales pitch ends on an ask.

What understanding an objection actually means

Sales reps say they understand an objection when they can repeat it back. You understand it when you can name what would have to change for it to disappear, in the prospect's terms rather than your product's.

That test is useful mid-call. If you cannot name the change, you are holding a label rather than a reason, and one more question will help you more than any answer you could give.

All three say the same thing in different orders: do not answer until you have asked. The four-beat version is shorter because a sales rep holding a phone cannot run five steps from memory.

Four categories most objections fall into

HubSpot's guide sorts sales objections into budget, authority, need and timing. Sorting your own sales objections this way tells you whether the problem is your list, your reason for calling, or your product.

Objections about the product itself

"You do not have the feature we need" and "we would build this internally" are product objections, and they are the ones sales reps argue with hardest. Ask what the feature would have to do, and whether anyone has scoped the internal build.

Answer a product objection with a fact about the product, not with value language. If your solution does not do the thing, say so, and if it does, show it rather than describing it.

Sometimes the honest answer is that your product does not do it. Saying so costs one deal and keeps the relationship, because the prospect remembers which sales rep told them the truth about a gap.

Objections about trust

"We tried something like this and it did not work" is not a product objection. It is a request for proof, and no response line answers it. Ask what went wrong, then show the part of your process that prevents it happening again.

If one category dominates your calls, fix that upstream. Repeated need objections point at your ideal customer profile; repeated authority objections point at the job titles on your list.

A bank of questions for any sales objection

The response line buys you two seconds. The question is what turns sales objections into information with value to you, so keep a small bank of questions beside the sheet and pick one by category.

Questions surface concerns, and statements bury them. Two rules for a bank of questions.

Every question is open, because a yes or no question returns a yes or no and nothing else. And you ask one, not three, because a stack of questions sounds like an interrogation.

If the prospect answers with detail you could not have guessed, the objection was real and the conversation is live. If the answers stay vague after two questions, it was an exit, and the right move is to offer them one.

Objection 1: "We have no budget"

What it usually means: there is no line item for this, because nobody has sized the problem yet. Companies that say they have no budget usually spend money every quarter on things that did get sized.

Response line: "That is fair, and most teams do not have a line for this until someone has put a number on what it costs them today."

Follow-up question: "When does your team plan budget for {{area}}, and who has to see a number before then?"

Stop when: there is no budget and no problem. No budget with a real problem is a timing conversation. No budget with no problem is a no, and you should log it as one.

Objection 2: "I do not have time"

What it usually means: early in a cold call, it is a reflex, not a statement about the calendar. Later in a deal, from someone who has already given you time, it is usually real.

Response line: "Understood. I will take thirty seconds, and if it is not relevant in thirty seconds I will leave it there."

Follow-up question: "Is a different day better, or is {{problem}} not something this quarter?"

Stop when: they decline the thirty seconds. Promising thirty seconds and taking two minutes costs you the callback and everything after it.

Objection 3: "We already have a vendor"

What it usually means: it is true, and the setup mostly works. There is usually one part that does not, and the prospect has stopped expecting anyone to fix it.

Response line: "Good, most teams your size have something in place. I am not asking you to replace it."

Follow-up question: "If you could change one thing about how {{vendor}} handles {{area}}, what would it be?"

Why it matters: their current solution is the benchmark your product will be measured against, so learn how it is used before you say a word about yours.

Never: criticize the incumbent. The prospect or their manager chose it, so an attack on the vendor is an attack on their judgment, and the call ends there.

Stop when: they cannot name anything they would change. That is a working system, and the honest move is to ask when the contract is reviewed, then leave.

When the objection is really about a competitor

"We already have a vendor" and "we are evaluating a competitor" are different objections. The first is about a working solution. The second is a live comparison, and the prospect is asking you for a reason to choose.

Answer a competitor objection with the two or three things your solution does differently, stated as facts a buyer can check. Do not rank the competitor, and never guess at their pricing, their roadmap or their customers.

Then ask which of those differences matters for their situation. If none of them does, the competitor is the right choice, and saying so is worth more to a sales reputation than a contested deal.

Objection 4: "Send me some information"

What it usually means: on a first call, it is the most common polite exit in B2B. It becomes a real request the moment the prospect names a topic, a person or a format.

Response line: "Happy to. So I send the right thing instead of a brochure: what should it answer?"

Follow-up question: "And if it answers that, is fifteen minutes the week after worth putting in now?"

The test: a real request survives the question, because the prospect can name the concerns it should answer. A brush-off does not, because there is nothing behind it to name. Either way, send something short, and see the email at the end of this page.

Objection 5: "I am not interested"

What it usually means: nothing in your first twenty seconds connected to a problem they recognize. It is a verdict on your reason for calling, not on your product.

Response line: "Fair enough. Is that because {{problem}} is handled, or because it is not on the list this quarter?"

Follow-up question: none. One question, then their answer decides. Asking twice after "not interested" turns a neutral contact into someone who remembers your company badly.

Stop when: they repeat it. The second "not interested" in one call is a no, and a sales rep who accepts it keeps the number usable for a better reason later.

Objection 6: "Call me next quarter"

What it usually means: either a real cycle with a date behind it, or a softer version of no that ends the call without an argument. The question separates them in one exchange.

Response line: "I can do that. So the call is worth taking, what will be different by then?"

Follow-up question: "Is there a date the {{project}} decision gets made, and should I plan around it?"

The test: a real timing objection names an event, such as a renewal, a hire, a reorganization or a budget cycle. A vague quarter with no event is a polite no.

Then: put the date in the CRM with the reason in the prospect's own words, and pick the thread back up in your sales cadence on that date, not before.

Objection 7: "It is too expensive"

What it usually means: the price has nothing to sit next to. Expensive is a comparison, and until you know what it is being compared with, any answer you give is a guess.

Response line: "Compared with what: another option you are looking at, what you spend on this today, or what the budget allows?"

Follow-up question: "If the number were not the issue, is this the approach you would pick?"

Why that second question: it isolates price. A yes means you have one problem to solve. A no means price was the acceptable way to say something else, and you have not found it yet.

If nothing helps: a prospect who cannot connect the price to a result does not have a price problem. Go back to the value proposition and the cost of their current situation, because that is where a number gets its meaning.

Never: discount on the first mention. A price that drops the moment it is questioned tells the buyer the first number was not real, and it invites the same question at renewal.

Objection 8: "I am not the decision maker"

What it usually means: it is usually true, and it is usually the most useful sentence in the call. B2B purchases are decided by a group, so one name was never going to be enough.

Response line: "Thanks for saying so, that saves us both time."

Follow-up question: "Who owns {{area}}, and what usually has to be true before they look at something like this?"

Then ask: "Would you rather introduce me, or should I reach out and say you pointed me there?" Both answers are fine, and one of them is an internal referral.

Note: this is different from a gatekeeper, who is routing your call rather than evaluating your offer. It also belongs in qualification, covered in how to qualify sales leads.

What one entry on the sheet looks like

Every entry your team writes should fit on four lines, in this order, because that is the order a sales rep needs them in while someone is talking. Copy the block and fill it per objection.

OBJECTION: "{{their words, verbatim}}"

USUALLY HIDES: {{the reason underneath, in one line}}

SAY: "{{acknowledgement}}, {{one short reframe}}."

ASK: "{{one open question that names something specific}}?"

STOP IF: {{the condition that makes this a real no}}

How to write an objection handling script for your team

A borrowed sheet of sales objections is a starting point. The version that works is built from what your own prospects say, in their words, about your own offer.

1. Pull the objections from your own calls

   Take thirty recent calls and write down the first sentence after the opener, verbatim. Do not paraphrase yet, because the exact wording is what reps will hear again.

2. Sort them into budget, authority, need and timing

   The pile that dominates tells you what to fix. A tall need pile is a targeting problem, not a scripting problem.

3. Write what each one usually hides

   Ask the sales reps who handled it well what turned out to be true. One line each, and leave it blank if nobody knows yet.

4. Write one response line and one follow-up question

   The line acknowledges and reframes in a single breath. The question has to be open, and it has to name something specific to their company.

5. Mark the stop rule for each objection

   Write the condition that makes this a real no. Without it, the sheet only teaches sales reps to keep going, which is how it turns into pressure.

6. Test it live, then rewrite monthly

   Run it for a month, log which lines produced a second question, and cut the ones that never did. Change one line at a time.

Who writes the sheet

The reps who take the calls write the lines, and one person edits them into a single voice. A sheet written entirely by marketing sounds like marketing, and the prospect hears that in the first clause.

Keep it to one page. If your objection handling document needs a table of contents, nobody will open it before a calling block, and a sheet that stays closed changes nothing about the calls.

How a team practices the sheet

• Say it out loud, not silently. Hearing the line helps, because lines that read well and sound wrong are the most common failure, and reading in your head hides that completely.
• Roleplay the second and third objections, not the first. Reps are prepared for the opening reflex and unprepared for the one that comes after they answer it.
• One sheet per segment. The objections from a fifty-person company and a five-thousand-person company are different sentences with different reasons behind them.
• Record which line was used. A sheet with no feedback loop is a document. A sheet with one field in the CRM is a system.
• Practice stopping. Ending a call cleanly after a real no is a skill, and it is the one nobody rehearses.

Where objection handling sits in the sales process

Objections appear at every stage, and the same words mean different things at each one. "No budget" from a stranger is a reflex. "No budget" from a prospect in a third meeting is a real constraint to solve together.

That is why the sheet is read alongside the B2B sales process rather than instead of it. The stage tells a sales rep how much weight to give the objection before answering it.

The mechanics of the call matter too: pace, silence, and the ask at the end. Those are covered in how to make a sales call, and they decide whether your best line lands or gets talked over.

When to accept a no

A sheet of objections without stop rules becomes a pressure tool. The rules below end calls early, which is the point: the time saved goes to prospects who have the problem.

• The second clear no in the same call. One question after the first no is fair. A second is you negotiating with a stranger about their own priorities.
• No problem, no budget, no date. When all three are absent there is no solution to sell, nothing to nurture toward, and the honest move is to close the record.
• They ask not to be contacted. Stop immediately, confirm it, and make sure the request reaches every list and every tool the same day.
• The objection is about your company, not the offer. A bad past experience is answered by fixing it, not by a line on a sheet.
• They keep agreeing and never commit. Pleasant calls with no next step are a tire kicker pattern, and they cost more than a fast no.

A clean ending is worth more than a forced next step. Prospects who were treated well when they said no answer the phone when something changes, which is the only reason the number stays useful.

What a no is worth to a sales team

A fast no has value, and it is the second best outcome of a sales call. It returns time to the sales rep, it keeps a dead record out of the pipeline, and it usually arrives with a reason worth writing down.

Teams that reward only meetings booked teach sales reps to argue with prospects. Teams that also count clean disqualifications get shorter pipelines and forecasts that hold, because the objections that ended each deal were logged instead of buried.

What the US rules say about a request to stop calling

This is a summary of one official source, the FTC guide to the Telemarketing Sales Rule, and it is not legal advice. Ask counsel about your own calls, especially to consumers or outside the United States.

The practical version: "do not call me again" is not an objection to handle. It is an instruction, and the only correct response is to confirm it and remove the number that day.

What to log after every objection

The sheet improves only if the calls feed it. Five fields are enough, and they should be filled in before the next dial, while the prospect's own wording is still fresh.

What a manager reviews each month

Count the objections by category and by segment, every month. One category rising across a segment is a signal about the list or the offer, and no amount of objection handling on the phone will fix that.

Then read ten calls where the prospect stayed after an objection and ten where they did not. The difference is almost always whether a question came before the answer.

The "what it hid" column is the one that pays. After a few dozen calls it shows whether your no-budget objections were really sizing problems, or whether you are calling companies that genuinely cannot buy.

Common objection handling mistakes

Most of these are habits rather than gaps in knowledge, which is why reading a list helps less than having a manager name one of them right after a call.

• Answering the label instead of asking what is behind it.
• Treating a first-ten-seconds brush-off as an objection worth a rebuttal.
• Using "I understand, but", which deletes the acknowledgement it opened with.
• Talking through the silence after your own question.
• Criticizing the incumbent vendor the prospect chose.
• Discounting the first time price is mentioned.
• Asking a second time after a clear no.
• Writing lines nobody can say out loud without reading them.
• Keeping a sheet for a year without checking which lines still work.
• Answering a product question with a value pitch instead of a yes or a no.
• Running one sheet for every segment, so the lines fit no prospect exactly.
• Logging "not interested" with no note about what preceded it.

The email after "send me some information"

When a prospect asks for information and actually names a topic, the reply is short and answers that topic in the body. A link and a brochure are not an answer.

The template below gives the answer first, offers the detail second, and makes "not now" a one-word reply. More follow-up wording is in the sales follow-up email templates.

Subject: The {{topic}} answer you asked for

Hi {{firstName}},

You asked what this would have to answer, so here is the short version instead of a brochure: {{oneLineAnswer}}

The longer write-up is here if you want the detail: {{link}}

One question so the next step is useful: is {{problem}} something your team is working on this quarter, or is it parked?

If it is parked, reply with "parked" and I will leave it until {{month}}.

{{senderName}}

Frequently asked questions