The situation
You dial the main line, and the person who answers is not the decision-maker, they are the person whose job includes deciding who reaches the decision-maker. A receptionist, an executive assistant, an office manager fielding calls between other duties. They ask who you are, what company you're with, and what this is regarding, and how you answer those three questions in the next fifteen seconds decides whether you get transferred or thanked for calling.
Most reps treat this as an obstacle to get around, so they either overexplain in a rush to sound important, or they try to slip past with something vague like "just following up on an email I sent." Both approaches read the same way from the other side of the desk: as someone trying to get past them rather than someone with a legitimate reason to be connected. Gatekeepers field dozens of calls like this a week. They are good at spotting the dodge.
Why reps lose here
Treating the gatekeeper as an obstacle instead of a person doing a job. The moment a rep's tone shifts, even slightly, to "just put me through," the gatekeeper hears it. Their job is to protect their boss's time, and a caller who is visibly trying to route around that job triggers the exact instinct that keeps calls from getting transferred.
Being vague about the reason for the call. "I wanted to talk to someone about your operations" is not a reason, it is a way of avoiding one. Gatekeepers cannot evaluate whether to transfer a call they cannot understand, so vagueness gets treated as a red flag rather than as mystery worth solving.
Not giving the gatekeeper anything to say if they push back internally. Even when a gatekeeper is willing to help, they often still have to justify a transfer or a message to the person they support. A rep who gives them nothing usable, no name, no specific reason, no company context, leaves them with nothing to say if asked "who was that and what did they want."
What the buyer is actually thinking
The person answering the phone is not the buyer, but how they read your call determines whether the actual buyer ever hears about it.
They are evaluating legitimacy first, interest second. Before a gatekeeper thinks about whether their boss would care about what you're selling, they are checking whether you sound like a real business call or a script. Confidence and specificity read as legitimate. Rehearsed enthusiasm reads as a script.
They often have real discretion, not just a rule to enforce. Many gatekeepers can use judgment about what gets through, especially for callers who are clear, brief, and respectful of their time. Treating every gatekeeper as an unmovable wall means missing the ones who would help if asked well.
They remember how they were treated. A gatekeeper who gets talked over, rushed, or condescended to has no reason to advocate for your call next time, and every reason to say "not available" reflexively. A gatekeeper who was treated as a colleague, not an obstacle, sometimes becomes the person who tells you when the right time to call back is.
The dialogue
The rep sells supply-chain forecasting software and is calling Meridian Foods, a regional food distributor, trying to reach the VP of Operations. Priya answers the main line.
Weak handling:
Priya: Meridian Foods, this is Priya.
Rep: Hi, can you put me through to whoever handles operations there?
Priya: I can take a message. What's this regarding?
Rep: Just following up on some information about improving supply chain efficiency, they'll know what it's about.
Priya: I don't have anything from you on file, and he's not really available for calls like this. I can pass along your number.
Nothing in the rep's answer gave Priya a reason to treat this as different from the dozen other cold calls she fields weekly. "They'll know what it's about" was meant to sound confident, but it read as evasive, because it assumed a relationship that does not exist yet. Priya has no name, no specific reason, and no way to represent this call if she wanted to.
Strong handling:
Priya: Meridian Foods, this is Priya.
Rep: Hi Priya, my name is Jordan, I'm calling from Fenwick Logistics Software. Quick question before I take up your time, who handles demand forecasting or inventory planning on the ops side there?
Priya: That would be Marcus, he's our VP of Operations. What's this about?
Rep: We build forecasting software for food distributors, and we just worked with two companies in your region on cutting spoilage from overordering perishables. I'd like fifteen minutes with Marcus to see if it's relevant to how Meridian handles that, but I don't want to take his time if it isn't a fit. Would it make sense for me to send you a short note on it first, so he can decide if it's worth a call?
Priya: He's usually pretty slammed, but I can pass that along. Send it to me and I'll flag it for him.
Rep: Appreciate it, Priya. I'll send that over in the next few minutes with your name on it so he knows it came through you. Is there a better time of day to try him directly if I don't hear back?
Priya: Mornings before ten are usually better. I'll let him know to expect something.
The rep opened by naming himself and his company instead of hiding behind vagueness, then asked a specific question that Priya could actually answer without evaluating whether to transfer anything yet. Naming a concrete, credible reason, spoilage from overordering, gave her something to represent internally. Offering the note as an option instead of demanding the transfer respected that she might not have the authority or inclination to connect him blind, and it gave her an easy way to help that did not require her to vouch for a stranger. Asking about a better callback time turned her into an ally instead of a barrier, and crediting her by name in the note gives Marcus a reason to trust that this cleared a real filter.
How to run this live
Set up a cold call scenario against a gatekeeper persona rather than the actual decision-maker, so the practice reps the moment before the real conversation even starts. Goals for the practice run:
- Open with your name and company before anything else, rather than leading with a vague reason for calling.
- State a specific, concrete reason the call matters to their business, not a generic value statement.
- Offer the gatekeeper an easy way to help, a note they can pass along, a specific time to try back, rather than demanding an immediate transfer.
- Notice whether your tone shifts when you sense resistance. A gatekeeper who senses you're trying to get past them, rather than through them, will hold the line every time.
Run it once against a gatekeeper who is willing to help if asked well, and once against one who is a genuine hard stop that day. Reading the difference, and staying respectful either way, is what this drill is for.
