Gatekeepers Aren't the Enemy: How to Get Routed Instead of Blocked

The war metaphor is why you keep losing

Somewhere in the last thirty years of sales training, someone decided the person who answers the phone is an obstacle. A wall. A dragon at the gate. And so we got a whole genre of advice about "getting past" them — tricks, misdirection, the confident-sounding lie, the call at 7:40am to beat them to the desk.

I have run four businesses and sold inside AWS and Dell, and I have never once seen that framing produce a durable pipeline. What it produces is a rep who sounds like a nervous salesperson pretending not to be a salesperson, which is the single most detectable thing on a phone call.

Here is the reframe that actually changes numbers. The person answering the phone is not a wall. They are a router. Their entire job is to move inbound traffic to the correct destination as quickly as possible. They do not want to block you. Blocking you takes effort. Blocking you means a conversation. Routing you takes four seconds and then they get back to what they were doing.

Routers respond to two inputs: clarity and confidence. They punish two things: vagueness and performance. Every gatekeeper script in this post is built on that one idea.

What the person on the other end is actually doing

Picture the desk. At a mid-sized construction firm it is an office manager who also does payroll, chases up subcontractor insurance certificates, and orders the coffee. At a council it is a switchboard operator with a directory in front of them and a policy about not giving out direct lines. At a law firm it is often a legal secretary or a floor receptionist who protects a partner's calendar because that calendar is billable in six-minute increments.

None of these people woke up wanting to fight you. What they want is to not make a mistake. The mistake they fear is putting a time-waster through to someone senior, because that costs them personally — a sigh, an email, a comment in a one-to-one. Their whole screening behaviour is risk management, not hostility.

So when you call, you are not trying to defeat them. You are trying to make the routing decision easy and low-risk. That means being specific enough that they can categorise you, and calm enough that you do not trigger the salesperson alarm.

Almost every rep I have listened to gets this backwards. They go vague to avoid being screened — "just a quick question for him" — which reads as evasive, which raises risk, which gets them blocked. Vagueness is the thing that gets you blocked. Not being a salesperson.

Tone rules, before you touch the script

You can have perfect words and still get bounced, because the first thing a receptionist processes is not content. It is delivery. Three rules, and they cost you nothing.

Slower. Speed reads as nerves, and nerves read as "this person is not supposed to be calling here." When I am coaching someone on this, I tell them to say their own name at half the pace they think is natural. It will feel absurd in your mouth and sound completely normal on the line. Everyone rushes their opener because they want to get to the ask.

Lower. Not fake-deep. Just drop out of the bright, rising, hopeful register that people use when they are asking for a favour. Rising intonation at the end of a sentence turns a statement into a request for permission. "I'm calling for Sarah Whitfield?" invites a no. "I'm calling for Sarah Whitfield." invites a transfer.

Shorter. The number one predictor of a blocked call is that the rep kept talking. You give one clean sentence and then you stop. Silence after a clear statement is the most powerful tool you have on a gatekeeper call, because the natural human response to a confident, complete statement is to act on it. If you fill that silence with a second sentence, you have converted a routing decision into a screening conversation, and you will lose the screening conversation.

Write "slower, lower, shorter" on a sticky note and put it on your monitor. I still do it when I go back on the phones after a stretch away.

Moment one: "What's this regarding?"

This is the fork in the road. Everything after this is downstream of how you handle four words.

Most reps do one of two things, and both are wrong. They either go completely opaque — "it's a private matter," "he'll know what it's about" — or they dump the pitch — "we help construction firms reduce equipment downtime through predictive maintenance analytics and I wanted to see if..." The first sounds like a scam. The second gets you a polite "I'll take a message."

What works is a specific, plain-language, non-salesy statement of subject matter. Not a pitch. A subject line.

Gatekeeper: What's this regarding?

You: Sure — it's about how they're handling [specific operational thing] across the [region/branches/sites]. I've not spoken to her before, so if she's the wrong person she'll tell me in about ten seconds.

