How to handle sales objections with techniques and examples

Think about the last time a prospect pushed back on a call. Maybe they said the price was too high, or the timing was wrong. A few rehearsed lines can help in that moment for objections you've heard before.

But practice gets you further. The more calls you take and the more objections you hear, the faster you learn which responses move the conversation forward and which ones stall it.

This guide gives you a head start on that practice.

You'll get a 5-step framework for sales objection handling, responses to 12 common objections, moments from Avoma's own sales calls, and ways to practice through role play.

You keep taking the calls. With this guide, you'll know what to try and what to listen for the next time a prospect pushes back.

TL;DR

• Most objections fall into 5 groups: price and budget, need and value, timing, authority, and trust or competition.
• The process has 5 steps: listen, acknowledge, ask questions, respond with evidence, and confirm.
• Managers build the skill by finding recurring objections in recorded calls, practicing them in role play, and scoring live calls over time.

What is objection handling in sales?

Objection handling in sales is how a rep responds when a buyer raises a concern about buying, such as price, timing, fit, or risk. Good objection handling uncovers the concern behind the words and answers it with relevant evidence. It ends with a next step that works for both sides, even when that next step is a "no."

The same objection can point to a gap in your product, a misunderstanding, or a polite way to end the call.

Say a buyer tells you, "This looks like a lot of work to roll out." Here are 2 ways to respond:

• Countering: "We guide your team through onboarding, and you'll have a dedicated CSM from day one."
• Clarifying: "When you say a lot of work, what are you picturing? The setup, or getting the team to use it?"

The clarifying question might reveal that the buyer's last rollout failed because reps never adopted the tool. That's a different problem from setup time, and it needs a different answer.

What are the most common types of sales objections?

Most sales objections fall into 5 groups. The group tells you where to start your questions.

Price and budget objections

"Too expensive" can mean the buyer hasn't seen enough value yet, is comparing you with a cheaper tool, or has a fixed budget. Budget objections are narrower: The company hasn't allocated the money, or someone else controls it. Late in a deal, a price objection can also open a negotiation.

Need and value objections

The buyer doesn't see a problem worth paying to fix, or doesn't connect your product to it. This often traces back to thin discovery. If the rep never established the cost of the current situation, the buyer has nothing to weigh your price against.

Timing objections

"Now isn't a good time" can reflect competing projects, a budget cycle, a reorg, or low urgency. Sometimes it's a soft no. Your job is to learn whether a real event makes later better, or whether later means never.

Authority objections

The person on the call can't decide alone. They need a manager's sign-off, a procurement review, or input from the team that will use the product. In B2B deals with several stakeholders, this is a normal part of the process.

Trust and competition objections

These come from risk. The buyer may already use a competitor, worry about switching costs, doubt a vendor's staying power, or need answers on security and implementation. Proof moves these objections: references, security documentation, and a clear rollout plan.

You'll find responses for all 5 groups in the 12 example objections later in this guide. They all rest on the same 5-step process.

How to handle objections in sales in 5 steps

These sales objection handling techniques work as one process, in the order a conversation moves:

1. Listen without interrupting.
2. Acknowledge the concern.
3. Ask questions to uncover the real objection.
4. Respond with relevant evidence.
5. Confirm you've resolved the concern.

This objection handling framework is close to LAARC (listen, acknowledge, assess, respond, confirm), a model used in sales and customer service.

1. Listen without interrupting

Let the buyer finish, including the part after the first sentence, because the detail that matters often comes second. Hold your rebuttal until they're done, and note their exact words for step 2.

2. Acknowledge the concern

Say back what you heard, in the buyer's words. Acknowledging a concern shows you heard it and leaves the buyer's assumptions open for the questions in step 3. Skip "I understand, but," since the "but" cancels the first half.

3. Ask questions to uncover the real objection

Ask 1 or 2 open questions to separate the stated objection from the concern underneath. A third question in a row starts to feel like an interrogation.

• "If price weren't a factor, would this be the right fit?"
• "How might we make the numbers work for your team this quarter?"

The last one is a "How might we" question from design thinking. It turns the objection into a problem you solve together.

4. Respond with relevant evidence

Answer the concern you uncovered in step 3. Match the evidence to it: a story from a similar team, a capability tied to their problem, or the cost of the current process in their own numbers.

Offer alternatives where they fit, such as a smaller rollout or a call with a product expert. Avoid leading with a discount, since it suggests the price was never firm.

5. Confirm you've resolved the concern

Ask, "Does that address the cost concern, or is something else still in the way?" If it does, agree on a specific next step with a date. If it doesn't, you've learned what to work on next.

If the buyer wants to pause, accepting that without pressure keeps the door open. Write down the objection and what you agreed for your follow-up.

Here's how the objection handling process plays out across 12 objections reps hear on a regular basis.

Common sales objections and how to respond

Use these responses as starting points, and adapt the wording to your product and the buyer's situation. In several cases, the right next step is more discovery. Avoma's own recorded sales calls from October 2026 supply 5 of the examples. The examples paraphrase the calls and leave out names, companies, and figures.

"It's too expensive"

"That's fair to raise. Is that compared with another option, or with what you'd budgeted? I want to make sure we're comparing the same things."

This response separates a value gap from a budget gap before you defend anything.

On one of Avoma's sales calls, a buyer liked the entry price but cooled when the add-on he needed raised the total. The rep explained how the modular pricing worked, without connecting the price to an outcome the buyer cared about. The objection stayed open, and a free trial kept a next step alive.

"We don't have the budget"

