# LinkedIn messaging playbook for multi-threading
> Message multiple stakeholders at one company without bypassing your first contact. Get practical scripts and flow strategies for B2B sales.
- HTML: https://getkinlead.com/linkedin-messaging-playbook-for-multi-threading
- Markdown: https://getkinlead.com/linkedin-messaging-playbook-for-multi-threading.md

**Short answer:** Multi-threading is messaging several stakeholders at one company so a single person ghosting you doesn't kill the deal. You must be transparent about who else you are talking to so you don't look like you are sneaking around.

## Pick your stakeholders

Don't message every person with a similar title. If you hit five people in one department with the same pitch, they will talk about it in their internal Slack. You need to target different roles that see the problem from different angles.

Map the company by finding the person who uses the tool, the person who pays for it, and the person who can block the installation. When you have all three, you aren't dependent on one person's mood or schedule.

The user is often your champion. They feel the daily friction and want it gone. The budget holder cares about the bottom line and risk. The blocker usually cares about security, IT standards, or how much work it takes to switch systems. If you only talk to the user, the budget holder might kill the deal because they don't see the ROI. If you only talk to the budget holder, the user might kill it because they think the tool is a burden.

| | Role | Perspective | Goal |
| --- | --- | --- | --- |
| The User | Feels the daily pain. | Confirm the pain is real. |
| The Budget Holder | Cares about ROI and risk. | Get a discovery call or pilot. |
| The Blocker | Focuses on security and integration. | Find technical hurdles early. |

## The transparency rule

Don't pretend you are starting from scratch with every person. If you message a VP like you've never heard of the company, but you've been chatting with a manager for two weeks, you look disorganized. It's worse if they realize you're trying to go over the manager's head to get a faster yes.

Be honest about your other conversations to create internal social proof. You are no longer a stranger; you are someone already talking to their team. This makes the second and third contacts more likely to reply because the risk is lower. They know a colleague has already vetted you to some degree.

When you name-drop a colleague, you move from a cold pitch to a warm referral. Even if the colleague hasn't explicitly introduced you, mentioning the conversation signals that you've done your homework and are acting in good faith. This prevents the 'who is this person' reaction from the executive team.

The goal is to create a web of conversations. If the manager leaves the company or gets promoted, you still have a line of communication with the VP and the IT director. You aren't starting from zero every time a single point of contact disappears.

**Sneaking around**

- Hi Sarah, I see you oversee marketing at Acme. I'd love to show you how we help with lead gen.
- Hi Mark, I'm reaching out to see if you have any problems with your current CRM.

**Transparent multi-threading**

- Hi Sarah, I'm chatting with James in your marketing team about your lead gen process. He mentioned you oversee the department, so I wanted to see if this aligns with your goals for the quarter.
- Hi Mark, I'm in touch with Sarah regarding your CRM goals. Since you handle the daily administration, I wanted to see if this would actually save you time.

## Scripts for the second and third contact

Change your message based on the role. Managers care about efficiency, VPs care about the bottom line, and blockers care that you won't break their systems. You cannot send the same script to three different people at the same company.

Keep these short. You aren't closing the deal in a connection request. You are just proving you are already in the building and have a valid reason to be there. The focus should be on the bridge between the person you're talking to and the person you've already spoken with.

If you're reaching out to a VP after talking to a manager, focus on the business outcome. If you're reaching out to a technical lead after talking to a VP, focus on the implementation and the lack of friction. This shows you understand the internal dynamics of their organization.

Avoid using generic praise or fluffy language. Don't tell a VP their company is a 'testament to innovation'. Just tell them you're talking to their team about a specific problem and want to ensure the solution fits their high-level strategy.

- **you:** Hi David, I'm talking with Elena about the onboarding bottlenecks at Northwind. She mentioned you oversee the operations team, so I wanted to see if solving this aligns with your goals for the quarter.
- **them:** I haven't spoken to Elena about this yet, but it is on my radar. What exactly are you discussing?
- **you:** We're looking at how to automate the document verification step. Elena thinks it'll save her team 10 hours a week. I can send over a brief summary of the approach if that helps?

