How do you coach reps to get past gatekeepers?

The outcome you should expect

Managers who ask "how do I coach reps to get past gatekeepers?" usually want a script. The script is the least important part. What actually changes is a rep's default posture on the first eight seconds of a live call, and that posture is what a gatekeeper reads before they process a single word of your value proposition.

Here is the realistic outcome shape when this coaching lands. In the first two to three weeks, you will see almost no movement in meetings booked. That is normal and you should tell the rep it is coming, because the silent stretch is where most coaching programs die — the rep tries the new opener four times, gets screened anyway, and quietly reverts to the old habit. What moves first is the *quality of the block*. A rep running the old approach gets hung up on. A rep running the new approach gets a sentence back: "He's in meetings until Thursday," or "That's actually Dana now, not Tom." That sentence is the leading indicator. It means the gatekeeper decided the rep was a person worth talking to rather than a robocall to dispose of.

By week four to six, the second-order effect shows up: the rep starts accumulating account intelligence they never had before. Names, titles, timing windows, who actually owns the process, whether the company just switched vendors. This is the part managers consistently underestimate. Even a rep who is still getting blocked 80% of the time is now producing usable RevOps data, and that data feeds back into list hygiene, sequence timing, and territory strategy.

By the end of a 90-day cycle, the honest expectation is a meaningfully better connect-to-conversation rate, a modest lift in meetings per hundred dials, and — most durably — a rep who no longer avoids the phone. Call reluctance is the real cost of gatekeeper failure. Reps who expect to be humiliated on a call find reasons to send email instead. Fixing the gatekeeper interaction fixes dial volume as a side effect, and dial volume is usually the bigger lever.

Set expectations with the rep explicitly: you are not promising that gatekeepers will start passing them through. You are promising that the interaction stops being adversarial, that they will learn something from every call, and that the compounding of those two things produces meetings. Frame it that way and the rep survives the silent stretch.

One adjacent note worth making up front. Everything below applies almost unchanged to the *digital* gatekeepers reps now face more often than human ones: shared inboxes, "info@" aliases, LinkedIn message screening, auto-attendant phone trees, and the executive assistant who runs the calendar but never answers the line. The posture — be honest, be specific, ask for routing help rather than access — transfers cleanly. Reps who learn it on the phone apply it in email without additional coaching.

What drives that outcome

Four distinct root causes produce identical-looking symptoms, and coaching the wrong one is the single most common waste of a manager's time. Before you build any plan, listen to three or four of the rep's recorded gatekeeper calls in Gong, Chorus, or whatever your team records with. You will hear the cause in the first ten seconds — the energy, the opener, and what happens the moment there is pushback.

Will and mindset. The rep sees the gatekeeper as the enemy. They sound apologetic, rushed, or slightly deceptive. They use hedging language ("Sorry to bother you, I was just wondering if maybe..."). Tone travels perfectly over a phone line and gatekeepers screen dozens of calls a day; they are extremely good at hearing it. This is the most common root cause and the one most managers skip past because it feels soft. It isn't. A rep who believes they are doing something slightly shameful will telegraph it every time.

Skill. Right attitude, wrong words. The rep asks "Is the decision-maker available?" — a phrase that instantly identifies a cold call. Or they give a vague reason ("just following up on some information"). Or they fold the second they hear "What's this regarding?" Skill gaps are the easiest to fix and produce the fastest visible improvement, which is why it is tempting to assume every problem is a skill problem.

Knowledge. The rep doesn't know enough about the account or the value to give a credible, specific reason. They can't name the function they need, can't reference anything real about the company, and so they default to generalities. Generalities are what gatekeepers are hired to filter out.

System and targeting. The rep is calling the wrong number, the wrong title, or a company where nobody answers the phone at all. No script fixes a bad list. This is a RevOps problem — data hygiene, enrichment quality, territory design — and coaching a rep harder on a broken list is both useless and demoralizing. If two or three reps on the same list are all struggling identically, stop coaching and go audit the data.

