Top 10 Ready-to-Use Sessions for Handling Gatekeepers in 2027

Permission plays versus context plays: the two families that matter

Every gatekeeper script in circulation is a variation on one of two moves, and knowing which family you're in tells you what the call needs before you dial.

Permission plays start from zero. You have no prior thread, no mutual contact, no partnership — just a phone number and a name you scraped from LinkedIn. These scripts work by changing the social frame of the call rather than by supplying information. The canonical example is answering "Who's calling?" with a question of your own: "Happy to tell you — could I get the name of the person I'm speaking with first?" You're not evading. You're converting a screening interaction into a conversation between two named people, which is a fundamentally different transaction. Reciprocity does the work. So does the plain fact that most reps arrive with a rehearsed pitch, so an ordinary human question breaks the pattern the gatekeeper has been trained to shut down.

Two more sit in this family. The "can you help me?" framing asks directly for guidance — "I'm hoping you can help me; I need to reach whoever owns renewals over there, and I'm not sure that's the right title. Can you point me in the right direction?" It works because gatekeepers are trained to block sales pitches, not to refuse a request for directions. And the reverse-psychology open — "I'm actually not asking to be transferred; I wanted to ask you something first. In your role, do you handle vendor approvals, or does that go up a level?" — treats the gatekeeper as a source of intelligence rather than an obstacle. With senior executive assistants, this is often the only one of the three that lands, because EAs at that tier have heard the name-swap move a thousand times.

Context plays start from something real. The email follow-up ("I sent a note to Dana on Tuesday about the Q4 renewal cycle — could you put me through?"), the mutual-contact referral, the partner reference ("I'm calling from our side of the integration work we're doing with your ops team"), and the problem-first open ("I'm calling because your competitor just changed their pricing model and I want to ask how you're handling it") all supply the gatekeeper with a reason that isn't "I want to sell something." The gatekeeper's actual job is triage, not obstruction — they need a category for you. Context plays hand them one.

The trade-off is exposure. Permission plays cost nothing and can be used on every call in your list. Context plays convert far better but each one carries a verification risk: if you claim an email you never sent, or a referral you don't have, the gatekeeper checks, and you're not just blocked at that account — you're flagged. Executive assistants talk to each other, and inside a single company you may only get one shot. Never manufacture a context play. If you don't have the context, run a permission play and go build the context afterward.

A third bucket exists that isn't really a play at all: the soft close. "I understand you're busy — I'll send a short email instead. What's the best address?" This is what you run when the first two families have failed. It has a modest but real conversion habit of its own, because a gatekeeper who has just successfully deflected you sometimes relaxes and offers the transfer anyway. More importantly it converts a dead call into a working email address, which is a genuine asset.

How to decide which session to run

Routing beats memorizing. Reps who try to hold ten scripts in their head freeze; reps who hold one decision rule and three scripts perform.

The rule has three inputs. First: do you have real context? Sent email in the last 48 hours, a named mutual contact who has agreed to be named, an active partnership, or documented public evidence of a specific problem at that account. If yes, run the matching context play — they outperform permission plays by a wide margin whenever the context is genuine. Second: what tier of gatekeeper answered? A front-desk receptionist at a 40-person company is routing calls, not defending a calendar. A dedicated executive assistant at a 5,000-person company is a trained filter who has personally chosen to protect that calendar and often has real authority over it. Receptionists respond to the name-exchange and help framings. EAs respond to being treated as the decision-maker they partially are. Third: what does their tone tell you? Friendly and unhurried → the help framing. Clipped and rushed → skip straight to the soft close and get the email; you will not win a two-minute conversation with someone who is currently on hold with someone else.

One habit separates good routing from guessing: log the branch you took and why, not just the outcome. A disposition field with six values — which play, and did it transfer — turns a quarter of calls into a routing table specific to your market. Generic benchmarks are a starting hypothesis; your own numbers replace them within a few hundred dials.

What the numbers actually look like, and how to read them

The published figures floating around gatekeeper training are mostly vendor blog content, and you should treat them as directional rather than as targets. The honest version of the numbers is structural, not statistical.

Volume math first. A typical outbound SDR making 60 to 80 dials a day will reach a live human on roughly a quarter to a third of them; the rest are voicemail, dead numbers, or IVR. Of those live connects, at mid-market and up, a meaningful share are gatekeepers rather than the target. So a rep is having maybe 8 to 15 real gatekeeper conversations a day. That's the denominator that matters. If your transfer rate moves from 15% to 25% on 12 conversations a day, you gained about one extra decision-maker conversation per day — roughly 20 a month, which at typical conversion is a material pipeline change from a scripting fix alone.

