Building sales pipelines across global markets

Conversation guide

5 cold calling scripts that help you navigate gatekeepers

Gatekeepers are not an obstacle to outsmart. They are part of the buying organization. These adaptable patterns help you communicate your purpose clearly, ask for the right direction, and protect the tone of the relationship.

05 SCRIPTS

Respect earns better direction

Use these patterns as flexible conversation structures—not lines to recite without listening.

Before you use the scripts

Aim for a clear route, not a clever bypass.

A good gatekeeper conversation is short, transparent, and useful. Your goal is to give the person enough context to help—not to pressure them into granting access.

A sales professional and gatekeeper using five respectful conversation paths to find the right contact
The strongest script is a prepared framework with room to listen, adapt, and respond honestly.

Five adaptable patterns

Choose the pattern that fits the moment.

Replace the bracketed language with precise, truthful context. Then say it in your own voice so it sounds like a conversation, not a performance.

  1. 01
    Script pattern

    When to use it

    The clear, context-first request

    Use this when you know the person you want to reach and can name the business topic in plain language.

    Hi, I’m trying to reach [name] about [specific business topic]. We help [relevant type of company] with [clear outcome]. Is [name] the right person for that conversation?

    Why it works

    It gives the gatekeeper enough information to route the call and invites a useful correction if your contact is not the right owner.

    Do

    Name a real topic such as lead qualification, CRM clean-up, or appointment setting.

    Don't

    Do not imply that the prospect expects your call when they do not.

  2. 02
    Script pattern

    When to use it

    The routing-expertise request

    Use this when you understand the problem area but are not certain who owns it inside the company.

    Could you point me in the right direction? I’m looking for the person responsible for [function or outcome]. Would that sit with [likely team], or somewhere else?

    Why it works

    The question respects the gatekeeper’s knowledge and makes the task specific enough to answer without forcing a transfer.

    Do

    Offer one sensible department as a starting point, then let them correct you.

    Don't

    Do not ask vaguely for ‘the decision-maker’; describe the responsibility instead.

  3. 03
    Script pattern

    When to use it

    The brief relevance check

    Use this when the gatekeeper asks for more detail before deciding whether to route the call.

    Of course. We support [peer companies or teams] with [specific challenge]. I wanted to ask [name] two quick questions to see whether it is relevant there. If it is not a current priority, I’ll leave it there.

    Why it works

    It explains the value, limits the ask, and lowers pressure without turning the gatekeeper into an audience for a full sales pitch.

    Do

    Keep the explanation to one challenge and one reasonable next step.

    Don't

    Do not stack features, buzzwords, or several unrelated benefits into the answer.

  4. 04
    Script pattern

    When to use it

    The ‘what is this regarding?’ answer

    Use this when you receive the most common screening question and need to make your purpose easy to relay.

    It’s regarding [specific issue] and whether [company] has a plan for [desired outcome]. My reason for calling is to share how we approach it and find out whether a short conversation would be useful.

    Why it works

    The answer is concise, transparent, and easy for the gatekeeper to repeat accurately to the person you are trying to reach.

    Do

    Use words the prospect’s team would naturally use to describe the issue.

    Don't

    Do not hide behind ‘a business matter,’ ‘an opportunity,’ or another empty phrase.

  5. 05
    Script pattern

    When to use it

    The respectful alternative

    Use this when a transfer is not available or the gatekeeper declines, but another low-friction path may still be appropriate.

    Understood—thanks for letting me know. Rather than keep calling, would it be better to send a short note for [name], or is there another person I should contact about [topic]?

    Why it works

    It accepts the boundary, reduces repeat-call friction, and gives the gatekeeper control over the most appropriate next step.

    Do

    Accept a final no graciously and keep any follow-up exactly as brief as promised.

    Don't

    Do not argue, apply urgency, or keep asking the same question in different words.

One final coaching note

Practice the structure, then listen.

Rehearse the purpose and the handoff—not every word. If the gatekeeper gives you new information, acknowledge it and adjust. A relevant response will always sound stronger than a perfectly delivered script that ignores the conversation.

Explore script development

Build a better call framework

Want scripts shaped around your market?

MRA can develop the opening, discovery flow, objection paths, and coaching notes your outbound team needs to hold clearer, more consistent conversations.