# How to message a gatekeeper on LinkedIn
> Message assistants and managers before the executive. Scripts for the first ask, the send me more info reply, and the follow-up when they go quiet.
- HTML: https://getkinlead.com/linkedin-messaging-for-decision-makers
- Markdown: https://getkinlead.com/linkedin-messaging-for-decision-makers.md

**Short answer:** Ask the assistant or manager for their read on the situation before you pitch the executive. Gatekeepers decide what reaches the executive's desk, so a small, specific question about who owns the problem gets you further than a calendar request.

## Why the direct approach fails

Most founders and sales reps send the same pitch to the CEO. The message reads like a template, so it gets ignored or reported. You lose the lead and you spend a little of your account's reputation at the same time.

The assistant or manager sitting between you and that executive is paid to protect their time. They also decide what reaches the executive's desk. Push past them and you become a problem to be handled. Ask for their read on the situation and you become someone they can help.

There's a second cost that's easier to miss. When a gatekeeper remembers your name as the person who tried to jump the queue, they block the next message too, and the one after that. Getting this right the first time is cheaper than repairing it.

**The direct pitch**

- Hi Sarah, I see you're the CEO of Acme. We help companies like yours grow revenue by 20%. Do you have 15 minutes next Tuesday?
- I'm reaching out because our platform is the best in the market for your industry. I'd love to show you a demo.

**The bridge approach**

- Hi Mark, I'm trying to get a short document in front of Sarah about the EMEA expansion. You manage her calendar, so I wanted to ask whether that's on her list this quarter or if someone else owns it.
- Hi Jane, I'm looking for whoever handles vendor selection for logistics at Acme. Is that you, or should I be speaking with someone else?

## Who actually counts as a gatekeeper

The person you want controls the executive's calendar or owns the problem your product fixes. Those are two different jobs and they need different messages.

A chief of staff filters on strategy. An assistant filters on time. A manager filters on whether the fix works. Sending one message to all three wastes the only thing you get for free, which is a first impression.

Start with the role closest to your problem. If you sell something a team uses every day, the manager who runs that team will answer a question about the work. If you sell something the executive signs off on, the assistant or chief of staff knows whether it's on the list this quarter.

Ignore titles that sound senior but sit outside the decision. A regional marketing lead at a large company may have no route to the person you need. Check who the role reports to before you write.

| | Role | What they control | How to approach them |
| --- | --- | --- | --- |
| Executive assistant | The calendar and the inbox | Ask what the executive is focused on this quarter, then ask who owns it |
| Department manager | The budget and the daily pain | Lead with the problem and ask how the team handles it today |
| Chief of staff | Which initiatives get airtime | Ask whether the topic is on the roadmap before you describe your product |
| Operations lead | The tools and vendors already in use | Ask what's in place now and where it falls short |

## How to write the first message to a gatekeeper

The first message has one job: get a reply that tells you where to go next. Keep it under about 60 words, name the executive or the problem, and ask something the gatekeeper can answer from memory.

Ask for a map of the org before you ask for time. People like being the one who knows how their company works. A question about internal ownership costs them ten seconds and puts them in the expert seat.

- **you:** Hi Mark, I'm trying to get a short doc in front of Sarah about the EMEA expansion. You run her calendar, so I wanted to check whether that's a live topic this quarter.
- **them:** It's live. She's in planning for it now.
- **you:** Helpful. Is there someone on the team who owns the vendor side of that, or does it all sit with her?
- **them:** Priya on the ops team handles most of it. I can forward it to her if you want.
- **you:** That would help. I'll send you two paragraphs she can skim in a minute.

> No meeting request and no deck in that first note. The gatekeeper offered the forward because the ask was small enough to say yes to.

```
Hi {{first_name}}, I'm trying to get a short note in front of {{exec_name}} about {{topic}}. You run their calendar, so I wanted to ask whether that's live this quarter, and who on the team owns it if it is.

If it's easier, point me at the right person and I'll take it from there.
```

## When they say send me more info

This reply is a test. A 20-page PDF or a link to your homepage fails it, because the gatekeeper has to understand it before they can pass it on. They won't do that work.

