"I'm Not the Right Person" — The Redirect That's Either a Gift or a Brush-Off

"I'm not the right person for this."

You will hear that sentence more than almost any other thing on a cold call, and it is the most misread sentence in prospecting. Two reps hear the identical words on the identical day. One of them hangs up with a named referral and permission to use it. The other one hangs up with an info@ address and a warm feeling that goes nowhere.

The difference is not the script. It's that one of them figured out, in about ten seconds, which of the two things they were actually looking at.

Because "I'm not the right person" means one of two completely different things. Sometimes you genuinely called the wrong title. You pulled a list, the data was stale, the guy you dialled runs commercial leasing and you are selling something that lives entirely inside facilities. That is a gift. He knows who owns it, he has no reason to protect them, and he will hand you a name if you ask properly.

And sometimes you called exactly the right person. They own the budget, they own the problem, they have thought about it more than you have — and they are getting rid of you politely, because "I'm not the right person" is a softer exit than "I'm not interested" and it works on almost every rep who hears it.

Same nine words. Two different situations. Here's how to tell them apart before you commit to a path.

The ten-second test

Don't ask them if they're the right person. They just told you they aren't, and asking again makes you sound like you weren't listening. Ask them what they'd do with the problem instead.

"Fair enough. Just so I don't waste the next person's time — if this landed on your desk tomorrow, what would you actually do with it?"

That's the whole test. It's not a trap and it doesn't feel like one, because it's a genuinely reasonable question. You are asking for routing information. Nobody feels cross-examined by a routing question.

What happens next tells you everything.

What a real redirect sounds like

If you called the wrong title, the answer is fast, specific and slightly bored. "I'd forward it to Priya, she runs ops for the eastern portfolio." "That'd go to our head of practice technology, not me." "Honestly I'd bin it, but the person who wouldn't is Dave in network planning."

The tell is specificity without hesitation. They're not thinking about it. There is a name sitting right there because in their world this genuinely is somebody else's job and they route things like this every week. There's also usually a little bit of relief in the voice — they've solved their problem, which was you, by giving you to someone else.

When you hear that, stop selling. Immediately. Do not try one more line about the product. You have won a different game and you should go collect the prize.

What a brush-off sounds like

If you called the right person and they're managing you off the phone, the answer is vague, slow, or it circles back to the pitch.

"Oh, it'd depend." "We'd have to look at it as a group." "I mean, it'd come through procurement eventually." Or the giveaway — they start explaining why they don't need it rather than who would handle it. That's not a routing answer. That's an objection wearing a costume.

The other tell is when they give you a name but the name is a department. "That'd be IT." "Send it to finance." Real referrals have first names. Brush-offs have functions.

And the loudest tell of all: they know the detail. If you're talking to someone who says they aren't the right person but then tells you what system they're currently on and when the contract renews, you are talking to the exact right person. Nobody carries renewal dates for problems they don't own.

Once you know which one you're in, the playbooks diverge completely.

Playbook one: it's a real redirect

Here is where most reps burn a genuinely good outcome. They hear a name, they say "great, could you send me their email?", the prospect says "sure, it's firstname.lastname@", everyone hangs up, and the rep sends a cold email to a stranger with a subject line that says "Referred by Mark" and gets nothing. Because it wasn't a referral. It was a directory lookup done by a human instead of by LinkedIn.

A referral is not an email address. A referral is permission plus context. You want three things, in this order, and the order matters.

One: the name, said back to them

Get the spelling and the exact title, and say it back. "Priya — is that P-R-I-Y-A? And she's got the whole eastern portfolio, or just the retail side?"

This does two things. It gets you accurate data, obviously. But it also drags the prospect one step deeper into helping you. They've now invested thirty seconds in your problem. People who have helped you a little are dramatically more likely to help you a lot — that's not a study I can cite, it's just what I have watched happen on hundreds of calls.

Two: the reason, in their words

"What's the best way to frame this for her? What would make her actually care versus delete it?"

This is the highest-value question in the entire sequence and almost nobody asks it. The person you've got on the phone works with Priya. They know what Priya is measured on, what she's already fighting, and what makes her roll her eyes. In one call I sat on, the answer to this question was "don't lead with cost, she's had cost savings pitched at her all quarter, lead with the reporting because she's the one who has to build the board pack." That single sentence was worth more than the whole list I'd bought.

You are also, quietly, getting qualification for free. If they can't tell you what would make Priya care, Priya probably doesn't care, and you've saved yourself a week.

Three: the handoff, with a specific mechanism

Don't ask "can I mention your name?" That gets a yes and produces nothing, because a mentioned name is just a claim. Ask for an action instead:

"Would you be alright forwarding this to her with one line saying it's worth ten minutes? I'll write the email so it takes you thirty seconds — you just hit forward."

That is a small, bounded, clearly-defined favour with the work already done. If they say yes, send that email within the hour with the forwardable text at the top and everything else below a line break. If they say "just email her directly and say I sent you," that's a weaker outcome but it's a real one — take it, and get the exact phrasing: "What should I say? 'Mark suggested I reach out' or something more specific?"

Then cash it fast. Referral goodwill has a half-life measured in days, not weeks, and the call you make into a warm introduction is a completely different animal from a cold one — the warm call into a principal's referral has its own opening, its own pace, and its own way of failing if you treat it like a cold dial with a nicer first line.

Worked example: the real estate principal

You've dialled a principal at a mid-sized agency. You're selling something that touches property management workflow. He says, forty seconds in, "Mate, I'm not the right person, I'm sales side."