"Thanks for being upfront about that. Has your team set the budget for this year, or do you fund projects like this when the case is strong enough? Who makes that call?"

The buyer's answer tells you whether to build a business case, wait for the next cycle, or find the budget owner.

On one of Avoma's sales calls, a buyer said the company hadn't budgeted for the purchase and an upfront annual payment would strain cash flow. The rep asked whether billing terms were the only blocker, then whether quarterly billing would get it approved. The buyer said it would. A later end-of-quarter urgency pitch was the one part he pushed back on.

"Now isn't a good time"

"That makes sense with everything on your plate. What's taking priority right now? If we picked this up after that, what would need to be true for it to be worth a look?"

This response gives the buyer an honest exit and gets you a real reason or date for the follow-up.

On one of Avoma's sales calls, the rep knew a company-level change could affect timing and raised it before the buyer did. The buyer confirmed the company had frozen spending until the change went through. The rep didn't push for a date, moved into discovery, and booked a tailored demo for the following week.

"Send me some information"

This can be a polite way to end the call, or real interest the buyer wants to share with colleagues.

"I'm happy to send something. So it's useful, what would you want it to answer? And who else would read it?"

Real interest produces specific answers. A vague answer tells you where the deal stands.

"We already use another solution"

"That's good to know. What's working well with it? And is there anything your team works around today?"

Unmet needs surface when the buyer names them. If there aren't any, step back and check in before their renewal.

On one of Avoma's sales calls, a buyer said half of their sales leadership liked the conversation intelligence tool they already used. The rep agreed the vendor had a strong brand, offered to look for gaps in the current process together, and suggested a trial that wouldn't disrupt the team. The buyer set up a group demo with enablement, sales operations, and sales leaders.

"Your competitor is cheaper"

"They may well be. Could you walk me through what you'd get with them? If the scope is the same, price should decide it. If it isn't, let's look at where it differs."

You accept the point without criticizing the competitor.

"I need to discuss this with my manager"

Sometimes the champion isn't sure how to make the case to their own leadership.

"That makes sense, and I'd expect it. What do you think your manager will ask first? I can write a one-page summary, or join a short call to take their questions."

This response equips your champion for a conversation you won't be in. The Miller Heiman sales process maps buying roles such as the champion and the economic buyer during discovery, so this request comes up before the deal depends on it.

"We don't need this right now"

"That could be right. How does your team handle [the problem] today, and how much time does it take a week? If it's an hour or less, you may not need us yet."

If there's no need, you've saved both sides time.

"We're happy with our current process"

For this buyer, change feels riskier than staying put.

"Glad it's working for you. If you could change one thing about it, what would it be?"

Then share a pattern you've seen at similar companies.

Teaching the buyer something they can't learn on their own is the "Teach" part of the Challenger sales approach. It lands when evidence backs the insight.

"Implementation will take too long"

"That's a reasonable worry. What did your last rollout look like? I'll walk you through what setup involves on your side and what we handle, and you can judge the effort."

Specifics replace a vague fear, and the buyer's past experience tells you what to address.

"We're concerned about security"

This is either a firm requirement or a review IT needs to complete before any purchase.

"That's the right question to ask. What does your security team check first? I'll send our security documentation and set up a call with our security team if that helps."

This response routes questions to the right people, so you don't improvise answers on the call.

On one of Avoma's sales calls, a buyer said IT was reluctant because setup seemed to ask for full admin access. The rep asked him to share his screen before answering, saw a standard app-approval prompt, and explained what it did. He then sent a written step-by-step guide the buyer could give IT, and they booked a follow-up.

"We're not sure we'll see ROI"

The buyer needs a business case for someone else, or doubts the outcome.

"Let's work it out with your numbers. How many hours a week does your team spend on [task] today, and what would you count as a win in 90 days?"

Agreed success criteria give any evaluation a clear measure.

Pro Tip: When a buyer raises a second objection right after you answer the first, the first one may not have been the main concern. Go back to step 3 and ask again.

The last section covers how managers turn these responses into habits on live calls.

How to improve objection handling through sales coaching and role play

Sales objection handling improves with feedback on live calls and practice between them. Sales coaching programs that build this skill run a loop: find the objections, practice responses, score live calls, and track progress over time.

Review sales calls to identify recurring objections

Start with what buyers say on your own recorded calls. Look for the objections that come up most, the deal stage where they appear, and the moments where reps stall or move on without answering.

Avoma's Smart Trackers find buyer objections across calls and group them by type, such as price, timing, and competitor. The "Unhandled objections" tracker flags calls where a buyer raised a concern and the rep left it unanswered. This objection coaching workflow covers the full process, including an Ask Avoma prompt.

Practice objection handling with sales role play

Sales role play lets reps rehearse a response before a buyer is on the line. Build each scenario from an objection your buyers raised, in their words, with the Call-to-Drill method in these sales role-play scenarios. A hot seat round fits objection practice: 1 rep stays on while the team takes turns raising objections.

Give reps feedback based on real conversations

Feedback sticks when it points to a moment on a call. Avoma's AI call scoring scores calls against your scorecard, such as MEDDIC, BANT, SPICED, or your own criteria, and links each score to the timestamped moment behind it.

Add objection handling items to the scorecard, such as "Asked a clarifying question before responding." Save strong responses from top performers to Playlists so the team can hear what works.

Track improvement across sales conversations

To check whether a coached response carries over to live calls, run a 3-Score Check. For objections, also watch how often reps leave one unhandled and whether those calls still end with an agreed next step.

If your managers can't listen to enough calls to coach objection handling, explore Avoma's sales coaching software.