Relative performance is more reliable than absolute. Across almost every team that measures this, the ordering holds: genuine referrals convert best by a wide margin, partner references and email follow-ups sit in the middle, cold permission plays sit below them, and pure pitch-first openers sit at the bottom. What varies enormously by market is the absolute level. Selling into hospital systems or government, a 10% transfer rate is strong. Selling into 50-person SaaS companies where the "gatekeeper" is a shared admin, 40% is achievable. Do not import someone else's benchmark and then conclude your team is broken.

Set the retirement threshold, not the success threshold. The useful metric discipline is a floor: any play that runs below roughly 15% transfer rate over 50-plus attempts gets pulled from the deck and retrained or dropped. Fifty is not arbitrary — below about 30 attempts the confidence interval on a rate that low is wide enough that you'll retire good plays and keep bad ones. Give each play a real sample before judging it.

Watch the second-order numbers too. Transfer rate is the obvious one, but three others tell you more. Email-capture rate on failed calls: a soft close that reliably produces a verified address is worth nearly as much as a transfer, because it seeds a legitimate email follow-up play for next week. Callback rate from gatekeeper-taken messages: some markets have gatekeepers who genuinely relay, and if yours does, the problem-first open is worth far more than its transfer rate suggests. Repeat-account penalty: track whether accounts you've called before transfer at a *lower* rate than fresh ones. If they do, your reps are burning goodwill with pressure tactics, and no script change fixes that.

Cost side is nearly zero, which is the point. These are scripts. The dial infrastructure, sequencer, and CRM you already pay for. The only real investment is coaching time — realistically 45 to 60 minutes of role-play per rep to get one play to sound natural, and a rep should own two or three plays cold, not ten. Ten half-learned scripts perform worse than three fluent ones, every time.

Adjacent channels move the numbers too. Gatekeeping is not phone-only. Shared inboxes, LinkedIn connection screening, procurement portals, and increasingly voice-AI receptionists are all the same function in different clothing. Teams that stop treating this as a phone problem tend to find the cheapest wins are elsewhere — a well-targeted LinkedIn message routed to the right person can sidestep the phone entirely, and the same routing logic applies.

Building the session: sequencing, drills, and rollout

A "ready-to-use session" is a training artifact, not a paragraph. Here is what to actually build.

Structure the 60-minute session. Ten minutes of framing: what a gatekeeper's actual job is, and why treating them as an adversary loses. Fifteen minutes on the two families and the routing rule, with the decision flow on screen. Twenty-five minutes of live role-play in pairs, with a third person scoring. Ten minutes to assign each rep their two primary plays and set the measurement.

Run the role-play with real resistance. The failure mode of gatekeeper training is a compliant partner who transfers on the first ask. Give the person playing the gatekeeper a card with an assigned personality — rushed, suspicious, friendly-but-firm, or "has explicitly been told to block all vendors this quarter" — and a rule that they must push back at least twice. The rep's job isn't to win, it's to stay conversational under a second refusal. That's the skill.

Drill silence separately. The single most transferable micro-skill is tolerating a pause. Most reps fill three seconds of quiet with an apology and lose the frame. Drill it with a timer, in isolation, before any script work: ask a question, count to three, say nothing. It feels absurd in practice and it's invisible on a real call.

Script the second question, not just the first. Every play has a predictable follow-up from the gatekeeper — usually "What's this regarding?" A rep with a strong opener and no answer to that question is worse off than one with a mediocre opener and a crisp, non-sales-sounding second line. Write the second and third turns for every play in the deck. That's where sessions fail in the field.

Sequence the rollout over four weeks. Week one, permission plays only, everyone, tracked. Week two, add the email follow-up play — which requires that the emails actually got sent, so it forces sequence hygiene as a side effect. Week three, add referral and partner plays for the reps who have the relationships to support them. Week four, review the disposition data and cut whatever is under the floor.

Make it stick with call review, not more training. Pull three recordings per rep per month where the call died at the gatekeeper, and review them as a group. Reps learn more from hearing a peer lose a call they could have won than from another slide deck.

Where gatekeeper handling connects to the rest of the funnel

Treating this as an isolated skill is the most common structural mistake, and it caps the ceiling on any session you run.

Upstream, list quality does more work than any script. If your rep is calling a main switchboard because the list has no direct dials, you've made a data problem into a training problem. Direct-dial coverage, verified titles, and correct org mapping remove the gatekeeper from a large share of calls entirely. Before investing heavily in gatekeeper training, check what percentage of your list actually requires it — sometimes the answer is 20%, and the training budget belongs elsewhere.

Sideways, the email and social channels feed the phone. The strongest phone opener available is a truthful reference to a message the prospect has already seen. That means sequence design — send first, call second, reference the send — converts a cold permission play into a warm context play at no extra cost. Teams that run phone and email as separate motions leave this on the table.

Downstream, the gatekeeper doesn't disappear after the transfer. In enterprise deals the executive assistant controls scheduling for the entire cycle. A rep who bulldozed past them on call one will find every meeting request mysteriously hard to book in month three. The strategic move — and this is the thing most training misses — is to treat the gatekeeper as a stakeholder to be won, not a door to be passed. Get their name, use it, thank them by name on the follow-up, and copy them on scheduling. In a long cycle, that relationship is worth more than the initial connect.

