The gatekeeper is the second-most expensive line item on most outbound P&Ls, after the dialer. 82% of decision-makers say reps are “poorly prepared” on first calls (Forrester, 2025), and a significant share of that signal traces back to reps who blew the 12 seconds they had with the executive assistant. The script does the work. The voice carries it. The dialer infrastructure decides whether the call rings clean enough to even reach the script.
Most articles on gatekeepers frame the conversation as adversarial: bypass, trick, skip. That framing wastes 3 seconds per call repairing tone, which compounds across 70 to 250 dials per day. The reps booking the most meetings in 2026 do three things differently. They prepare 7 scripts so they pick the right one based on who picks up. They dial verified mobile direct when the data exists, so the gatekeeper is not in the workflow at all. And they fix the dialer infrastructure underneath, so the call rings without a Spam Likely tag before the gatekeeper even reaches for the receiver.
This guide gives you the 7 scripts, the data that lets you skip the gate entirely, and the dialer setup that makes both layers work in 2026.
Who gatekeepers actually are (and what they’re optimizing for)
A gatekeeper is the person between you and the decision-maker. In SMB they are usually the receptionist, in mid-market a shared executive assistant, in enterprise a dedicated chief of staff. The script that works on each is different, and reps who use one script across all three lose 30% of the meetings they could have booked at the mid-market and enterprise layer.
The gatekeeper is not trying to block you. They are trying to not waste the executive’s time on something the executive would have wanted them to filter. That is a useful frame: every gatekeeper interaction is the gatekeeper running a quick relevance test on your behalf. If you can pass the test in 12 seconds, the transfer happens.
The relevance test has three inputs:
- Tone. The gatekeeper hears whether you sound like an internal call or an outbound rep within the first 3 to 5 seconds. Confidence (not arrogance) signals legitimacy.
- Specificity. A vague reason for the call (“I wanted to discuss our services”) fails the test instantly. A specific reason (“I noticed your team’s hiring announcement and wanted 30 seconds about how peer teams handle the first 90 days”) passes.
- Respect for the executive’s time. Reps who promise a 30-second ask earn more transfers than reps who say “I just wanted to chat for a minute.” The 30-second framing tells the gatekeeper the rep has thought about the cost of interruption, which is exactly the gatekeeper’s job to protect.
For the broader call structure that frames where the gatekeeper conversation fits, see the complete cold calling guide. For the openers that pick up immediately after the transfer lands, see proven cold call opener scripts.
The 7 cold call gatekeeper scripts
Memorize all 7. Pick the right one in real time based on who picks up the phone and what they say in the first 10 seconds. Reading a script verbatim is the fastest way to fail the relevance test.
Script 1, First-name request (the default)
“Hi, this is [your first name]. Can you put me through to [prospect’s first name]?”
Delivered in the tone of someone who expects the transfer. No company name, no last name, no over-explanation. Silence after the request. Top quartile reps win this 60-70% of the time on SMB and small mid-market. Falls off above 200-employee companies, where the gatekeeper expects more context.
Script 2, Permission-based (when Script 1 stalls)
“Hi, I know I’m calling out of the blue. Is now a fine moment to ask if [prospect’s first name] is around, or should I try later?”
Acknowledges the cold call directly, which counterintuitively earns more transfers than pretending the call is routine. Use when the gatekeeper challenges the first-name request with “what is this regarding?”
Script 3, Email follow-up reference
“Hi, I’m [first name] from [company]. I’m following up on the email I sent [prospect’s first name] on [day], wanted to see if I could reach them for 30 seconds.”
Requires sending a real email 24 to 48 hours before the dial. The email creates a referenceable artifact that the gatekeeper can verify with one click. Lift on transfer rate: roughly 15-20% in mid-market US B2B SaaS.
Script 4, Peer reference (works at enterprise)
“Hi, I work with [Peer Company]‘s VP Sales on [specific topic]. Wanted 30 seconds with [prospect’s first name] about something specific to their team.”
The peer name does the work. Use real peers, in the prospect’s industry, ideally one the prospect would recognize. Generic peer references (“we work with companies like yours”) fail instantly at enterprise gatekeeper level.
Script 5, Direct ask for help (the executive assistant move)
“Hi, I could really use your help. I have a specific message for [prospect’s first name] about [specific topic]. What’s the best way to make sure they see it?”
Asks the assistant to be the routing expert they actually are. Honest, respectful, and bypasses the screening reflex because you are not asking for a transfer, you are asking for advice. Best script for chief of staff and senior executive assistants.
Script 6, Off-hours bypass
[No script. Dial at 8:00 AM or 5:45 PM local time.]
The gatekeeper is not at their desk. The decision-maker often is. Pair with verified mobile data when available. Off-hours calling lifts direct-pickup rates by roughly 30-40% across most US B2B ICPs.
Script 7, Mobile direct (the skip)
[Dial the prospect’s verified mobile number.]
No script needed because the gatekeeper is not in the conversation. Verified mobile data from Cognism, ZoomInfo, Apollo, or Lusha is the structural fix for gatekeeper friction at scale. Reps dialing verified mobile direct reach the prospect at roughly 3 times the rate of reps dialing the corporate switchboard. The 7-script library is the fallback when mobile data is missing or stale.
The gatekeeper is not the problem. The dialer infrastructure that lets your team ring 250 verified mobile numbers a day cleanly is the answer. Scripts are the fallback when the data is missing.
What NOT to say (the red flags that kill the transfer)
The scripts above carry tested patterns. The list below carries failure modes that show up on coached call recordings every quarter, across SaaS, real estate, and insurance ICPs.
- Do not lie about being a personal contact. “Yeah, [prospect] and I go way back” gets you through the gatekeeper and burns the prospect relationship the moment they pick up. The gatekeeper remembers and tells the executive. The meeting is dead before it books.
- Do not over-explain. “Hi, I’m [first name], I’m calling from [company] because we help companies like yours with [pain point] and I wanted to see if [prospect] would be interested in a quick chat about…” fails the relevance test in the first 12 seconds. Trim ruthlessly.
- Do not pitch the gatekeeper. They are not the buyer. A pitch triggers the screening reflex instantly. Be brief, professional, and route-focused.
- Do not apologize. “Sorry to bother you” downgrades your tone before the conversation starts. The gatekeeper hears it as a signal that you do not belong on this call.
- Do not push back if they refuse to transfer. Ask for the best email or callback time, then end the call cleanly. A pushy rep is a remembered rep. Try the same number tomorrow with Script 3 (email follow-up) or pivot to off-hours.
A sixth pattern worth flagging: do not stack two questions in your opener. “Can I speak with [prospect], and if not, what’s the best time to call back?” gives the gatekeeper cover to skip the first request. One ask at a time, then silence.
When you do get through, the opener you deliver to the decision-maker is its own discipline. See the cold calling fundamentals for the call-mechanic moves, and the cold call objections playbook for the responses that handle the early brush-off after you clear the gate.
The dialer setup that gets you to the gate (and through it)
The script is downstream of three infrastructure decisions. Reps who blame the gatekeeper when their connect rates drop usually have a dialer problem, not a script problem.
Caller-ID reputation. Carrier reputation algorithms (Hiya, TNS, Robokiller) flag numbers that dial at high volume from a single area code or that recipients repeatedly ignore. Once a number is tagged Spam Likely, its connect rate drops 70-90% overnight, and gatekeepers see the tag before they pick up. The fix is number rotation (a pool of 5 to 10 outbound numbers per rep, rotated automatically) and STIR/SHAKEN attestation through a compliant dialer. See how to fix Spam Likely caller ID for the rehab playbook.
Local presence dialing. Matching the rep’s outbound caller-ID to the prospect’s area code lifts connect rates by 20-30% in most ICP segments. The gatekeeper sees a local number and treats the call as more legitimate than a 1-800 or out-of-state number. Most modern dialers handle local presence at the platform layer.
Verified mobile data. The structural fix that makes scripts 1-5 mostly unnecessary. Reps dialing verified mobile direct reach decision-makers at roughly 3 times the rate of reps dialing the corporate switchboard. Verified mobile data comes from B2B data providers (Cognism, ZoomInfo, Apollo, Lusha); compliance with TCPA mobile rules is non-negotiable when dialing US mobile numbers. For the TCPA framework around cold calling cell phones, see the regulatory deep-dive.
Dialing volume per rep. A rep doing 70 manual dials per day will hit a gatekeeper on roughly 30 to 50 of those calls and lose 5 to 8 minutes per failed transfer to the next dial. A rep on a 4-line parallel dialer doing 250 to 400 dials per day filters dead lines and voicemails at 95% accuracy, so the gatekeeper conversations happen at 3 times the volume, and the rep iterates the 7 scripts at 3 times the speed. The 7 scripts that win 60-70% of transfers do not get to 60-70% by accident. They get there because the rep tested them across 50 to 100 conversations a week, which is impossible without the dialing infrastructure underneath.
The other lever sales leaders underestimate: why prospects do not answer cold calls is mostly a technical question (caller-ID, attestation, screening), not a behavioral one. The reps who win the gatekeeper consistently also have the caller-ID reputation that makes the call ring in the first place.
The takeaway
The gatekeeper is not the problem. The script library and the dialer infrastructure together are the answer, and most teams over-invest in the first and under-invest in the second. Seven scripts, picked in real time based on who picks up, win 60-70% of transfers at the SMB and mid-market layer. Verified mobile data plus off-hours timing cuts the gatekeeper out of 40-50% of dials at the upper end of mid-market and enterprise. Caller-ID reputation, attestation, and number rotation decide whether the call rings clean enough to even reach the script.
Pull your team’s last 90 days of call recordings this week and count the gatekeeper transfers. If the rate is below 50%, the script library is the gap, and the 7 patterns above will move the number in two weeks. If the rate is above 50% but the team still books fewer meetings than peers, the gap is downstream: the rep wins the gate and loses the prospect in the first 30 seconds, which is a different fix. And if the rep is losing the call before the gatekeeper even picks up, the gap is the dialer infrastructure, which is the highest-ROI fix available to outbound teams in 2026.
