When They Say 'We Already Use Someone': What Confident Reps Say Next

You already know the freeze. Your prospect says "We already use someone for that" and your mind just stops. You apologize and hang up, or you keep talking to fill the silence and watch them check out.

The problem isn't that you don't know your product or your pitch. It's that you haven't said the right response out loud before the real call happens. When it does happen, your brain is scrambling for words instead of staying focused on the reason you actually called.

Confident reps never freeze here. They have three things ready: one thing they name to validate the customer, one specific gap their current setup might not cover, and one question to keep the conversation going. That's it. Everything else is just staying calm and letting the customer answer.

Here's what that looks like.

Why "We Already Use Someone" Freezes Most Reps

The objection hits you from a different angle than you trained for. You rehearsed your pitch. You practiced your feature story. But when someone says "we already have one," you're trying to fit your pitch into the wrong moment.

The customer isn't saying they don't need the category. They're saying that need is already filled. So your brain looks for what you prepared (features, benefits, comparisons) and finds nothing that fits.

Most reps solve this by giving up. They apologize, excuse themselves, and hang up. Or they try to sell harder, which loses the customer faster.

What they didn't practice is the one thing that actually works: naming one specific problem their current setup might not solve, and asking if it matters to them.

What Confident Reps Say Back (The Framework)

The response has four parts, and all of them together take 15 to 30 seconds.

First, validate. "Makes sense" or "I hear you" tells the customer you processed what they said. Don't linger here. One sentence, max.

Second, give a reason to stay. "The reason I called is..." followed by one specific gap. Not a feature of your product. A problem with how most current setups handle a specific scenario. "Most employer plans have gaps when life changes" or "Most help desks don't handle scenario X well" or "Most vendors in that space don't cover compliance for Y."

Third, ask a question. "Quick question: with your setup, how are you handling Z?" or "Have you run into that?" Turn the conversation from "you don't need me" to "do you have this specific problem?"

Fourth, stop talking. Let them answer. Silence is your friend here.

Real Scenarios Across Sales, Service, and Claims

Insurance cold call. Customer: "I already have insurance through my employer."

Confident rep: "Makes sense. The reason I called is most employer plans have big gaps when life changes. Quick question: have they walked you through what happens to your coverage if you left that job?"

Customer service. Customer: "We already have a help desk."

Confident rep: "I hear that. The reason I'm reaching out is most help desks don't handle escalations the way urgent issues need. Have you had problems with wait times on critical tickets?"

Claims or back-office. Customer: "We already use a vendor for that."

Confident rep: "Makes sense you'd standardize. What I'm seeing is most platforms in that space don't flag compliance issues well. Are you running into that with what you have now?"

The pattern stays the same every time. Validate, name one gap, ask if they feel it. Don't defend your product. Don't list features. Just name one problem and see if it matters to them.

Why This Response Actually Works

When someone says "we already use someone," they're not rejecting you. They're closing the door on the entire category. A feature pitch doesn't reopen it.

But naming one specific problem with their current setup does something different. You're no longer asking them to switch vendors because you're better. You're asking them if they have a problem their current vendor doesn't solve.

That's a different conversation. It moves you from "do you need this?" to "do you have this?"

When you ask that question, stop talking. The silence that follows tells you everything. If they start explaining their workaround or naming a frustration, you've held their attention. If they say "nope, we're good," they're being honest, and you've done your job.

Either way, you didn't freeze. You stayed focused. You had one reason to call, you named it, and you let them decide if it mattered.

From Knowing It to Saying It Naturally

You can read this response right now and know it's right. But knowing it and saying it on a real call are different things.

When the objection hits on a real call, you're managing three things at once: your tone, your pace, and your words. If you haven't said them out loud before, your brain freezes trying to do all three.

That's why confident reps practice. They've already said the response a dozen times before the real call happens. They've felt the pause that follows the question. They know how long two seconds of silence actually is. They know their exact words for that specific gap.

Knowing and saying are built differently. Practice is the bridge.

If you want to practice this response before a real call, search Hinahon in the App Store or Google Play.

Frequently Asked Questions

What if acknowledging their solution makes me sound unsure of my value?

The hesitation here is usually about the rep's own confidence in the gap they're about to name. A quick, confident acknowledgment ("Makes sense" or "I hear you") isn't accepting their objection as final; it's saying you listened and you're moving forward with intent. The rep who skips it sounds tone-deaf or defensive. The rep who acknowledges confidently and immediately pivots to a specific gap sounds professional and prepared. If the gap is real and specific, the acknowledgment adds credibility, not weakness.

What if they say it angrily or dismissively, does the response change?

The words stay the same, but tone and pace shift. Pause longer before you speak. Drop your pace. Keep your voice calm and level. You're not reacting to their frustration; you're modeling that this conversation is worth a steady, thoughtful pace. Tone-match anger and you lose them. Stay calm and you tell them this is worth taking seriously.

What do I say if they push back on my response?

Move to a specific pain point with their current solution. Ask what they're running into with the vendor they have. Don't defend your response or your product. Confident reps don't sell back; they clarify what problem the customer is still having with what they're using now. That keeps the focus on their gap, not your pitch.

What if I stumble on the actual call or forget the exact words?

The exact phrasing matters less than the structure. If you freeze mid-call, pause and name what you're trying to do: "The reason I called is most [solution type] don't handle [specific gap] well. Have you run into that?" Stumbling on words is recoverable. Stumbling on your reason for calling is not. When you've said the framework a dozen times before, your brain can rebuild the phrasing even if you forget a specific phrase.

What changes if they mention this on an inbound call?

On an inbound call, they called you for a reason. Their current solution isn't fully solving for it. Don't gloss over that signal. After you acknowledge, ask why they called. "If you already have someone, what brought you to reach out?" Let them tell you what's not working. On an inbound call you've already got their attention; use it to understand their real gap instead of guessing at one. The framework stays the same (validate, name a problem, ask), but inbound flips the question. You're asking them to tell you the gap, not you guessing at it.