"I Don't Handle That Anymore" — The Redirect That's Half True

Two people say the exact same sentence

You get past the opener. You get your one line out. And before you can ask the question you actually called to ask, you hear it:

"Yeah, I don't handle that anymore."

Here's what makes this one hard. Two completely different people say that sentence, in the same tone, with the same amount of friendliness, and there is no way to tell them apart from the words alone.

The first person is telling you the truth. Their company reorganized in January. The category moved to a new function. They used to own it, they don't now, and they are mildly annoyed that your list is nine months stale — but not at you personally.

The second person owns it fine. They just don't want to talk to you, and "I don't handle that anymore" is the most socially frictionless exit in the English language. It's not a lie they have to defend. It doesn't require them to be rude. It makes you the one who made the mistake, which means you'll apologize and hang up, and they get their morning back.

Most reps treat both versions the same way. They say "oh, sorry to bother you, who should I talk to?" get the answer "probably IT," say thanks, and hang up. That call produced nothing. You didn't get a name, you didn't get a reason, you didn't get permission, and you burned a phone number that was actually reachable — which, on a cold list, is worth more than most of the numbers on it.

The good news is that you can tell the two apart with one question, and both versions can be converted into something. Not the same something. But something.

The one question that sorts them

After they say it, you say this. Flat. No apology in your voice, no "oh gosh sorry." Just:

"No problem — who picked it up?"

Then shut up.

That's it. That's the whole diagnostic. The reason it works is that it's an easy question for an honest person and an awkward question for someone improvising.

If the redirect is real, they answer fast and they answer with a human being. "That's Dana now." "Marcus took that over when we split the group." They don't have to think, because the answer is a fact they live with every day. They may even volunteer the story — we split procurement in two, my half is indirect now — because people like explaining their own org chart.

If the redirect is a brush-off, you get a department. "Probably IT." "That'd be operations." "You'd have to check with corporate." Nobody who genuinely handed off a function refers to the person who took it as "corporate." A department name is what you say when you need to produce an answer and you don't have one, because you were never actually redirecting — you were leaving.

There's a third response worth naming: the pause. Two, three seconds of nothing, then a department. That's the sound of someone deciding what to say. Treat it exactly like the department answer.

Notice what the question does not do. It doesn't accuse anyone. If you're wrong and it really is IT, you've lost nothing and you sound like a professional who wanted to get it right. I've asked this thousands of times and I have never had someone get offended by it. The worst outcome is "I don't know," which is itself information — they're not close enough to the thing to know who owns it, which means even the real version isn't going to be a great referral.

When you get a department: don't leave yet

You've now established, quietly and without saying so, that you're probably still talking to the person who owns the problem. So do not accept the routing. Not yet.

Here's the move. You give a thirty-second value statement before you let them send you anywhere. Frame it as courtesy, which is also what it genuinely is:

"Totally fair. Before I go bother the wrong person over there — can I give you fifteen seconds on why I called, so you can tell me whether it's even worth passing along?"

That sentence does two things. It asks for a tiny amount of time, which is easy to grant. And it hands them a job they're qualified for — judge whether this matters — instead of a job they've already refused, which was talk to a salesperson.

Then you deliver the thirty seconds. Not your pitch. Not your company's positioning statement. The specific, concrete problem you solve for people in their exact seat, said in the words they'd use, ending in a question that isn't a meeting request.

"We work with plants in the two-to-four-hundred-headcount range. The thing we keep running into is that maintenance is scheduling around a spreadsheet that only one person really understands, and when that person takes vacation the whole month gets reactive. That's the problem we fix. If that's not a thing there, I'll drop it and stop calling."

That last clause matters. You have given them a graceful exit that is cheaper than the fake redirect. If they wanted rid of you, the easiest thing in the world is now to say "yeah, that's not us." And a decent number of people will say it, and that's fine — you got a real disqualification instead of a fake referral, which is a better outcome for your pipeline than you think.

But a decent number will do something else. They'll correct you. "It's not the spreadsheet, it's that we can't get parts." That is not a redirect anymore. That is a discovery call starting. The thing that killed the brush-off wasn't persistence; it was giving them something specific enough to disagree with. The same mechanic sits underneath every good opener I've written — the manufacturing cold call script I use with plant managers is built almost entirely around saying one thing precise enough that being wrong is still useful.

The question that works when they're still stonewalling

If they hold the line — "look, it's really not me anymore" — there's one more thing worth asking, and it's the single most underused question in this whole situation:

"Understood. Last thing and I'll let you go: if it were still yours, what would you want to know before you took a call like this?"

This is a gift of a question. It costs them nothing. It's flattering in a way that isn't gross, because it's asking for expertise rather than time. It's hypothetical, so there's no commitment attached. And people love answering it.

What comes back is either a real answer — "honestly the only thing I'd care about is whether it plugs into our existing system, because the last three vendors said yes and lied" — or nothing. If it's a real answer, you now have the qualification criteria for the entire account, given to you by an insider, in their language, for free. If they were faking the redirect, you also just got them to reveal what they actually care about, which makes your follow-up email lethal.

And if it's nothing? Then it was a real handoff and they're genuinely disengaged, and you've lost fifteen seconds.

When you get a name: run the full referral sequence

Now the other branch. They gave you a name in under two seconds. This is a real redirect, and it is worth much more than most reps extract from it.

The mistake is stopping at the name. A name is the floor. Here is what I ask for, in order, and it takes maybe forty seconds total.