Once you know the cause, the coaching conversation itself should follow a GROW structure — Goal, Reality, Options, Will — rather than a lecture. Ask, let the rep self-diagnose, then co-build the language together.

Goal. "What are you actually trying to get from the gatekeeper?" Most reps say "get past them." Push: "If the assistant is on your side, what do they do for you?" The rep should arrive at the answer themselves — the real goal is a warm internal referral, not a sneaky transfer.

Reality. Play the recording. Ask "What did the gatekeeper do right there, and why do you think they did it?" Let the rep notice their own tone. Self-discovery sticks; your verdict doesn't.

Options. Then hand over the language. The opener that works is honest and warm: *"Hi, I'm hoping you can help me. My name is Maria with Acme — I work with operations leaders on cutting invoice errors. I'm trying to reach whoever owns AP. Is that Tom, or am I off base?"* Three mechanics make it function: an explicit request for help, a specific plain-English reason, and a named guess the gatekeeper can correct. Never say "decision-maker." Say the function.

Will. End with a specific commitment and a check-in time. "Try harder" is not a commitment. "Use the honest-help opener on every dial Tuesday morning, we review three of those calls Wednesday at 9" is.

Then drill the pushback lines until they're automatic. The five that cover nearly every real call:

• *"What's this regarding?"* → "Totally fair to ask. We help AP teams cut invoice errors — I've got one quick question for Tom about how you handle that today. Is he the right person?"
• *"Send me an email."* → "Happy to, and I will. So I send something useful instead of generic — what's the best way Tom likes to hear about this kind of thing?" This converts a brush-off into discovery.
• *"They're not available."* → "No problem — when's a good time to catch them? Or if it's easier, I can send one sentence you can forward. What works better for you?"
• *"They're not interested."* → "Appreciate you protecting his time. Quick check so I don't keep bugging you both — is AP error rate even on his radar this year, or should I close the file?"
• *"They're in a meeting."* → "Perfect — what time does that wrap? I'll call back then."

The coaching point underneath all five: every response must be specific, respectful, and hand the gatekeeper a clear next step. Vague answers get blocked. Specific answers get routed. And notice that none of them are tricks. Nothing here depends on the gatekeeper misunderstanding who you are.

Benchmarks and realistic ranges

Be careful with benchmarks in this area — most numbers floating around gatekeeper content are vendor marketing, and connect rates vary enormously by segment, region, industry, and whether you're dialing direct lines or main switchboards. Rather than borrow someone else's figures, build your own baseline in week one and coach against that. Here is how to structure the measurement.

Set the baseline before you coach anything. Pull the rep's last two to four weeks of dial data and record four things: dials placed, human contacts reached, conversations that lasted beyond the opener, and meetings set. Those four numbers are your before-picture. Without them you cannot tell coaching from noise, and you lose the single most motivating tool you have — showing the rep their own improvement in their own numbers.

Connect-to-conversation rate is the primary metric. Of the calls that reach a live human, what fraction turn into an actual exchange rather than an immediate hang-up or hard screen? This isolates the gatekeeper skill better than anything downstream, because it strips out list quality and dial volume. It is also the metric that moves first, typically within two to four weeks of real drilling — well before meetings move.

Gatekeeper-to-target pass rate is the secondary. How often does the rep get routed toward, referred to, or given usable direction on the right contact? Count a referral as a win even when there's no transfer — "That's Dana in finance, try her Tuesday" is a successful call.

Pushback-recovery rate. Of the calls where the rep hit a screen, how often did the conversation stay alive for at least one more exchange? This is the metric that most directly reflects whether the drilled responses are actually being used. If it's flat, the rep is nodding in the 1:1 and reverting on the phone.

Meetings per hundred dials is the lagging payoff. Useful for reporting upward, useless for weekly coaching, because the sample size on a single rep's week is too small to distinguish signal from luck. Look at it monthly, not weekly.

