The objection isn't what kills the call. The next 20 seconds are.

Pull five calls you lost last month. Not the dead leads — the real ones, where the customer engaged, asked questions, and then went quiet.

Listen to what happens right after the customer pushes back. Not the objection itself. The reply.

You'll hear the same handful of moves over and over. They're not random. They're habits, and they show up in almost every losing call regardless of industry, price point, or rep tenure.

Here are the patterns worth naming, how to hear them, and what to run instead.

Pattern 1: Answering a price objection with a price answer

Customer says "that's more than I was hoping to spend." Rep immediately goes to financing terms, a discount, a cheaper package.

The rep thinks they're being responsive. What they're actually doing is confirming that price is the problem, closing off any chance to find out what's underneath it.

"That's more than I expected" can mean six different things:

  • I compared you to a competitor and you're higher
  • I had a number in my head from three years ago
  • I can afford it but I don't see why it costs that
  • My spouse set the budget and I'm not the decision maker
  • I'm testing to see if you'll fold
  • I genuinely cannot pay this

Four of those are not price problems. But the second the rep drops the number, all six get treated the same way.

What to run instead — ask before you move:

"Totally fair. Help me out so I don't waste your time — is it that the number's higher than you budgeted, or higher than you expected it to be? Those are different problems and I can only help with one of them."

That one question splits the pile. Budget problem means you talk scope and payment. Expectation problem means you talk value and comparison. Reps who skip it discount their way into a loss and never learn why.

How to hear it on a recording

Time the gap. From the end of the customer's price objection to the rep's first number, count the seconds. Under three seconds and no question in between? That's the pattern. It's one of the easiest things in the world to score because it's binary — did a question come first, yes or no.

Pattern 2: The rebuttal that arrives before the objection is finished

Losing calls are full of overlap. The customer starts to explain a concern and the rep begins talking at word eight.

Customer: "We've actually been working with another company for about —"

Rep: "Right, right, and a lot of our customers came from them, what we do differently is —"

The customer never got to the part that mattered. Maybe the relationship is with a vendor whose contract ends in 40 days. Maybe their contact just left. You'll never know, because the rep buried it.

The fix is mechanical, not philosophical. Train a one-beat pause. After the customer stops talking, count one. Then speak.

It feels like forever to the rep. It's invisible to the customer. And it catches the second half of objections, which is where the real information lives — people lead with the socially acceptable version and follow with the true one.

"We're pretty happy with who we've got... though honestly their service has been slow since the summer."

The rep who interrupts never hears the second clause.

Pattern 3: Treating a stall like an objection

"Send me some information." "Let me think about it." "I need to talk to my partner."

These aren't objections. An objection is a stated reason not to buy. A stall is the absence of a reason — the customer ending the conversation without telling you why.

Losing calls handle stalls by agreeing to them.

Customer: "Just email me something and I'll look it over."

Rep: "Absolutely, what's the best email?"

That call is over. The email gets opened or it doesn't, and the rep has no control either way.

Winning handling treats the stall as an incomplete sentence and finishes it:

"Happy to. So I send the right thing — when you look it over, what's the part you'll be deciding on? Price, timeline, or whether it's the right fit at all?"

Or for the partner version:

"Makes sense. When you talk to her, what do you think her first question's going to be? Let's make sure you've got that answer, because if you don't, you'll just be scheduling another call with me."

You're not blocking the exit. You're making the exit produce information.

What this looks like in a scorecard

Separate the two in how you score. "Objection handled" and "stall converted" are different skills and most reps are fine at the first and terrible at the second. If you lump them together you'll keep coaching the thing they already do well.

Pattern 4: Over-answering

A single objection gets a 90-second response. The rep covers four angles, three proof points, a story about another customer, and a warranty detail nobody asked about.

Long answers read as defensive. They also give the customer four new things to object to.

The pattern is easy to spot in a transcript: look at the rep's word count on the turn immediately following any objection. If it's three or four times longer than their average turn, you've found it.

Target: answer in two or three sentences, then hand it back.

"Fair concern. Installs run two days and we schedule them three weeks out, so you'd be done well before the holidays. Does that timeline work on your end?"

Done. The question at the end is not optional — it's what stops the rep from filling the silence with more talking.

Pattern 5: Accepting the first "no" as final — or ignoring it entirely

Two failures, opposite directions, both common.

The first rep hears a soft no and folds immediately. "No problem, I'll follow up in a few months." No attempt to understand it.

The second rep hears a soft no and pushes the same pitch harder, louder, a second and third time. The customer stops arguing and starts getting polite. Polite is the sound of a lost deal.

The middle is one honest attempt to understand, then a decision:

"Okay — before I let you go, can I ask what tipped it? Not to talk you out of it, I just want to know if I missed something or if it's genuinely not a fit."

Customers answer that question far more often than reps expect, because it doesn't sound like a close. And the answer is worth more than the deal was — it tells you whether the loss came from the product, the price, or the way the rep ran the call.

Pattern 6: No objection at all

The quietest losing call is the one with zero pushback. The customer agrees with everything, says it sounds great, and disappears.

If your rep's calls have no objections in them, that's not skill. It's one of two things: they're pitching so vaguely nothing is worth disagreeing with, or they never asked a question specific enough to provoke a real answer.

Count objections per call across your team. The rep at the bottom of that count is usually not the smoothest rep. They're the one having the shallowest conversations.

How to run this on your team this week

Don't try to fix all six. Pick one.

  1. Pull ten calls — five won, five lost, same rep or same lead source.
  2. Mark every customer objection with a timestamp.
  3. For each one, write down only two things: did a question come before the answer, and how many sentences was the answer.
  4. Compare won to lost.

You'll see the gap in about 20 minutes, and it'll be specific enough to coach on Monday. "Ask one question before you answer price" is a sentence a rep can actually carry into the next call. "Handle objections better" is not.

If you're reviewing enough volume that tagging objections by hand stops being realistic, that's the point where tooling like MoreSignal earns its keep — scoring every call for the same two things instead of the five you had time for. But start by hand. You need to hear the pattern yourself before you'll trust a score that points at it.