Smokescreen Objection Playbook: 'Busy' vs 'Who Are You?'

Smokescreen Objection Playbook: 'Busy' vs 'Who Are You?'

I spent the last two weeks on calling events that taught me something I should've learned years ago: not all objections mean the same thing, and treating them the same way kills deals.

Here's what happened. We ran back-to-back calling campaigns with fresh teams. Some reps reported high callback rates but low meeting closes. Others got fewer callbacks but moved prospects faster into meetings. At first, I thought it was rep quality. It wasn't. It was objection interpretation.

There are two objections that sound similar but absolutely require different responses. Confusing them costs you meetings you should have won.

The first is the "Busy" objection. When someone says "I'm swamped right now" or "This isn't a good time, can you call back Thursday?", they're telling you they're interested but genuinely preoccupied. I call this an interest signal. The person hasn't rejected your premise. They've just deprioritized the conversation. Your job is to earn the callback.

Here's where I see reps blow it: they treat "busy" like a "no" and they pivot hard. They sell harder. They try to convince the person the call is worth interrupting for. Wrong move. When someone is busy, respecting their time and building confidence in the callback is what converts.

Last week, one of my best reps got "I'm in the middle of a client call right now" from a prospect at a real estate firm. His response: "Totally get it. I won't keep you. Quick question before you go, though: if I called back Thursday at 10am, would that work?" She said yes. He set a calendar reminder, called exactly at 10am, and booked the meeting. He treated "busy" as a scheduling problem, not a rejection problem.

The second objection is "Who are you?" This sounds like genuine confusion, but it's almost never that. It's a control test. Someone who doesn't know you is checking whether you have confidence in what you're selling and whether you panic under mild pressure. If you treat this like a "busy" objection and back off respectfully, you lose momentum.

I watched a newer rep on our team get hit with "I'm not familiar with your company" from a prospect at a tech firm. His response was polite deflection: "Yeah, we're pretty new to your space. Happy to send some info." The prospect said thanks, took the materials, and never responded.

Same day, another rep got the exact same objection from a similar prospect. His response: "That's exactly why I called. We're working with firms like yours on a specific problem right now, and I wanted to see if it applies to you. We found that companies in your space waste about two weeks a year on this one thing. Have you noticed that?" He kept momentum, asked a direct question, and got the meeting.

The pattern is clear. "Busy" is about respect and callbacks. "Who are you?" is about confidence and momentum.

Here's the test I use now: Does the objection assume I might be worth their time later, or is it testing whether I belong in the conversation at all?

"Busy" = they're assuming you're worth their time, just not now. Build the callback, respect the timing, reference specific details so they remember you're credible.

"Who are you?" = they're testing your credibility in real time. Give a direct answer, don't over-explain, ask a specific question, stay in control.

I've adjusted how I train teams. First, I show them how to recognize the difference instantly. Then I teach them two separate playbooks. For "busy" objections, we script callback frameworks with specific days and times. For "who are you" objections, we script confident redirects that turn it into a discovery question.

The result: callback rates stayed high, but close rates from callbacks jumped 40%. We're booking more meetings from the same call volume because we're not wasting momentum on the wrong response.

The lesson is simple. Not all objections are obstacles. Some are signals that tell you exactly what to do next. Listen to which one you're hearing, and respond accordingly.