A few practical notes on ranges. Enterprise accounts with staffed front desks and dedicated executive assistants will always show lower pass rates and higher intelligence yield than mid-market accounts where the target's direct line is discoverable. Do not compare an enterprise rep's numbers to an SMB rep's and conclude one is better coached. Segment first. Likewise, if your team dials primarily into industries with heavy call-screening norms — healthcare, legal, government, financial services — expect lower absolute numbers and set the improvement target as a relative delta against the rep's own baseline rather than a team-wide absolute.

Also watch trend data inside the call recording tool: filler-word frequency, talk-speed at the top of the call, and the length of the rep's opening turn. Those three tend to improve visibly over 30 to 60 days and give you something concrete to show a rep whose booked-meeting count hasn't budged yet. It keeps them in the program through the silent stretch.

One RevOps caveat on all of this. Dispositions have to be clean or none of the metrics mean anything. If reps are logging "no answer" for a gatekeeper screen, or "not interested" for a gatekeeper who simply refused to transfer, your denominator is garbage. Before you launch a coaching cycle, spend twenty minutes with your ops person confirming that the disposition picklist distinguishes gatekeeper-reached from target-reached from no-contact. That one field is the difference between a measurable program and a vibes-based one.

Risks, edge cases, and failure modes

Coaching tricks instead of posture. The fastest way to destroy this program is to teach deception — "say you're returning their call," "say you're a colleague," "ask for them by first name only to sound familiar." These work occasionally and cost permanently. The moment a gatekeeper catches it, the rep is burned on that account and often flagged internally. Worse, it trains the rep that the interaction is adversarial, which reinforces exactly the mindset you're trying to fix. Coach respect, not misdirection.

Rescuing the rep. A manager who grabs the phone to "show them how" gets a satisfying win and teaches nothing. The rep needs the reps. Let them struggle through the call, then debrief hard.

One-and-done coaching. A single pep talk with no commitment, no cadence, and no follow-up review changes nothing. Cadence beats intensity every time. Ten minutes weekly for twelve weeks outperforms a two-hour workshop by a wide margin.

Uniform coaching across different root causes. A nervous rep does not need a better script; a confident rep with a vague opener does not need mindset work. Running the same drill for both wastes half the team's time.

Blaming the rep for a data problem. Covered above but worth repeating as a failure mode: if targeting is wrong, coaching harder makes things worse. The rep concludes they're bad at the job when the list is bad, and call reluctance deepens.

Coaching to the deal instead of the skill. "Just get past this one gatekeeper on the Henderson account" solves today. Coaching the repeatable behavior solves the quarter.

Now the edge cases that trip up otherwise-good programs.

The genuinely hostile gatekeeper. Occasionally a rep hits someone who is rude regardless of approach. Coach the exit explicitly: thank them, hang up, log it, try a different contact or channel. Reps without a sanctioned exit will either grind pointlessly or take it personally. Consistent hostility at one account is usually a signal about timing, targeting, or a prior bad experience with your company — treat it as data, not a challenge.

Accounts with no human gatekeeper at all. Increasingly common. Auto-attendants, directory-by-extension systems, and screened mobile numbers mean the "gatekeeper" is software. The adjacent skill here is voicemail-as-bridge: leave a short, specific, honest message, then reference it on the next attempt — "I left Tom a note Tuesday about AP error rates, did that reach him?" This gives the next human you reach a reason to route you.

Regulated and high-screening industries. Healthcare, financial services, and government front desks often operate under explicit policies about vendor calls. Coach reps to ask about the policy directly rather than fight it: "Is there a process here for vendor introductions? I'd rather go through it properly." Reps who respect the process sometimes get handed the actual path in, which is more valuable than a transfer.

Regional and cultural variation. Directness that reads as confident in one market reads as rude in another. If your team dials internationally, the honest-help opener still works but the pacing and formality should shift. Have reps who cover a region contribute the local variant rather than importing one script globally.