Write the summary you would want if you had 30 seconds to decide whether something was worth forwarding. Three lines: the problem, what you do about it, and one thing you can actually back up.

1. **Write three lines they can forward.** One sentence on the problem, one on what you do about it, one on who else has the same problem. No adjectives and no percentages you can't source.
2. **Ask one question back.** Ask which part of the problem is loudest for them right now. The answer tells you whether to keep going and gives you something to reference in the next message.
3. **Offer to write the forward for them.** Say you'll draft two sentences they can paste to the executive. Most people take the offer because it removes the last bit of work.
4. **Agree a date to check back.** Ask when the executive's planning cycle lands and offer to follow up then. It gives you a reason to reappear that isn't chasing.

> Never send a deck in the first two messages. If the gatekeeper can't summarise it in one line, it won't reach the executive.

## What to do when the gatekeeper goes quiet

Silence usually means your message landed at a bad moment. One follow-up is fine. Two turns you into the person they mute.

> If that gets nothing, move sideways inside the same account. Try the manager who owns the problem, or someone in the same role at a similar company. Keep the original gatekeeper in a lead group so you don't message them again by accident.

```
Hi {{first_name}}, circling back once. If {{topic}} has moved on, tell me and I'll close the loop. If it's still live, I can send two paragraphs {{exec_name}} can skim in a minute.
```

## Handing off to the executive

When the gatekeeper forwards your note, the executive opens it cold. Two things help: the gatekeeper's name in the first line, and a reference to the specific thing they said.

- **you:** Hi Sarah, Mark passed along my note on EMEA vendor selection. He mentioned you're in planning this quarter, so I'll keep this short.
- **them:** Thanks. What does your setup do that our current one doesn't?
- **you:** It scores every inbound lead against your ideal customer profile and drops the ones below the line, so Priya's team stops working the wrong list. Want the two-page version or 15 minutes with her?

> Keep your reply short too. They asked one question, so answer that question and offer the next step. If they want detail, they'll ask for it.

## Doing this with Kinlead

Kinlead finds people who match the customer you describe, or your website, and scores each lead from 0 to 100 against that profile. Leads below the fit line aren't kept, so your lead groups stay small enough to work through.

For gatekeeper work, the [Steal Customers agent](/features/steal-customers) is the useful one. It watches competitor company pages and optional founder or employee profiles, reads the comments on their recent posts, and turns commenters who look like buyers into leads. Each lead keeps the post URL, what the post was about and what they commented, which gives you something real to open with.

Put those leads in a [lead group](/features/lead-groups-and-scoring) and point a campaign at it. Load your referral scripts into the campaign's sales playbook, which is your own sales script, and the AI writes messages and follow-ups from it. Set the campaign to hand the conversation to you at the first reply, so you take over the moment a gatekeeper answers.

Kinlead sends at most one action every 5 minutes per LinkedIn account, inside daily limits you set and inside a send window in the lead's time zone. You can start a [7-day free trial](/signup) or [book a demo](/demo).

## Related

- [Book a demo](https://getkinlead.com/demo.md)
- [Pricing plans](https://getkinlead.com/pricing.md)
- [Steal Customers feature](https://getkinlead.com/features/steal-customers.md)

## Common questions

**Should I name the executive in the first message?**

Yes, if you know who owns the decision. Naming them shows you picked this company on purpose, and it gives the gatekeeper something specific to confirm or correct.

**What if the gatekeeper says they handle it themselves?**

Take them at their word and ask what they're doing about the problem today. Plenty of managers own both the budget and the decision, and treating them as a detour wastes a real conversation.

**How long should I wait before following up?**

A week is reasonable for a first follow-up. After that, move to another person in the account and leave the original contact alone for a while.

**Do I need Sales Navigator to find assistants and managers?**

No. Standard LinkedIn search filters for job title and company find most of them. Kinlead uses LinkedIn's standard search too, so a Sales Navigator seat isn't required.

[Create a Kinlead account](https://getkinlead.com/signup) or [book a call](https://getkinlead.com/demo) to talk through pricing and setup.
