"I'm Not the Person Who Handles That" — Deflection, Truth, or Both

The Six Words That End Most Calls

"I'm not the person who handles that."

Every SDR has heard it. Most apologise, ask for a name, get a vague "just call the main line," and hang up. The call is over in under ninety seconds and the rep logs it as a gatekeeper block or a bad contact. On to the next dial.

I have done this myself more times than I want to admit. Early in my career, I treated that sentence like a locked door. It is not a locked door. It is a hallway. The person on the other end just told you they know where the right room is. Your only job is to walk down the hallway with them instead of turning around.

Here is how I handle it now, why most of the deflections you hear contain real information even when they are also a brush-off, and the exact words I use to turn "wrong person" into a warm introduction.

Why Reps Fumble This Moment

When someone says "I'm not the right person," a new rep hears rejection. An experienced rep hears something more interesting: the person just implicitly confirmed that somebody at the company handles the thing you called about. They did not say "we don't do that" or "we're not interested." They said the responsibility lives somewhere else.

The reason most reps fumble it is they shift into apology mode. "Oh, sorry to bother you — do you happen to know who I should reach out to?" That question is polite and completely powerless. It gives the other person permission to say "not sure, try the main number" and end the conversation with zero friction.

The deeper problem is that reps treat this as a routing problem and only a routing problem. Half the time it is. But the other half, the person you are talking to is actually involved in the decision — they just do not want to have a sales conversation right now, or they genuinely believe someone else is the "official" contact. Both of those scenarios are workable if you do not bail out of the call.

The Three-Sentence Response

Here is the framework I use. Three sentences, in order, every time.

Sentence one — validate without apologising. "That makes sense — this touches a few different people at most companies."

You are not sorry. You are not flustered. You are casually acknowledging that org charts are complicated, which they already know.

Sentence two — name what you want and why it matters to them. "If I could get to the right person, it would save you from getting calls like this one in the future."

This reframes the referral as something that benefits them. Nobody wants to keep getting cold calls meant for someone else. You just gave them a selfish reason to help you.

Sentence three — ask for the name and the context. "Who over there usually owns decisions around [specific problem], and what's the fastest way to reach them?"

Notice I did not ask "who handles purchasing" or "who's in charge of vendor selection." I asked who owns the problem. That question gets you a different name — usually someone more senior, someone who actually feels the pain — than the procurement question does.

The full thing, spoken naturally, takes about ten seconds. Here is what it sounds like in practice:

"That makes sense — this touches a few different people at most companies. If I could get to the right person, it would save you from getting calls like this one in the future. Who over there usually owns decisions around downtime on the packaging lines, and what's the fastest way to reach them?"

Most people will give you a name. Many will give you a direct number or an email. Some will transfer you on the spot.

The Follow-Up Question That Changes Everything

Before you let them go, ask one more thing:

"When something like this has come up before — new tooling, a process change, whatever it is — were you part of that conversation at all?"

This is the question that reveals whether you are actually talking to an influencer. The answer is almost always some version of yes. "I mean, they'd loop me in eventually" or "I'd have to sign off on the implementation" or "I sit on the committee but Karen runs point."

Now you know two things. First, the name they gave you is real and relevant, because they just described a process that involves both people. Second, the person you are already speaking with has a role in the decision, which means you can say:

"Got it — so you'd be involved on the [implementation / clinical / operations] side. Would it make sense for me to copy you when I reach out to Karen, so you have context if it moves forward?"

You just turned a deflection into two contacts and permission to use one person's name with the other. That is not a failed call. That is pipeline.

The Internal-Referral Email

Once you have a name and a reason to use it, send the email the same day. Not tomorrow. The same day, while the person who gave you the referral still remembers your call.

Here is the template I use:

Subject: [First name of referrer] suggested I reach out

Hi [New contact],

I was speaking with [Referrer name] earlier today about [one-sentence version of the problem you solve]. [He/She] mentioned you're the person who typically owns that area.

I'm not going to pretend [Referrer] and I are old friends — it was a short call. But [he/she] thought it was worth connecting us, and I'd like to give you a quick look at what we're doing for [similar company type — "other packaging plants in the Southeast" / "multi-site health systems" / "mid-size consulting firms"].

Would a fifteen-minute call on [specific day] or [specific day] work?

Two things matter in this email. First, you are honest that the referral came from a brief phone call, not a deep relationship. Lying about this destroys trust before you have any. Second, you name a specific and relevant peer group so the reader can self-identify. "Other packaging plants in the Southeast" is a mirror they can see themselves in.