The rep who is too good at this. Rare but real: a rep builds such strong gatekeeper rapport that they stop pushing toward the target and settle for pleasant conversations that go nowhere. Watch for high connect-to-conversation with flat pass rate. The coaching note is to always close with a routing ask.

Compliance and recording. Before building any of this on call recordings, confirm your recording consent posture is correct for the jurisdictions you dial into. This is a RevOps and legal question, not a sales one, and it is much cheaper to check first.

A practical rollout plan

One conversation changes nothing. Build a 30/60/90 loop and run it on a fixed weekly rhythm.

Days 1–30 — language and mindset. Co-build the opener and the five pushback responses with the rep rather than handing them a document; language the rep helped write gets used. Institute a 90-second warm-up before every dialing block — the rep says the opener out loud twice before the first call, because cold openers fail and warmed ones don't. Manager reviews three recorded calls per rep per week and gives exactly one specific note. One. A list of six notes is a list of zero notes.

Days 31–60 — reps and reflexes. The rep should now handle all five pushback lines without reading anything. Add an objection-ladder role-play where you play the gatekeeper and escalate through three registers — friendly, guarded, then dismissive — and the rep must stay warm and specific through all three. Score it on a simple four-item scorecard: tone, specificity, named guess, recovery. Add a "be the gatekeeper" reversal where the rep plays the assistant for five minutes; feeling how a pushy opener lands teaches more in five minutes than an hour of feedback. Start a weekly twenty-minute call-review club where each rep brings one win clip and one flop clip and the team diagnoses together — peer coaching scales faster than you alone.

Days 61–90 — independence and scale. The rep self-reviews their own calls and brings their own note to the 1:1. You shift from teaching to maintaining. Add the intelligence debrief: five minutes in each 1:1 where the rep shares one thing they learned from a gatekeeper who did *not* pass them through. This reframes a block as a data point, and across a quarter it produces a meaningful pile of account intel per rep that feeds back to RevOps for list and sequence refinement.

For enterprise accounts where the same gatekeeper answers every time, layer in a multi-touch pattern rather than treating each call as standalone. First call: reconnaissance only — introduce yourself by name and company, ask one low-pressure routing question, thank them, hang up. No pitch, no attempt to get through. Second call a few days later: reference the first conversation by name and add one specific reason. Third call: frame the gatekeeper as the expert on the process — "I've left a couple of messages and want to respect your time. What's the best way to get Tom a two-minute update on this?" Familiarity does real work here, and reps consistently report the interaction becomes far less stressful once the gatekeeper recognizes them.

A note on where this sits in the wider system. Gatekeeper coaching is one node in a larger outbound motion, and it fails quietly when the surrounding nodes are broken. If the sequence timing means the rep calls the same account four times in three days, no opener saves them. If enrichment is stale and half the named guesses are people who left the company, the "is that Tom, or am I off base?" move backfires. If the value proposition is genuinely generic, the rep has nothing specific to say and the gatekeeper is right to screen them. Before or alongside the coaching cycle, do a quick pass with RevOps on list freshness, dial cadence, and whether the rep can articulate one concrete outcome your product produces. Those three fixes often deliver more lift than the coaching itself — and they make the coaching stick when it lands.

Related questions

How is coaching gatekeeper skills different for SDRs versus AEs?

SDRs dial far more volume, so drill reflexes and run tight weekly cadence. AEs hit gatekeepers less often but on higher-stakes accounts, so coach preparation and multi-touch patience instead of speed. AEs also have more legitimate reasons to call, which makes the honest opener easier.

Should reps ever ask a gatekeeper for the target's direct line?

Yes, but late in the conversation and framed as convenience for the gatekeeper: "So I stop bothering you — is there a better line or time?" Asking as the opener reads as bypassing them. Asking after a helpful exchange often works.

Does this coaching transfer to email and LinkedIn?

Directly. Shared inboxes, executive assistants managing calendars, and screened LinkedIn requests are the same interaction in another channel. The transferable move is asking for routing help rather than access, plus one specific plain-English reason.