Three things are happening there. You answered the question directly, which drops the risk score. You used operational language rather than product language, which makes you sound like a peer or a vendor they already work with rather than a cold caller. And you pre-admitted that you are new, which is disarming — you have said the thing they were about to catch you on, so there is nothing to catch.

That last clause matters more than people expect. "I've not spoken to her before" is honest, and honesty is unusual enough on these calls that it registers. You are not claiming a relationship. You are also not apologising. You are just stating a fact and moving on.

Some variations that hold up:

It's about their subcontractor onboarding process — specifically the insurance certificate side. Is she the right person for that, or is it someone else?

It's regarding scheduling across the two sites. I think she owns that, but tell me if I've got the wrong name.

Notice that both of those end with a question back to the gatekeeper that treats them as knowledgeable. That is not a trick. It is accurate. They usually do know who owns what, and asking them is the fastest route to the right human. I have been redirected to a better contact than the one I called for more times than I can count, purely because I asked the receptionist who owned the problem instead of insisting on my target.

And never, ever say "I'll only take a minute of her time." It signals that you know you are an imposition, and it invites the counter-offer of no minutes at all.

Moment two: "Is she expecting your call?"

This is the integrity test, and it is where a lot of reps torch the call by lying. "Yes" is a lie that survives about eleven seconds — until the person picks up and says who? — and now you have burned the account, because the receptionist will remember, and receptionists talk.

Answer it straight, then immediately supply the reason the call is legitimate.

Gatekeeper: Is he expecting your call?

You: No, he isn't — this is the first time I've reached out. I'm calling because [specific, relevant reason tied to their business]. If he's not the right person for that, I'd rather find out now than keep bothering you.

The "no" is doing the heavy lifting. It is unexpected. Most gatekeepers ask that question braced for a slippery answer, and a flat, unbothered "no, he isn't" changes the temperature of the call. You have just demonstrated that you are not going to manage them.

The follow-on clause has to be genuinely specific, though, or the honesty is wasted. "I'm calling because I'd like to introduce our platform" is not a reason, it is a category. "I'm calling because they've just picked up the two schools contract and I've worked with three firms who hit the same staffing crunch at that stage" is a reason. It refers to something true about their organisation. If you cannot say something true about their organisation, you are not ready to make the call, and no amount of gatekeeper technique will fix that.

A second version, for when you want to keep it very short:

No — cold call, honestly. Worth two minutes of his time or it isn't, and he can decide that faster than either of us can.

That one works better than it should. Naming it as a cold call removes the entire pretence and a certain type of no-nonsense office manager will put you through just because you did not waste their time.

Moment three: "Leave your details and I'll pass them on"

This is the polite dead end. It is not a rejection, it is a filing action. Your details go on a pad and the pad goes in a drawer. If you accept it and hang up, you have made a call that produced nothing.

Do not fight it. Accept it, then attach a small, easy request to the acceptance.

You: That's great, thank you — I'll give you my details in a second. Before I do, two quick things so I'm not wasting your time. First, is she actually the person who owns [the thing] these days, or has that moved? And second, when is she normally at her desk? I'd rather call back at a sensible time than keep landing in your lap.

You have complied, so there is no friction. And you have asked two questions that are easy to answer and cost the gatekeeper nothing — one that qualifies your target, one that gives you a callback window. A receptionist who tells you "she's usually in before eight-thirty" has just handed you the account. That is not a trick you played on them. That is a person helping you because you were pleasant and did not try to bulldoze them.

The follow-up call is where this pays off. When you ring back at 8:15 and get the same person, you open with recognition rather than a fresh pitch:

Morning — it's Tim again, we spoke on Tuesday. You mentioned she's usually in early, so I thought I'd take your advice.

You are now a known quantity. Known quantities get routed.

On using a peer's name

There is a legitimate version of this and an illegitimate one. The illegitimate one is implying a relationship you do not have — "Dave suggested I call" when Dave did no such thing. Do not do it. It unravels in the first thirty seconds of the actual conversation and it makes you the kind of person who does that.