Comparable functions elsewhere. Recruiters screening past hiring-manager assistants, agencies pitching past media buyers, vendors navigating procurement portals, and clinical sales reps working past practice managers all face the same structure: a trained filter with a triage job and no incentive to take a risk on you. The plays transfer almost unchanged. What changes is the vocabulary and the acceptable pretext — a research framing that works in software sounds evasive in healthcare, where compliance context matters more.

Automation is reshaping the boundary. Voice-AI receptionists and automated screening layers are now the first filter at a growing share of accounts. They respond to categorization, not rapport — silence tactics and reciprocity plays do nothing against a system that is pattern-matching your stated reason for calling. Against an automated screen, the useful move is to state a clear, specific, non-sales category and let the routing logic do its job. Expect this share to grow, and expect the human plays to become more valuable precisely because they're scarcer.

Related questions

Should reps ever give their company name to a gatekeeper?

Yes. Refusing to identify yourself reads as evasive and gets you blocked faster. Give the name plainly and immediately follow with a specific, non-pitch reason for calling. Concealment is the tactic that trains gatekeepers to distrust everyone.

How many gatekeeper plays should one rep actually know?

Two or three, fluently. Ten half-memorized scripts produce hesitation, and hesitation is what gatekeepers screen on. Assign each rep one permission play and one context play matched to their accounts, then add a third only after the first two are automatic.

What if the gatekeeper asks who referred you and you have no referral?

Say you have none. "No referral — I found the team through your recent product announcement and wanted to ask about it." Inventing a referrer is verifiable, and getting caught poisons the account permanently, not just the call.

Does this apply to inbound-heavy teams?

Partially. Inbound reps hit gatekeepers when routing multi-stakeholder deals or reaching an economic buyer the requester doesn't control. The routing logic holds; context plays are far stronger because inbound reps almost always have a genuine prior touch to reference.

How do these plays work against automated phone systems?

Differently. Rapport and silence tactics have no effect on a routing system. State a clear, specific category for your call and let the system route. Save the human plays for the human who picks up on the other end.

FAQ

How long before a new gatekeeper session shows up in the numbers?

Two to four weeks, assuming reps are having 8 to 15 gatekeeper conversations a day. That's a large enough sample per rep to see a directional shift. Anything faster is noise, and judging a play on a single bad morning is the most common reason good scripts get abandoned prematurely.

Should the session be run for the whole team at once or by segment?

By segment. SMB reps hitting shared admins and enterprise reps working dedicated executive assistants are solving different problems, and mixing them means half the room is drilling a play they'll never use. Split the role-play groups even if the framing portion is shared.

Is the pause-and-wait tactic manipulative?

It's a conversational habit, not a trick — plenty of skilled communicators pause before answering. It becomes manipulative when it's used to pressure someone who has already declined. If the gatekeeper has said no clearly, take the soft close and move on rather than waiting them out.

What should the CRM disposition field actually capture?

Which play was used, whether a transfer occurred, and if not, the reason: rushed, screened, no authority, or explicit block. Four reasons is enough. More granularity than that and reps stop filling it in honestly, which costs you more than the extra detail is worth.

How do you keep sessions from decaying after the training week?

Attach them to an existing ritual rather than scheduling new meetings. Three gatekeeper-failed recordings reviewed in the weekly pipeline meeting keeps the skill live at almost no cost. Standalone refresher trainings get cancelled by the third month, every time.

Can these plays be adapted for handling gatekeepers over email or LinkedIn?

Yes, with adjustment. The context plays port cleanly — referencing a real prior message or mutual contact works in any channel. The permission plays depend on real-time reciprocity and mostly don't survive the translation; asynchronous channels reward specificity and brevity over conversational maneuvering.

Sources

• Gong Labs — sales call research and data
• Salesloft resources and sales development guides
• HubSpot Sales Blog — cold calling and prospecting
• Gartner — sales practice research and insights
• Harvard Business Review — sales and negotiation
• MEDDICC — qualification methodology resources
• Outreach — sales engagement resources
• Sandler — sales training methodology
• LinkedIn Sales Blog

Related on PULSE

• [Top 10 Ready-to-Use Sessions for Prospecting Email Writing](/knowledge/st0681)
• [Top 10 Ready-to-Use Discovery Call Training Modules](/knowledge/st0669)
• [The Challenger Sale Method: Ready-to-Use Facilitator Deck for a 60-Minute Class](/knowledge/st0785)
• [Top 10 Consultative Selling Templates for Team Practice Sessions](/knowledge/st0730)
• [Top 10 Sales Training Sessions on Time Management for Reps](/knowledge/st0698)
• [Top 10 Sales Training Sessions on Negotiation Tactics](/knowledge/st0685)