How do I coach a rep who avoids the phone entirely?

That is call reluctance, not a gatekeeper problem. Shrink the ask — five dials with you sitting there, debriefed immediately. Volume returns once the interaction stops feeling humiliating, and gatekeeper skill is usually the fastest route there.

What if my whole team struggles with the same accounts?

Stop coaching and audit the data. Uniform failure across reps points at the list, the titles, or the phone numbers. That is a RevOps fix — enrichment quality, territory design, disposition hygiene — not a skills fix.

FAQ

What's the single most important mindset shift for reps dealing with gatekeepers?

Seeing the gatekeeper as an ally rather than an obstacle. When a rep treats the assistant as a partner who holds useful information — who actually owns the process, when the target is reachable, what they care about this quarter — they stop sounding nervous or evasive. Gatekeepers screen dozens of calls a day and are exceptionally good at hearing posture. This shift alone typically moves outcomes more than any script change, because the script only works when the tone underneath it is genuine.

How do I tell whether the problem is mindset, skill, or targeting?

Listen to recordings, don't guess. Mindset shows up as apologetic tone, hedging language, or the rep avoiding phone blocks entirely. Skill shows up as a confident rep with a vague opener who folds on the first screen. Targeting shows up as consistent "wrong department" responses, disconnected numbers, or the same failure pattern across multiple reps on the same list. That last one is the tell — if three reps fail identically, it's the data, not the people.

What does a respectful opener actually sound like?

Something close to: "Hi, I'm hoping you can help me. This is Maria with Acme — I work with operations leaders on cutting invoice errors. I'm trying to reach whoever owns AP. Is that Tom, or am I off base?" It asks for help, gives a specific plain-English reason, and offers a named guess the gatekeeper can correct. Avoid "decision-maker," avoid "just following up," and avoid anything that implies a prior relationship you don't have.

How often should we run gatekeeper role-play?

Weekly, in short sessions. Five to ten minutes per rep beats a quarterly workshop by a wide margin, because the goal is reflex rather than recall. Vary the scenario — cold first call, follow-up call, friendly gatekeeper, dismissive one — so the rep isn't rehearsing one memorized path. Drill until the language sounds like the rep talking rather than the rep reciting; a script that sounds like a script defeats the entire purpose.

How long before I should expect to see results?

Connect-to-conversation rate typically moves first, within roughly two to four weeks of consistent drilling. Meetings booked lag well behind that, often not showing clear movement until the second month, because the sample size on any single rep's week is too small to read. Tell the rep this in advance. The most common failure is a rep abandoning the new approach during the silent stretch before the downstream numbers catch up.

What should a rep do with a gatekeeper who won't help at all?

Thank them, end the call politely, log what happened, and try a different contact or channel. Grinding against hostility rarely converts and can get the company flagged internally. Consistent hostility at one account usually signals bad timing, wrong targeting, or a prior negative experience with your company — treat it as information for RevOps rather than a personal challenge, and route the effort somewhere it can compound.

Sources

• Gong Labs — Cold Call Opening Lines That Work
• RAIN Group — Cold Calling Tips and Techniques
• Sandler — The Gatekeeper Is Your Friend
• MindTools — The GROW Model of Coaching and Mentoring
• Harvard Business Review — How to Get the Most Out of Coaching
• Richardson Sales Performance — Sales Coaching Best Practices
• HubSpot — Cold Calling Tips
• Salesforce — Sales Coaching Guide

Related on PULSE

• [How do you coach reps across multiple time zones?](/knowledge/cg0186)
• [How do you coach reps you never see in person?](/knowledge/cg0182)
• [How do you coach reps to handle silence and pauses on calls?](/knowledge/cg0180)
• [How do you coach reps to sell to executives?](/knowledge/cg0178)
• [How do you coach reps to improve their lead-to-opportunity rate?](/knowledge/cg0170)
• [How do you coach reps to increase average deal size?](/knowledge/cg0167)