GuidesPublished 9 min read

Handling Multiple Objections: A Scored Drill

a line deflected off a plane, redirected upward
Listen to this article · 12:25 · AI-generated narration
0:00 / 12:25
Chapters

What should you say first when a buyer stacks objections?

Say the objections back in the buyer's words, then ask which one decides the deal. Do not answer anything yet. A buyer may raise price, timing, and an integration concern in one breath. When that happens, the first move we recommend is a playback and a ranking question:

So I heard three things: the price is above what you planned, you can't start before next quarter, and you're not sure it works with your CRM setup. Did I miss one? If only one of those could be solved, which one decides whether we keep talking?

Each part has a job. The playback puts on the record that you heard every concern. Did I miss one gives the buyer room to add anything you skipped. The ranking question hands the priority call to the person who owns the decision.

Use the buyer's nouns, not your category labels. We score a playback that relabels the buyer's words as a fail. For groundwork on reflecting buyer language, start with Sales Listening Drills: Paraphrase First.

The first response to stacked objections is a question, not an answer.

TL;DR

Handling multiple objections starts with refusing to answer them all at once. Play every objection back in the buyer's own words, ask which one decides the deal, handle only that one, and get the buyer to confirm it is resolved before you move to the next. If it stays open, name it and agree when you will return to it. Drill the sequence in scored practice, against a pass bar a manager can check from the transcript.

  • Play back every objection verbatim before answering any of them.
  • Let the buyer rank the concerns. Ask which one decides the deal.
  • Handle one objection. Get the buyer's confirmation, or an agreed return, on the transcript before moving on.
  • Score four separate rows: playback, ranking question, single handling, confirmation.
  • A failed run gets a one-row debrief and a re-run booked on the calendar.

Why a single monologue answer fails

Some reps answer price, timing, and integration in one long turn. That puts three answers on the record and no buyer confirmations. Read the transcript back and you cannot point to any concern the buyer considers resolved. If the deal advances anyway, it advances on rep opinion. Exit criteria exist to prevent exactly that: they demand buyer-verified evidence, not the rep's sense that the call went well.

Our standard is simple. An objection counts as handled only when the buyer says so. Under that standard, the monologue fails no matter how good each answer was.

There is a fair counter-position. Strong reps handle objections best by improvising, and an agreed first response can make them sound canned. We take that seriously, so we fix only the first move. The playback and the ranking question are drilled until they are automatic. What follows depends on the objection the buyer picks, and the rep improvises it from understanding. Rehearsal is what makes improvisation safe. The rep who owns the first move is not caught flat when three objections land together.

An objection counts as handled only when the buyer confirms it in their own words on the transcript.

How do you choose which objection to handle first?

Let the buyer choose, then work through the order the buyer gives you. We leave objection prioritization to the buyer. Your guess about which concern matters most is opinion. The buyer's answer is evidence.

Plan for three replies:

The buyer names one. Take it and park the rest out loud: Understood. Let's take price first. I'll come back to timing and the CRM question.

The buyer says all three matter equally. Ask once more, as a forced ranking: If we solved two of them and not the third, which one would still stop this?

The buyer adds a fourth. Add it to the list, play back the full list, and ask the ranking question again.

If your org qualifies deals with MEDDPICC, the buyer's answer is evidence for the Decision criteria field. Log the buyer's words verbatim, because the rep's summary of what decides the deal is not the same evidence.

The buyer's ranking of objections is evidence; the rep's guess about which one matters most is opinion.

Handle one, confirm it, then return to the list

Handle the chosen objection the way your playbook handles it on its own. The stack changes the order, not the branch. Your team's agreed first responses for price, timing, and integration still apply.

Then confirm before you move on. Use this line: Does that answer the price concern, or is part of it still open? A yes in the buyer's words closes the item. Anything less leaves it open: I guess, we'll see, or a change of subject. Ask one follow-up. If the item is still open, name it and agree with the buyer when you will return to it. Do not slide to the next concern without that agreement. Then go back to the list: That leaves timing and the CRM question. Which one next?

The buyer may re-raise a confirmed objection later in the call. Treat that as a repeated objection, not a new stack. Repeated Objection Handling: Second Response covers that line.

Never move to the next objection until the buyer has closed the current one or agreed when you will return to it.

The four-row rubric a manager scores from the transcript

Score each row pass or fail, per rep, per scenario. Do not blend the four rows into one number. A rep who passes playback and fails confirmation needs a different drill from a rep who fails the ranking question. Score the handling row against your own objection standards. Reps rationally discount feedback from a generic rubric.

