Cold Call Teardown: The Rep Booked a Meeting — With the Wrong Person

A rep I was listening back with had a great week on paper. Five meetings booked from cold calls into hospital systems. By the end of the following month, four of them had gone nowhere and one had turned into a "let me loop in my director" email that never got answered.

The call below is a composite. I have heard some version of it many, many times, in healthcare and everywhere else. Three minutes, polite on both sides, ends in a calendar invite, and dead on arrival. What makes it worth tearing apart is that the rep does almost everything right. The opener is fine. The tone is fine. The value prop is tight. The call still fails, and it fails at a specific, findable moment in the first sixty seconds.

The call

0:00 — Gatekeeper answers the main line for a mid-size regional hospital system. Rep asks for whoever owns clinical documentation workflows. Gets transferred.

0:22 — "This is Dan."

Rep: "Dan, hi. Timothy from [vendor]. I'll be honest with you, this is a cold call — do you want to hang up or do you want twenty seconds?"

Dan: (laughs) "Go ahead, twenty seconds."

Rep: "We work with hospital systems on clinical documentation. Specifically the gap between what a nurse charts at the bedside and what actually makes it into the record before shift change. Reason for the call — I don't know if that's a problem at your shop or not. Are you the right person for that?"

Dan: "Yeah, sure, I handle that."

Rep: "Great. So what we do is—"

0:51 through 2:20 — Ninety seconds of product. Integrations. A named reference account. How the pilot works. Dan asks two good questions. Dan says "that's interesting" twice.

2:31 — Rep asks for twenty minutes next week. Dan says Thursday works. Rep sends the invite from the car.

2:58 — Call ends. Rep logs a meeting.

Dan is an IT project manager. He is running an integration backlog for a team that inherited clinical systems after a merger. He is genuinely helpful, genuinely interested, and cannot spend a dollar, cannot convene the clinical stakeholders, and does not sit in any meeting where this decision gets made. He will show up Thursday. He will take notes. He will say he'll share it internally. Nothing will happen.

The exact moment it went wrong

Minute one. Not the ninety-second product dump — that is a symptom. The failure is here:

Rep: "Are you the right person for that?"

Dan: "Yeah, sure, I handle that."

Rep: "Great. So what we do is—"

The rep asked a qualifying question and then accepted a one-clause answer as a verified fact. That's it. That's the whole failure. Everything after 0:51 is the rep selling with total conviction to a person whose authority was never actually established.

And here is the part that stings: the rep asked the right question. "Are you the right person for that" is a fine question. The problem is that it is a closed question with a socially expensive "no." You have just called someone at work and asked whether their job includes an important thing. Almost nobody says "no, that's above me." Dan wasn't lying. In Dan's head, he does handle it. He handles the integration tickets. He handles the vendor evaluations that land in his queue. He handles the part he sees.

The rep heard "I own this decision." Dan said "I touch this workflow." Those are not the same sentence, and the entire deal turns on the difference.

Why "I handle that" is the most dangerous answer on a cold call

A hard no ends the call cleanly and you dial the next number. "I handle that" does something worse — it rewards you. It feels like progress. It gives you permission to do the fun part of the job, which is talk about the product. You get a dopamine hit and a calendar invite and a line in the CRM, and none of it is real.

Every rep I have watched fall into this has fallen in the same way. They were nervous about the authority question, they asked it once, they got an answer that let them stop asking, and they sprinted through the door before anyone could close it.

The fix is not to be more aggressive. Being more aggressive gets you "who do you report to," which is insulting, and it gets you nothing, because the person you just insulted will now route you to a voicemail box on purpose. The fix is to ask a question where the honest answer costs Dan nothing.

The two sentences

Here is what I would have said at 0:47, immediately after "yeah, sure, I handle that."

"Perfect — and just so I don't waste your time on the wrong half of this: when something like this actually gets bought, who else ends up in the room with you? Usually there's a clinical side and a budget side and I never know which one I've reached first."