One — confirm the scope. "Got it, Dana. Does she own the whole thing or just the [X] side?" You are checking whether the handoff was clean. Half the time it wasn't, and you learn there's a second person, or that the person you're speaking to still owns a piece. That's a foot back in the door with someone who's already talking to you.

Two — the why. "Was that a reorg, or did the role just move?" This sounds like small talk. It isn't. "We centralized it under the new VP" tells you the buying process changed and probably got slower. "It moved when Dana joined in the spring" tells you Dana is new, which means Dana has a mandate and a budget and a reason to take calls. New people in a seat are the most receptive buyers on any list I've ever worked.

Three — the permission, asked properly. Not "can I use your name?" — that's a yes/no that people reflexively soften. Ask:

"When I reach out to her, is it fair to say you pointed me her way?"

That's a lower bar and a truer statement. They did point you her way. They're just confirming you can say so. Almost everyone says yes, because it's accurate and it costs them nothing.

Four — the one nobody asks. "Do you tend to forward things to her, or is she better on the phone?" You're asking a person who works with your prospect every day how to reach your prospect. That intelligence is not available anywhere else. "She never answers her desk line, everything goes through Teams." "Honestly just email her, she reads everything at six a.m." I have had this one question save me two weeks of dialing a phone that was never going to ring.

Five — the ask you're not entitled to but should make anyway. "Any chance you'd be willing to drop her a two-line note so it's not completely cold?" Say it lightly. Accept no instantly and cheerfully. Most people will decline, and that's fine. Some won't, and a two-line internal forward from a colleague is worth more than any sequence you will ever write.

This whole sequence is the same discipline as any good multi-threaded call — you're not trying to win the meeting on this call, you're trying to leave with more than you arrived with. It's the logic behind the financial services script I use with wealth management COOs, where the person who picks up is very often not the person who signs, and the entire value of the call is the map you build of who is.

The follow-up email that names the redirect

Here is the part people skip, and it's the highest-response cold email I've ever sent. Not because it's clever. Because it isn't cold.

You email the new person, and you put the redirect in the subject line and the first sentence, by name.

Subject: Rob Feeney pointed me your way

Dana —

I called Rob about maintenance scheduling this morning and he told me it moved to you in the spring, so I'm following his advice.

The reason I called him: we work with plants your size where the schedule lives in one person's spreadsheet, and the month goes reactive whenever that person is out. Rob said the piece he'd want to know about is whether it plugs into what you already run — so, short answer, it does, and I'm happy to show you exactly how in ten minutes.

Worth a look, or should I let it go?

Tim

Look at what's doing the work there. A real name in the subject line, which means it reads as internal. A verifiable first sentence — Dana can walk to Rob's desk and check, and it will hold up. The specific concern Rob raised, which proves the conversation happened and pre-answers the objection. And a closing question that gives permission to say no, which is what makes people answer instead of ignore.

Send it the same day. The referral decays fast — a week later, Rob doesn't remember the call, and if Dana checks, you look like you're name-dropping a stranger.

One rule on this email that I'd tattoo on people: write only what you can defend. "Rob pointed me your way" is defensible if Rob said "talk to Dana." "Rob suggested we connect" is a stretch. "Rob asked me to reach out to you" is a lie, and it is the exact kind of lie that gets discovered in a hallway and kills the account permanently. The whole power of this email comes from being true. Don't trade that for a slightly better verb.

Opening the next call without overclaiming

Same discipline on the phone. When you dial Dana, you open with borrowed authority, and the trick is borrowing precisely the amount you were actually given.

"Dana, my name's Tim. I spoke to Rob Feeney this morning about maintenance scheduling and he told me it sits with you now — so this is a cold call, but at least it's a well-directed one."

That little bit of self-awareness at the end does more than it looks like. You've told her exactly what this is. You've shown you did the work to find the right person. And you've named a colleague without claiming an introduction you didn't get, which means when she says "Rob mentioned this?" you can say "he mentioned you own it — I asked him who to call" and the whole thing stays clean.

Compare that to the rep who opens with "Rob asked me to give you a call." It plays better for four seconds and then it's radioactive. In any account where people talk to each other — which is all of them, and especially the tight partner-led ones I write about in the professional services script — the overclaim gets found out.

The part that actually determines whether you can do this

Everything above is easy to read and hard to execute, for one reason. "I don't handle that anymore" arrives at a moment when you are already slightly off balance, and the honest human instinct is to apologize and get off the phone.

You will not think your way out of that in real time. The only thing that works is having said "No problem — who picked it up?" enough times that it comes out of your mouth before your nervous system catches up. Same for the fifteen-second ask, same for the permission question. These have to be reflexes, not decisions.

So drill them. Say the diagnostic question out loud until it sounds bored rather than hopeful. Practice getting the department answer and rolling straight into the value statement without a beat of dead air, because the dead air is what tells them you weren't expecting it. Practice being told no on the intro request and moving on cheerfully, because the flinch is what makes it awkward.

If you don't have a partner to run that with, that's the specific problem I built DrillCall to solve — you get a prospect who throws the half-true redirect at you and holds the line, so you can burn through twenty reps of it on a Tuesday night instead of learning it on live accounts. Whatever you use, the point stands: the redirect is one of the three or four sentences you will hear every single day of your career. It deserves to be rehearsed like a line, not improvised like a surprise.

Get good at this one and the wrong-person objection stops being a dead end. Half the time you're still talking to the right person. The other half, you leave with a name, a reason, permission to use it, and an email that doesn't read cold. That's a good call either way.