The legitimate version is using a name as context, clearly labelled as context.

I spoke with Mark in operations last week about the scheduling side, and he pointed me toward her for anything to do with the commercial contracts.

Only say that if it happened. If it did, it is the single strongest gatekeeper unlock available, because now the routing decision is not yours, it is Mark's, and the receptionist is not on the hook. This is a strong argument for working accounts bottom-up: a five-minute conversation with a site supervisor gives you a name you can use honestly for the next three calls.

When the gatekeeper is not a gatekeeper at all

Some of the people you have been trying to "get past" are the people you should be selling to.

At a firm of forty people, the office manager frequently owns the software budget, the vendor relationships, and the operational headache you are calling about. The executive assistant to a partner often decides which vendor meetings make the calendar and which do not, and their opinion carries weight in the room afterwards. In a council, the officer who answers the switchboard for a small department may be the person who actually assembles the procurement paperwork.

So listen for the tell. If they ask a substantive question back — "what does it integrate with?", "is this the thing that does the certificates?", "we looked at something like that last year" — stop routing and start talking. That is not a screen. That is an evaluation.

Good question, and honestly you sound like you know this area better than most people I speak to. Can I ask what happened when you looked at it last year?

Give them the same respect and the same discovery you would give the VP. Worst case, you learn the account's history for free. Best case, you have an internal advocate who will walk your name down the corridor in a way no cold call ever could.

The verticals that screen hardest

Screening intensity is not evenly distributed. Three sectors will test your scripting far harder than the rest, and each for a different reason.

Government and public sector. The screen is procedural rather than personal. Switchboards work from a directory and a policy, and the policy often says do not transfer external commercial calls to named officers. Fighting the policy is pointless because the person on the phone did not write it. What works is asking the routing question the system is built to answer: which team owns this, and is there a published contact for it. Officers are usually reachable if you know the team name, which is why the framing in our government and public sector cold call script leans so heavily on knowing the department structure before you dial rather than on charming the switchboard.

Legal. The screen is economic. Every minute a managing partner or litigation chair spends on your call is a minute not billed, and the secretary's job is to protect that. Vague subject lines die instantly here. You need to sound like you understand the practice area, and you need to be asking for a scheduled slot rather than a conversation right now. Our legal cold call script for reaching a managing partner or litigation chair is built around booking twenty minutes precisely because "can I have a few minutes now" is the wrong ask in a firm that measures time in six-minute units.

Healthcare. The screen is about clinical priority, and it should be. Nobody at a hospital is putting a vendor through to a CMIO who is mid-round. The right move is to accept that clinical leaders have narrow, structured availability and to work with the person who manages that calendar rather than around them. The approach in the healthcare cold call script for CMIOs and VPs of clinical operations assumes you will go through an assistant and treats that as the intended path, not the obstacle.

Construction and trades screen differently again — the office manager is usually reachable but your target is on a site with no signal, so the real question you should be asking is when they come off site, which is the whole logic behind our construction and trades cold call script for VPs of operations and general superintendents.

What I would do this week

Pull ten of your own recordings where you got blocked. Listen only to the first fifteen seconds. I would bet you talked fast, your voice went up at the end of your opening line, and when they asked what it was regarding you produced something either evasive or thirty words too long. That is the whole diagnosis for most reps, and it is fixable in an afternoon.

Then rewrite your three lines — the subject-matter answer, the honest "no, he isn't expecting me," and the accept-and-ask response to the message offer — and say each one out loud twenty times until it is boring. Boring is the goal. Boring is what routing sounds like.

If you want reps against a receptionist who actually pushes back, that is exactly what we built DrillCall for — you run the gatekeeper moment over and over until the honest "no" comes out flat and unhurried instead of apologetic. It is the cheapest place to be bad at this. Better there than on the one call into the account you have been chasing all quarter.

Stop trying to get past them. Start giving them a reason to route you.