# How to send connection requests to multiple people at one company
> Learn how to sequence LinkedIn connection requests to multiple stakeholders at one account without looking like a bot or spamming the company.
- HTML: https://getkinlead.com/connection-requests-for-multi-threaded-accounts
- Markdown: https://getkinlead.com/connection-requests-for-multi-threaded-accounts.md

**Short answer:** To connect with multiple people at one company without looking like a bot, stagger your requests across different roles and timeframes. Start with the end user, then the manager, and finally the executive, using unique hooks for each to avoid looking like a coordinated spam attack.

## The multi-thread strategy

If you send five connection requests to the same company in ten minutes, you look like a script with a target list. People in the same department talk. When a VP, a director and a manager all see your name in their notifications at the same time, they have a reason to compare notes and ignore you.

Multi-threading means building relationships with several people at one account to raise your odds of a deal. The goal is to create a presence that feels like normal networking in their industry. You want each person to see a request that makes sense for their role, not a copy of the same pitch sent to their colleagues.

A good multi-thread starts with one person who replies. That reply gives you a reason to contact the next person: 'I was talking with Sarah about onboarding and she thought you might own the process.' The second request now has a source, and the source is a colleague.

**The bot approach**

- Sending five requests to the VP, director and manager on Tuesday morning.
- Using the same generic template for every person at the company.
- Following up with everyone on the same day.

**The human approach**

- Sending one request to a manager on Monday, a director on Wednesday and a VP the following week.
- Changing the hook based on the specific role of the person.
- Waiting for a response from one person before moving to the next.

## Mapping your entry points

You cannot treat a C-level executive the same way you treat a coordinator. Each role has different pressures and goals. If you ask a VP about a specific software bug, you look like you do not understand their job. If you ask a coordinator about the five-year strategic vision, you waste their time.

Start by identifying who feels the pain your product solves. These are your end users. They are usually more open to connecting and can give you the internal context you need to make your message to the boss more effective. Then map the manager who owns the process and the executive who signs the budget.

Write down the role you are contacting and the problem you think they own. If you cannot name the problem in one sentence, you are not ready to send the request. A vague reason to connect is what makes the request look automated.

| | Role | Priority | Goal |
| --- | --- | --- | --- |
| End user | High | Confirm the problem exists and get workflow details |
| Manager | Medium | Get a referral to the budget owner or internal champion |
| Executive | Low | High-level validation or a top-down directive to the team |

## Writing non-robotic notes

The common mistake in multi-threading is the copy-paste. Even when you change the name, the sentence structure often stays the same. If two colleagues compare notes, they see the pattern right away.

Your notes should be short and focused on the person, not your product. Use the end user to gather information, the manager to find the path to a deal and the executive to align with company goals. That makes your outreach feel like separate, intentional conversations.

Do not send the same article or case study to everyone. The end user wants a workflow detail. The manager wants a path to a decision. The executive wants a business outcome. If you only have one asset, use it with the person it fits and write a plain note to the others.

- **you:** Hi Sarah, saw your post about remote onboarding. How is your team handling the documentation side today?
- **them:** It's a mess. We're still using one giant Google Doc.
- **draft:** To the manager: Hi Mark, I'm talking with a few people in your department about onboarding friction. Thought it made sense to connect.
- **draft:** To the exec: Hi Jane, I've been following your company's expansion into the EMEA market. Would like to keep in touch.

## The sending sequence

Timing is the difference between a conversation and a block. Space your requests so they do not land together in a way that looks automated. If you get a response from one person, use that momentum to fuel the next request.

If the end user accepts and tells you their manager makes the decisions, you have a reason to message that manager that is not a cold pitch. Saying you are already talking to their team gives the manager context for why you appeared.

If someone declines or ignores you, do not rush to the next person at the same company. Give the account a few days. A request that arrives right after a rejection can feel like you are working down a list, because you are.

1. **Day 1: the end user.** Send a request to the person doing the actual work. Ask a specific question about their daily workflow or a recent post they wrote.
2. **Day 3: the manager.** If the user accepted, mention that you are talking to people in their department. If they did not, send a request focused on team efficiency.
3. **Day 7: the executive.** Send a request to the VP or C-level. Keep it high-level and focused on company growth or industry trends.
4. **Day 10: the warmest lead.** Follow up with whoever gave you the most engagement. This is where you ask for a meeting.

> If a request stays pending for a week, do not send another request to the same company. Wait until the first one is accepted or withdrawn.

## How to keep your story straight across people

People at the same company compare notes more often than you think, especially when the message touches a shared problem. Keep a simple record of who you contacted, what you said and what they told you. A spreadsheet works. A note in your CRM works if you have one. The point is to avoid asking the same question twice or contradicting yourself.

When someone says they are not the right person, ask who owns the problem and whether you can mention their name. That turns a dead end into a warm path. When someone says they already saw your request to their boss, be direct. Say you are reaching out to a few people to find the best person to talk to about a specific problem. Most people accept that when your tone is helpful.

Keep the next step for each person separate. The end user may be ready for a short call. The manager may want a one-page summary. The executive may want a meeting with the team. Treating those as the same step is how you lose the thread.

- Write down the exact hook you used for each person.
- Note any internal names they mention.
- Keep the next step for each person separate.
- Stop contacting a company for a week if two people ignore you.

## Doing this with Kinlead

Kinlead can hold the list and the timing. The Steal Customers agent watches competitor company pages and optional founder or employee profiles, reads 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.

Kinlead sends from your own LinkedIn account at a human pace: each account sends at most one action every 5 minutes, inside daily invite and message limits you set and inside a send window in the lead's time zone. The AI writes connection notes under 200 characters that open with why that person became a lead. You can read and edit queued messages on the Actions page before they send.

Campaigns can point at any lead group, so you can keep one group for a target account and run a separate sequence for each role. Replies from every campaign land in one inbox, classified by intent, with interested replies first. For teams, a Pro admin can invite teammates by email and choose which workspaces each teammate can open. Each teammate signs in with their own login and can connect their own LinkedIn.

## Related

- [AI LinkedIn connection templates](https://getkinlead.com/ai-linkedin-connection-request-templates.md)
- [AI sales playbook](https://getkinlead.com/ai-sales-playbook-for-linkedin-outreach.md)
- [Campaigns and send windows](https://getkinlead.com/features/campaigns-and-send-windows.md)

## Common questions

**What if two people at the same company tell me to talk to the same person?**

That is a useful signal. Message that person and mention both names. Say, 'Sarah and Mark both suggested I reach out to you about X.' It turns a cold lead into a double referral.

**Should I send a connection request or a direct message first?**

Send a connection request first for most roles. It is lighter than a direct message and gives the person an easy way to ignore you without an awkward inbox item. Use a direct message when you have a warm intro or a specific reason to write.

**How do I handle it when a lead mentions they already saw my request to their boss?**

Be honest. Tell them you are reaching out to a few people to find the best person to talk to about a specific problem. Most people understand that when your tone is helpful rather than pushy.

**How many people should I contact at one company?**

Start with two or three: the end user, the manager and one executive. Add more only when you get a reply or a referral. A wide blast to every employee makes the account harder to open.

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