Copy the original contact if they gave you permission. Even if they didn't explicitly say yes, cc'ing them is usually fine — they gave you the name, after all — and it adds social pressure for the new contact to respond.

Vertical-Specific Handling

The deflection sounds different depending on who you are calling. Here is how I adjust.

Plant Managers Who Push You to Corporate

This is the most common deflection in manufacturing. You call a plant manager about downtime, yield, maintenance costs — something they feel every day — and they say "that's a corporate decision" or "you'd need to talk to our VP of operations."

The thing is, plant managers almost always influence these decisions even when they don't make them. Corporate does not buy a new piece of equipment or a new maintenance platform without asking the plant what they need.

After the three-sentence response, I use this follow-up: "When corporate has evaluated something like this before, did they come to you and your team for input on what's actually happening on the floor?"

The answer is almost always yes. Now you can position the plant manager as someone who gives corporate a reason to look at you, rather than someone who blocks you from corporate. If you are calling into manufacturing and want the full approach for getting time with plant-level decision makers, the manufacturing cold call playbook walks through this in detail.

Clinical Staff Who Push You to IT

"That's an IT decision" is the healthcare version of "talk to corporate." You call a chief medical information officer or a VP of clinical operations about a workflow problem and they tell you to call the IT department.

Sometimes this is true. Health systems have strict procurement channels and IT often does own vendor selection for anything that touches the EHR. But clinical leadership defines the requirements. IT implements what clinical leadership asks for.

My follow-up here: "Understood — IT would handle the technical evaluation. When your team has needed a change to how [specific workflow] works, did that request start with you or with IT?"

It started with them. It always started with them. Now you are positioned as someone who can help them build the case that IT will eventually evaluate. The healthcare cold call playbook covers the full framework for navigating these clinical-to-IT handoffs.

Partners Who Push You to the Firm's Ops Director

Professional services firms — law, accounting, consulting — have a particular dynamic. The partners generate revenue and the ops director manages vendors. When you call a practice leader, they will almost reflexively say "you need to talk to our director of operations" or "our COO handles that."

The follow-up: "Makes sense. When the firm has brought on a new tool that changes how your team works day to day, does the ops director make that call alone or does your group weigh in?"

Partners always weigh in. The ops director does not force a new tool on a revenue-generating partner. Now you have a path to the ops director with the partner's implicit endorsement, and you know the partner will be in the room when the decision gets made. The professional services cold call playbook breaks down how to navigate partner-level conversations from the first dial.

What to Do When It Is a Genuine Wrong Number

Sometimes you truly called the wrong person. They are in a completely different department, they have no relationship to the problem, and they cannot give you a useful name. This happens.

When it does, acknowledge it fast. "I appreciate you telling me that — sounds like I missed the mark on this one. If I wanted to find whoever deals with [problem], where would you point me?" Even a genuine wrong number can sometimes give you a department name or a switchboard extension that gets you closer. Do not spend more than thirty seconds here. Thank them, hang up, and fix your list.

The key is recognizing the difference between a true wrong number and a soft brush-off. True wrong numbers sound confused. Brush-offs sound practiced. If the person immediately names a title or a department — "you want our VP of IT" or "that would be procurement" — they know exactly who handles it. That is not a wrong number. That is a referral waiting to happen.

Tracking What Happens Next

A deflection is only valuable if you follow through. Here is my workflow:

1. Log the original contact as a referral source in your CRM. Note what they told you about their role in the decision.
2. Send the internal-referral email within two hours.
3. Call the new contact the next morning. Reference the email and the referrer by name.
4. If the new contact does not respond in three business days, call the original person back. "Hey, I reached out to Karen like you suggested — haven't heard back yet. Any advice on the best way to get on her calendar?" This almost never feels intrusive because they already volunteered the name.

Most reps do step one and skip steps two through four. That is why most reps treat deflections as dead ends instead of open doors.

Where DrillCall Fits

If I were building this muscle on a team right now, I would put reps on DrillCall to practice the three-sentence response and the follow-up question before they ever use them live. Role-playing deflection handling with AI that can throw realistic curveballs — "actually, we just signed a contract with someone else" or "corporate already looked at this last year" — builds the reflex so the rep does not freeze on a real call. That is where I would start.

The Rep Who Gets the Name Wins

Every sales floor has a rep who seems to magically get warm introductions that nobody else gets. They are not magic. They are just staying on the line for forty-five more seconds when everyone else hangs up.

"I'm not the person who handles that" is not a stop sign. It is someone telling you they know who the right person is. Your job is to make it easy and worthwhile for them to share that information. Three sentences, one follow-up question, one honest email. That is the whole system.