"I'm Not the Right Person For This" — When It's a Redirect and When It's a Brush-Off

The sentence is doing two different jobs

"I'm not the right person for this" is the most useful thing a prospect can say to you and also the most expensive, and the difference is decided in the next fifteen seconds by what you do with it.

One version of that sentence is a human being trying to help you. They genuinely do not own the thing you called about, they know exactly who does, and they would quite like to hand you off and get back to their afternoon. That person is a routing opportunity dressed as an objection. Handled well, you leave the call with a name, a reason, a warm intro and a second contact inside the account. Handled badly — which for most reps means saying "no problem, sorry to bother you" and hanging up — you leave with nothing and you dial the same company again in six weeks from scratch.

The other version is the politest hang-up in the English language. They are the right person. They listened to your whole opener, decided they did not want the conversation, and reached for the one objection that sounds cooperative and cannot be argued with. It is socially perfect. It makes you the unreasonable one if you push. And almost every rep I have watched takes it at face value, because it does not feel like rejection.

So the skill is not "how do I handle the not the right person objection on a cold call." The skill is telling which sentence you just heard, and then running a completely different play depending on the answer. Same words, two branches, and if you run the wrong branch you either burn a real referral or you spend four minutes arguing with someone who was never going to buy.

Free signal: when they said it

Before you ask anything, you already have a tell, and it is free.

A genuine non-owner interrupts you. They cut in early, usually before you have finished the reason for the call, often on the second or third word of your value line. They are not being rude. They heard enough to know it is not their department and they are stopping you to save you both time. The tone is slightly apologetic and slightly relieved.

A deflector lets you finish. They hear the whole thing — the opener, the reason, the ask — and then they say it. Think about what that means. They stayed on the line long enough to evaluate. They understood the offer well enough to route it. And the routing arrived only after the evaluation came back negative. Nobody sits through a ninety-second pitch about a problem that has nothing to do with their job.

The second tell is the shape of the sentence. Real non-owners tend to say who instead of who-not. "That's Priya, she runs that." "You want the ops side, not me." The deflector says the negative half only: "I'm not the right person," full stop, no name attached, waiting to see if you accept it.

Neither tell is proof. They stack, they do not decide. But if someone let you finish and gave you no name, you should be leaning hard toward brush-off before you have asked a single question.

The one question that separates them

Here is the question. Do not ask "who is the right person?" That question invites "I don't know" or "let me check and come back to you," both of which end the call, and it also signals that you are only interested in getting past them.

Ask them to route you with specificity instead.

"That's fair, thanks for telling me. So I don't waste the next person's time — when [the specific thing] comes up, does that land with ops or with finance?"

Two named options, one concrete trigger, framed as you being considerate rather than you being persistent. Now watch what comes back.

Someone who genuinely does not own it answers instantly and adds detail you did not ask for. "Neither, actually, it sits with the regional leads and then Dan signs off." They correct your two options because they know the real map. That confidence is the signal. You cannot fake an org chart you do not carry in your head.

A deflector goes vague. "Um, it would probably be ops, I think." "You'd have to talk to someone in that team." "Try our procurement inbox." They hedge because naming a specific colleague makes them responsible for your next call, and they do not want to be responsible for something they have already decided is not worth doing. Vagueness is the fingerprint. In my experience it is close to a perfect indicator, because the cost of specificity is the exact cost they are trying to avoid.

The honourable exception is genuinely tangled ownership, and you have to allow for it. In regulated and public-sector accounts, people often really do not know who owns a thing, because five people own a piece of it and none of them own the decision. Anyone who has worked a council or a housing association knows the answer to "who owns this?" is frequently "a committee that meets next month," which is why the government cold call script spends its opening seconds pinning down what the officer actually controls before it asks for anything. Same thing in wealth management, where an operations lead may own the process, the risk function owns the veto and nobody owns the budget line — the financial services opener is built to establish that map early rather than assume it. So if the vagueness sounds confused rather than evasive, treat it as a real redirect and help them draw the map.

Branch one: extract the referral properly

You have decided it is real. Now stop selling. Completely. The person on the phone is not a buyer and every second you spend pitching them makes them less willing to hand you their colleague. Your entire job for the next ninety seconds is to leave with four things, in this order.

The name

"Who's picked that up?"

Past tense, not "who's the right person." "Who's picked that up" presupposes that somebody has, and it asks about a fact rather than a judgement. Wait after it. Do not fill the pause with "or if you're not sure, no worries" — that is you giving them the exit for free.

If they only give you a first name, get the rest: "Priya — do you know her last name so I don't call the wrong Priya?" Small, harmless, and it doubles the chance you find her.

The reason

This is the step everyone skips and it is worth more than the name.

"And is that because she owns the budget for it, or because she runs the process day to day?"

What you are collecting is the first line of your next call. There is an enormous difference between "Priya, your colleague said you own this" and "Priya, Mark mentioned you're the one who actually runs the weekly process, and that the reporting side of it has been a headache since the reorg." The second one is not a cold call. It is a call where you already know something true about her week.

While you are there, take the free intel. "Anything I should know before I call her? Has this come up already?" People who have decided to help you will keep helping if you keep asking easy questions. This is often where you learn they looked at a competitor last year, or that the whole thing is frozen until a system migration finishes in the spring.

Permission to use their name

"When I call Priya, is it fair to say you suggested it?"