Two sentences. Let me break down why each piece does work.

"Perfect" — you accepted his answer. You did not challenge him. He said he handles it, and you agreed that he handles it. Nobody is defensive now.

"So I don't waste your time on the wrong half of this" — the reason for the question is framed as a service to him. You are protecting his calendar, not auditing his org chart.

"When something like this actually gets bought" — hypothetical and future tense. He is not admitting he lacks authority. He is describing a process. Describing a process is easy and low-stakes. People love explaining how their organisation works.

"Who else ends up in the room with you" — with you. He stays in the room in this sentence. You have not removed him. You are asking who joins him, which presumes he belongs there. Compare that to "who makes the final decision," which is a question about whether he matters.

"There's a clinical side and a budget side and I never know which one I've reached first" — this is the load-bearing sentence and most reps skip it. You have given him a menu. Now he doesn't have to invent an answer or guess what you want; he just has to point. And critically, you have signalled that reaching the "wrong" one is normal and expected, so telling you the truth is not an embarrassing confession.

What Dan says next, nine times in ten, is something like: "Yeah, so I'd handle the technical eval, but Sharon in nursing informatics would have to sign off on anything that touches charting, and honestly if it's got a real price tag it goes to the CNO."

You just got the map. In twelve seconds. Without insulting anybody.

The follow-up that most reps forget

There is a third sentence, and it is the one that separates reps who know the buying committee from reps who can actually reach it:

"Got it — has Sharon flagged this as a problem, or is it more that you're seeing it from the systems side?"

This tells you whether you have a champion with a mandate or a helpful person with a hunch. If Sharon has never mentioned it, Dan is not carrying a signal from the clinical side. He is interested personally. That is a very different call, and it changes what you ask for at the end.

Do not throw Dan away

The wrong lesson from this teardown is "disqualify low-authority contacts faster." That is how reps end up burning the only warm body inside an account they'll never get back into.

Dan is valuable. He is just not a meeting. He is an introduction.

The move is to change the ask. Instead of "can I get twenty minutes with you Thursday," you ask for something Dan can actually deliver:

"Dan, here's what I'd suggest. A demo to you alone is honestly not that useful — you'd just have to repeat it all to Sharon anyway and I'd have made your week worse. What if I put together a short summary of what we do and the two or three questions a nursing informatics lead usually asks, you forward it to Sharon if you think it's worth her time, and if she bites, we do one session with the three of us? That way you're not carrying my pitch for me."

Read what that does. You have declined a meeting he offered, which immediately makes you more credible than every other vendor who ever called him. You have told him the meeting would waste his time, not that he is unimportant. You have given him a specific, small, forwardable action. And you have pre-written the internal sell so he doesn't have to.

Then you send the email that day, short, written for Sharon, not for Dan. Subject line she'd open. Two or three lines about the charting-to-record gap in her language. One line at the bottom: "Dan — feel free to forward as-is if useful."

A rep who does this consistently ends up with a set of internal advocates across an account, which is worth more than a stack of no-show meetings with project managers. This is the whole logic behind how we structure the healthcare cold call script for getting a CMIO or VP of Clinical Operations on the phone — you are not trying to bypass the Dans of the world, you are trying to arrive at the clinical exec already vouched for.

This is not a healthcare problem

Hospitals make it vivid because the clinical/IT/finance split is so stark. But the same call happens everywhere with different job titles.

In public sector, you get routed to a delivery officer who is deep in the operational detail, is delightful to talk to, and has no procurement authority whatsoever — and the person who does has a completely different set of concerns, which is why the government and public sector script opens the way it does. In financial services, you reach an operations manager who "handles vendor relationships" and turns out to mean he handles the renewal paperwork, while the person you need is a COO thinking about advisor capacity — the framing in the wealth management COO script exists precisely because the first person who says yes to you is rarely the person who can say yes to the deal.

The pattern is universal: the more accessible someone is, the less likely they are to be your buyer. The people with authority are hard to reach because they have authority. If a stranger gets through to someone in ninety seconds and that person has forty minutes to chat, update your priors.