Test: "Fair enough. If it landed on your desk tomorrow, what would you do with it?"

"I'd give it to Sam, she runs the PM division."

Fast, named, specific. Real redirect. So:

"Sam — she's got the whole PM side including the trust accounting, or just the property side? ... Got it. What would make her care about this versus delete it? ... Right, so it's the tenant comms that's the sore point, not the reporting. That's useful. Look, would you mind forwarding this to her with one line saying it's worth ten minutes? I'll write it so all you do is hit forward. What's the best address for you?"

That's the whole thing. Under ninety seconds, and it started with a rejection. Note what you did not do: you did not pitch the principal after he told you it wasn't his problem. Principals in this market get pitched constantly — the whole reason the real estate cold call is hard is that they've already had three proptech conversations this week — and the fastest way to lose the referral is to make him regret picking up.

Worked example: the practice leader

Professional services is different, because the org chart is fake. A partner will tell you they're not the right person and be technically correct and functionally wrong at the same time. Titles at these firms describe billing structures, not decision rights.

So when a practice leader says "you want our COO for that," the test question does extra work:

"Sure. If it landed on your desk though — would you actually have a view, or is it genuinely a COO call?"

Watch what comes back. "I'd have a view, but she signs" is a completely different answer from "no, genuinely not my area." The first one means you keep talking to the person you've got, because you've found an internal champion who just told you they're not the signer. The second is a clean redirect.

When it's the first, you say: "Then let me take two minutes with you rather than starting cold with her, because if it doesn't survive your view it's not worth her time." That's a hard sentence to say no to, and it's the same move that makes the professional services cold call work generally — you get twenty minutes by being the person who respects the twenty minutes.

Playbook two: it's a brush-off

Now the other branch. The answer was vague, they knew too much detail, they told you it'd "go to IT" without a name. You are talking to the owner and they want off the phone.

The rule here is simple and almost nobody follows it: do not argue with the title claim.

The instinct is to say "well, actually, most people in your role are the ones who decide this." It feels like you're correcting a factual error. What it actually does is call them a liar in the first minute of a relationship that doesn't exist yet. You will never recover from it. I've heard reps do this and I've heard the temperature of the call drop through the floor in real time.

Instead, take the exit they offered and put a small hook in it.

The line that earns thirty more seconds

"No problem, I won't push it. Can I ask one thing before I go, and then I'll leave you alone — is it not the right person, or not the right time?"

That's it. It works because it accepts the rejection completely and unconditionally, which removes the pressure they're bracing against, and then it offers them a face-saving alternative that happens to be the truth. People take the true option when it costs them nothing.

What you usually get back is something like: "Look, it's more that we just did this six months ago," or "we've got a freeze until the new financial year," or "honestly we've got bigger fires." Every one of those is real information you did not have ten seconds ago, and none of them are "no forever."

And the promise matters: and then I'll leave you alone. Say it and mean it. If they give you a timing answer, do not immediately pitch. You said you'd go. Go — but go with a date.

Worked example: network ops in telco

Head of network operations, big carrier. You get thirty seconds in and hear "this isn't me, you want architecture."

But then in the same breath: "we've got enough monitoring already."

That second clause is the tell. Architecture doesn't complain about having enough monitoring. You called the right person.

"Understood. One question and I'll get out of your way — is it that it's not you, or that you've already got this covered? ... Right, so you've got the tooling, it's more that nobody's got time to act on what it's telling you. That's a different problem to the one I called about. Can I ask what the plan is there?"

You haven't argued. You repeated their own words back and asked one question about the thing they volunteered. Network ops leaders are relentlessly interrupted and will forgive almost anything except being talked at — which is the whole premise of the telco cold call, where the opening has to earn the second sentence rather than assume it.

The six-week callback that isn't a cold call

If you get a timing answer, get a date. Not "I'll follow up in a while." A date, with a reason attached to their words:

"You said the freeze lifts in July. If I call you the first week of July, is that annoying or is that useful?"

Ask it exactly like that, with the annoying option first. It gives them a genuine out, which means the yes is a real yes. And when they say "yeah, July's fine," you've converted a brush-off into a scheduled conversation you have permission to have.

Then when July comes, your opener is not a cold call. It's: "Jenny — Tim, we spoke in May, you said the freeze lifts this month and to call you. Has that happened?" No introduction, no re-pitching, no "I don't know if you remember me." You are simply doing the thing you said you'd do, which puts you in a category almost no other caller is in.

Write the date and their exact words in the CRM. Their exact words, not your summary of them. "Freeze lifts July, bigger fires until then, doesn't own it but influences" is a note that makes the next call easy. "Not interested, callback July" is a note that makes the next call cold again.

The bit that actually matters

Both of these branches are ten to ninety seconds of talking. Neither is complicated. What makes them hard is that they happen at the exact moment your brain is processing a rejection, and under that load almost every rep defaults to the same two failures — either accepting the brush-off as a redirect and collecting a useless email address, or arguing with a genuine redirect and burning a referral that was sitting there for free.

You don't fix that by reading about it. You fix it by hearing the sentence enough times that the test question comes out of your mouth before you've decided to say it. That's why, if I were building this into my week, I'd spend fifteen minutes running the redirect against a DrillCall scenario until both branches are automatic — hear the vague answer, hear the specific one, and take the right fork without thinking about it — rather than practising on live prospects who only give you one shot each.

The reps who beat you at this aren't better talkers. They just know which of the two calls they're on.