Never assume this. Ask it out loud, because the answer tells you how strong the referral actually is. "Yeah, of course, tell her I sent you" is gold. "Um, maybe just say you were passed along" tells you the relationship is thin and you should treat the next call as barely warm. And you must ask, because dropping someone's name without permission is how you get one call and no second one.

Keeping them involved

This is the part almost nobody does and it is the whole reason the branch is worth running.

"Would it be easier if I put it in an email to her and copied you, so it doesn't land out of nowhere?"

Notice the framing. It is not "could you introduce me" — that is work for them and most people quietly never do it. It is "I will do the work, you just have to be visible on the thread." The cost to them is zero. And the effect is that your next email arrives with an internal colleague's name in the CC field, which is a completely different object than a cold email.

If they say yes, send it the same hour, keep it three sentences, and put the reason in the first one. If they say no, you still have the name and the permission, and you go direct.

One more line before you let them go, and it is worth the eight seconds:

"Last thing — if Priya says it's not her either, who else touches this?"

You are buying a spare. Routing chains inside big accounts are longer than anyone admits, and having the second name in your pocket means the next dead end does not send you back to the switchboard.

Branch two: they are the right person and just don't want the call

Different play entirely. Do not ask for a name — you will get a fake one, or a shared inbox, and you will spend a week chasing a ghost.

The mistake here is arguing about ownership. "Well, our other customers usually find the Head of Ops is involved" is you telling someone you know their job better than they do, on a phone call they did not want, in the first minute. You lose that argument even when you are right.

Instead, give ground on the label and take back the relevance.

"Fair enough, I might have the wrong door. Can I check one thing and then I'll leave you alone?"

That sentence does three things. It concedes, which drops their guard. It caps the call, which is the only reason they stay on. And "can I check one thing" is a tiny ask that is awkward to refuse after you have just agreed with them.

Then you ask the question they cannot comfortably take the exit on:

"When [the specific painful event] happens — the invoice bounces back, the rota has a hole in it on a Friday afternoon, whatever it is — does that reach your desk at all, or does it genuinely never get to you?"

"Genuinely never" is the load-bearing phrase. You have handed them a clean way out and made it explicit, which means taking it is a statement rather than a dodge. People will deflect all day, but they will not usually claim outright that a problem sitting in the middle of their job never reaches them. What comes back most often is some version of "well, I hear about it, but I'm not the one who decides."

And that is the honest answer, and it is not a no. That is a person telling you they are an influencer, not an economic buyer. So run the influencer play: stop asking for a decision and start asking for their view. "That's actually what I wanted — I don't need you to decide anything. I want fifteen minutes of what it looks like from where you sit, because if it's not a real problem for you then it's definitely not worth taking to whoever does decide." You have just made the meeting cost them nothing and flattered their judgement, both of which are true.

The staffing world is full of this one. Call a VP of Recruiting and you will often be told to speak to the branch managers, when the VP is the person who signs and the branch managers are the people who will be told what to use — which is exactly why the staffing and recruiting script treats the downward deflection as a signal to re-anchor rather than a routing instruction. Downward deflection is nearly always a brush-off. Upward and sideways deflection is nearly always real. Nobody sends you to their boss to get rid of you.

Cashing the internal referral so it doesn't go cold again

A referral has a shelf life measured in days. Sit on it for two weeks and the goodwill has evaporated, the colleague has forgotten the conversation, and you are cold again with an extra name.

The warm call is structurally different from the cold call and reps who do not know that waste the advantage. You do not open with a hook, because you do not need one — the name is the hook. First sentence: the referrer and the relationship. Second sentence: the reason they were pointed at you, in the referrer's words, not yours. Third sentence: the ask, small and time-boxed. That is the entire opening, and it should take well under a minute, which is the shape laid out in the healthcare warm call script — the ninety-second version aimed at a CMIO works because it spends none of its time earning attention and all of it establishing relevance.

The one thing to guard against: do not oversell the strength of the referral. "Mark told me to call you" when Mark said "you could try Priya" is a lie that gets discovered in the first internal conversation, and it costs you both contacts. "Mark mentioned you run this" is accurate and does the same work.

When it really is a dead end

Sometimes it is nothing. They do not own it, they do not know who does, they have no interest in finding out, and the account is not worth the archaeology. That is fine. Get off the phone quickly and politely, log the actual words they used in the CRM, and move.

What you should not do is log it as "not interested." That is the field that gets your account quietly buried for a year. "Says ownership sits elsewhere, no name given, let me finish before objecting" is a note that tells the next rep — possibly you in three months — that this was a brush-off from someone who listened all the way through. That is a warm account with a bad first call, not a dead one.

What I'd do with this on Monday

Pull five calls from the last month where you heard this objection and you accepted it. Listen for when in the call it came, and whether you got a name. My guess is you will find at least one where the person let you finish, gave you nothing, and you thanked them and hung up. That was a live conversation you walked out of.

Then practise the two branches out loud until the diagnostic question comes out of your mouth without you deciding to say it, because on a real call you have about two seconds to pick a branch and no time to think. That is exactly the kind of thing DrillCall exists for — running the same objection at you over and over until the redirect and the brush-off sound different to your ear, which is not something you can learn from reading a script.

The reps who get good at this stop treating "I'm not the right person" as the end of a call. It is a fork. Take the wrong branch and you lose the account twice. Take the right one and the objection was the most productive thing that happened all morning.