Rewriting the call

Here is the same three minutes, done right. Same opener, because the opener was never the problem.

Rep: "Dan, hi. Timothy from [vendor]. I'll be honest with you, this is a cold call — do you want to hang up or do you want twenty seconds?"

Dan: "Go ahead."

Rep: "We work with hospital systems on the gap between what a nurse charts at the bedside and what actually lands in the record before shift change. Is that a live thing at your shop or am I miles off?"

Dan: "No, that's a thing. I handle that, actually."

Rep: "Perfect — and just so I don't waste your time on the wrong half of it: when something like this actually gets bought, who ends up in the room with you? There's usually a clinical side and a budget side and I never know which one I've reached first."

Dan: "Right. I'd do the technical eval. Sharon in nursing informatics owns anything touching charting. Big spend goes to the CNO."

Rep: "Got it. Has Sharon flagged this, or is it more that you see it from the systems side?"

Dan: "Bit of both. She's complained about it. Nothing formal."

Rep: "That's useful. Then let me not book a demo with you, because you'd just have to repeat the whole thing to Sharon and I'd have made your week worse. Let me send you a short note written for her — what we do, and the two questions a nursing informatics lead always asks. Forward it if you think it's worth her time. If she's in, I'd do one session with the three of us. Fair?"

Dan: "Yeah, send it over."

Two minutes. No meeting booked. Dramatically better call.

That is a hard thing for a rep on a meetings quota to internalise, and I am not going to pretend otherwise. Your dashboard will not reward you for it this week. It will reward you next quarter, when your pipeline is not full of ghosts.

The rubric: run this on your own recordings

Pull five cold calls from the last two weeks where you booked something. Not your best five. The five most recent. Score each one out of six. One point per item, no partial credit.

1. Did you ask an authority question at all? Not "is this a problem for you" — an actual question about who owns the decision. If it never came up, zero, and stop there.

2. Was the authority question open, not closed? "Are you the right person" is closed and gets you a reflexive yes. "Who ends up in the room" is open and gets you a map. If the honest answer to your question would have required the prospect to admit something unflattering about their own standing, you asked it wrong.

3. Did you get a name? Not a function. A name. "Sharon in nursing informatics" is a point. "Clinical would have to look at it" is not. If you got a function, did you ask "who's that, out of interest?"

4. Did you test for signal? Do you know whether the real buyer has already expressed the pain, or whether your contact is the only one who cares? This is the single best predictor of whether the internal forward goes anywhere.

5. Did the ask match the authority? If your contact can't buy, you should not have asked for a demo. You should have asked for a forward, an introduction, or a name. Booking a demo with someone who can't buy is not a win you get to count.

6. Did you leave the contact intact? Listen for defensiveness. Did the tone change after your authority question? Did they get shorter with you? If you cooled the call down by asking, your phrasing was the problem, not the question.

Most reps I have run this with score two or three on their booked calls, which is the uncomfortable part. The calls that felt best are often the ones that score worst, because a low-authority contact with time on their hands gives you the friendliest conversation of your day.

What you do with the score: if you're consistently losing point two, rewrite one sentence and say it out loud fifty times before your next block until it comes out relaxed. If you're losing point five, that is a discipline problem, not a skills problem — you know the contact can't buy and you're booking the meeting anyway because the number is due Friday.

If you want to drill it rather than just diagnose it, the thing I'd do next is run the same scenario over and over against a prospect who sounds like an owner and isn't — that is exactly the kind of rep we build in DrillCall, because the sentence only becomes automatic when you've hit the wall with it thirty times in a row and found the phrasing that doesn't make a helpful project manager go cold on you.

One last thing. The rep in this teardown was not bad. He was good enough to get through, good enough to earn twenty seconds, good enough to hold a conversation with a stranger about their job. Those are the hard parts. Adding two sentences to the front of the pitch is the easy part. Go add them.