> Always name the first person you contacted. It turns a cold pitch into a warm referral.

## Managing the conversation flow

Complexity grows when multiple people reply. You can't keep five separate threads going forever. You need a plan to move these conversations into a single path toward a meeting. If you keep answering the same questions in five different LinkedIn threads, you'll eventually contradict yourself.

If people are moving in the same direction, move them off LinkedIn into a shared environment. This stops you from repeating the same info five times and lets the stakeholders talk to each other. A shared email thread or a calendar invite with all key players is the goal.

Be careful not to alienate your first contact. If you jump straight to the CEO, the manager who helped you might feel betrayed. Always frame the move upward as a way to help the manager get the resources or approval they need to solve their problem.

When a blocker raises an objection, don't fight them in a vacuum. Use the interest from the budget holder to motivate the blocker to find a way to make it work. Conversely, use the technical concerns of the blocker to show the budget holder that you are being thorough about risk.

1. **Group the context.** If two or more people show interest, suggest a joint call or a group email thread to force internal alignment.
2. **Defer to the hierarchy.** If a VP says yes but the user is hesitant, don't argue with the user. Ask the VP how to address those concerns so the project moves forward.
3. **Update the original contact.** Tell your first lead you've reached out to their boss. Say, 'I'm going to loop in Sarah to make sure this fits the broader budget' so they don't feel bypassed.
4. **Consolidate the win.** Once all parties agree on the value, move to a single proposal document that addresses the user's pain, the VP's ROI, and the blocker's security needs.

## Handling common multi-threading roadblocks

Sometimes a stakeholder will tell you they aren't the right person, but they won't give you a name. In this case, ask them who typically handles the budget for that specific outcome. Don't ask 'who is the boss', ask 'who is responsible for the X goal'.

If you get a 'no' from one person but a 'maybe' from another, don't panic. B2B buying is rarely a unanimous vote at the start. It's about finding the person with the most pain and the most power, then using them to pull the others along.

If you find yourself in a situation where two stakeholders are disagreeing in your threads, do not take a side. Position yourself as the expert who can provide the data to help them make a decision. Offer a short demo where both can see the tool and discuss their different requirements in real-time.

Avoid the trap of 'over-threading'. If you message ten people at a 50-person company, you'll look like a spammer. Stick to the core roles: the user, the buyer, and the technical gatekeeper. Any more than that usually creates noise rather than signal.

```
Hi [Name], I'm chatting with [Colleague] about [Specific Problem]. Since you handle [Their Specific Role], I wanted to see if [Proposed Solution] fits into your current priorities for [Quarter/Year]. Would it make sense to loop you into a brief conversation?
```

## Doing this with Kinlead

Use the [Steal Customers](/features/steal-customers) agent to find people at a target company who comment on competitor posts. This gives you a list of active stakeholders who are already thinking about the problem you solve.

Put these stakeholders into [lead groups](/features/lead-groups-and-scoring) and use a sales playbook for a consistent tone. Set the AI to hand the conversation to you at the first reply. This lets you manually coordinate the multi-thread so you don't contradict yourself across different roles.

Because Kinlead sends at a human pace (one action every 5 minutes) and respects your set daily limits, you can scale this approach across multiple accounts without triggering LinkedIn's safety warnings. You can manage all these threads in one [unified inbox](/features/unified-inbox) and prioritize the replies that show the most intent.

## Related

- [AI SDR Playbook](https://getkinlead.com/ai-sdr-playbook-for-industry-disruptors.md)
- [Lead Groups and Scoring](https://getkinlead.com/features/lead-groups-and-scoring.md)
- [Unified Inbox](https://getkinlead.com/features/unified-inbox.md)

## Common questions

**Should I message everyone at once or wait for a reply?**

Wait for a response from your primary contact. Use that baseline of interest as the hook to reach out to the other stakeholders.

**What if the first person tells me not to contact their boss?**

Respect the request. Pushing past a direct no from a champion creates a bad impression that will reach the boss before you do.

**How many people at one company is too many?**

Three to five is usually the limit for small or mid-sized companies. In enterprises, you can go wider if you group them by department.

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