Score playback, ranking, single handling, and confirmation as separate rows, per rep per scenario, never as one blended number.

Rubric rowPass: the transcript showsFail: the transcript shows
Verbatim playbackEvery objection restated in the buyer's own nouns before any answerAn objection dropped, relabeled, or answered before the playback
Ranking questionRep asks which concern decides the deal and waits for the buyerRep picks the order, or asks and answers it themselves
One at a timeRep handles only the buyer's chosen objection in that turnRep answers two or more objections in a single turn
Buyer confirmationBuyer states the item is resolved, or rep names it open with an agreed returnRep moves on after their own summary or a buyer non-answer

The drill you can run this week

Rehearse the stack in scored practice before a live buyer delivers it. Burning real pipeline as training material is the most expensive coaching method a sales org can choose. We recommend a format that costs the manager 30 minutes to run: 5 minutes of setup, 15 of drilling, and 10 of debrief. Budget about 10 minutes beforehand to pick the scenario from a live deal and choose the rubric row you will debrief.

Scenario. Take three objections from a real open deal. The buyer opens with all of them at once: Look, the price is above what we budgeted, we can't start anything before next quarter, and I'm not sure this works with our CRM setup. Buyer rules. If the rep answers more than one objection in a turn, the buyer says Okay and confirms nothing. When the rep asks the ranking question, the buyer picks one concern. Change the pick on the second run. Reps. Each rep runs the scenario twice in the drill block.

Pass bar. All four rows pass on the same run. For every objection, the manager can highlight the playback line, the ranking question, and either the buyer's confirmation or the agreed-return line. If any of those is missing, the run fails and is re-run. In XL Roleplay, report flags link to the exact transcript moment, so you can jump straight to the confirmation line. A recorded call scored by hand works too, and the pass bar is the same.

An objection handling drill passes only when all four rows pass on one run, with every objection buyer-confirmed or named open with an agreed return.

What does a failing attempt sound like?

A failing attempt sounds like a fluent answer to everything and a question to nothing. The buyer delivers the stack, and the rep replies in one turn:

Totally fair. On price, we can phase the rollout to bring the first-year number down. On timing, you could start onboarding now so you're live when the quarter turns. On the CRM, there's a connector your admin can set up. Should we get a follow-up on the calendar with your IT lead?

Each answer is reasonable, and the run still fails all four rows. There is no playback, and the CRM has replaced the buyer's CRM setup. There is no ranking question and three objections are answered in one turn. The rep then jumps to a next step without a single buyer confirmation.

The subtler fail passes three rows. The rep plays back the list, asks which concern decides, and handles price well. Then the rep says Great, so on timing while the buyer is still silent. That run fails the confirmation row only, and it is still a fail.

A fluent answer to every objection with no buyer confirmation fails the confirmation row, however good each answer sounds.

How to debrief a failed run

Debrief one row, not four. Start with the earliest failed row in call order: playback, then ranking, then single handling, then confirmation. Later rows depend on the earlier ones being in place. Use this script:

1. Go to where the buyer finished the third objection. Read me your next line. 2. What was that line supposed to do? Wait for the rep's answer. 3. Give the verdict on one row: The row is the ranking question. Your next line answered price before asking which concern decides the deal. 4. Book the re-run before you leave. Use the same scenario with a different first pick.

If the scorecard's talk/listen ratio runs high on a failed run, treat it as a pointer to the monologue turn, not as the verdict. If a rep fails the same row twice, take that flagged moment into a 15-minute 1:1. Run it in addition to the pipeline 1:1, never in place of it. Keep the drill on a protected recurring block, separate from deal reviews. The full script is in Sales Roleplay Debrief: One Behavior, Re-Run.

A debrief names one row, lets the rep diagnose first, and ends with a re-run on the calendar.

Frequently asked questions

What if the buyer refuses to rank the objections?

Ask once more with the forced version: which one would still stop the deal if the other two were solved. If the buyer still says all of them, handle them in the order they were raised, and get each one confirmed or named open with an agreed return before moving on.

Doesn't the playback slow the call down?

It adds one turn. We consider that a fair price for learning which concern decides the deal and for a transcript that shows each item closed.

How is handling multiple sales objections different from handling a repeated objection?

A stack is several distinct concerns raised together. A repeated objection is one concern raised again after you answered it. The stack drill trains order and confirmation; the repeated-objection drill trains the second response.

Which methodology does the drill assume?

None. The four rows score sequence and buyer confirmation, so they fit any methodology. Load your own objection standards for the handling row.

All insights