# How to connect with former managers on LinkedIn
> Reach out to old bosses for business introductions or advice without sounding transactional. Use these practical templates and outreach strategies.
- HTML: https://getkinlead.com/connection-requests-for-former-bosses
- Markdown: https://getkinlead.com/connection-requests-for-former-bosses.md

**Short answer:** Avoid generic requests when messaging a former manager. Reference a specific project you worked on together or advice they gave you that you still use. Remind them of your competence and the value you provided before asking for a referral or meeting.

## The mindset for reaching out

Messaging a former manager is different from messaging a peer. With a peer, you shared the grind of daily tasks. With a manager, the relationship rested on your ability to deliver results that made them look good to their own bosses.

When you reach out after a long gap, the manager wonders if you are a high performer or someone struggling. You need to signal that you are successful and that your request is a strategic move, not a plea for help.

Shift the dynamic from employee and boss to two professionals in the same industry. Highlight the mentorship they provided and the outcomes you achieved under their leadership.

A former manager has less context on your recent work. They remember your output, not your current title. That is why the first message should remind them of a result you delivered, not list everything you have done since. Do not apologize for the gap or explain why you disappeared. A short line like 'It has been a while' is enough. The message should look forward.

**Peer-style approach**

- Hey, it's been a while! How have you been?
- Remember that time we stayed late for the Q3 report?
- I'm looking for a new role, can you help me out?

**Manager-style approach**

- I'm applying a strategy you taught me about client retention and it's working well in my current role.
- I saw your recent post on scaling teams and it reminded me of how you structured our department in 2019.
- Since you know my work ethic and the industry, I'd value your perspective on a new project I'm building.

## Choosing your hook

Generic connection requests are easy to ignore. Use a hook that triggers a positive memory of your performance and reminds them you were an asset to their team.

Pick a hook based on how long it has been since you worked together. If it has been a few months, a simple update works. If it has been years, anchor the message in a shared success or a lesson they taught you.

Do not focus on your current need in the hook. The hook is only for the connection request. The business ask happens after they accept.

A good hook is specific enough that they can place you without opening your profile. It should mention a project, a team, or a piece of advice that only the two of you would know. Avoid hooks that require them to remember a small detail from years ago. If they have to search their memory, the note feels like a test. Use a project or result they would likely remember.

| | Hook type | When to use it | Example phrasing |
| --- | --- | --- | --- |
| The advice hook | When they were a strong mentor | I'm using the [Topic] framework you taught me and it's helping me hit my targets. |
| The update hook | When they've changed companies | I saw [Company] launched [Product]. It reminded me of when we built [Project] together. |
| The gratitude hook | After a long period of silence | I realized how much the [Specific Skill] I learned from you helped me get to where I am now. |
| The shared project hook | When you delivered a result together | I still think about how we handled [Project]. I use that approach in my current role. |

## Writing the connection request

The connection request is a filter, not a sales pitch. If you ask for a favor in the invite, you risk a decline because you have created a debt before you have rekindled the relationship.

Keep the note short. People read these on a phone. If the text is too long, they will skim it and forget to hit accept.

Focus on the manager and the shared project. This makes the message about their influence and your shared success, which complements their leadership.

1. **Reference a specific result.** Mention a project, a metric, or a specific piece of advice. Avoid saying 'I enjoyed working with you' because it's too vague.
2. **State your current context.** Briefly mention your current role or company so they know you've progressed in your career.
3. **End with low pressure.** Use a closing like 'Hope you're doing well' or 'Would love to reconnect'. Do not ask for a meeting yet.

> Keep your connection note short enough to read on a phone. Long notes get cut off.

```
Hi [Name], I still use the [specific framework] you taught me on [project]. I'm now [role] at [company] and wanted to reconnect. Hope you're well.
```

## Moving from connection to business

Once the request is accepted, do not pitch immediately. Wait for their response or give it a day. The transition from catching up to business should feel like a natural progression.

The bridge matters. Connect your past performance under them to your current business goal. This explains why you are asking them specifically for help.

Be specific with your ask. Asking 'Can you help me?' is work for the manager. Asking 'Would you be open to introducing me to the VP of Sales at Acme?' is a simple yes or no decision.

If they ask what you need, give one sentence and one easy next step. Do not send a long document unless they ask for it. The goal is to make saying yes simple.

- **you:** Thanks for connecting! I've been following your work at Northwind and saw the new expansion into the EU market. Looks like a great move.
- **them:** Thanks! It's been a wild ride. Great to see you're doing well at your new spot. How's the new role treating you?
- **you:** It's going great. I'm actually building a tool that helps agencies automate their lead scoring, similar to that project we did back in 2021. Since you know my work and the agency space, would you be open to introducing me to the Head of Ops at Apex? I think they'd find this useful.

## Handling a yes, a no, or silence

A yes is not permission to send a long brief. Reply with one sentence on what you need, one sentence on why they are the right person, and a link or file if it helps. Make the next step small: a forward, a short intro email, or a 15 minute call.

If they say no, thank them and ask if anyone else comes to mind. Do not argue or explain why they should help. A clean no leaves the door open for a later ask.

Silence is common. People change jobs, miss messages, or mean to reply and forget. Wait a week, send one short follow-up that adds a detail, then stop. If they do not answer after that, mark it and move on.

- They say yes: send the forwardable blurb, the intro email draft, and the exact ask in one message.
- They say no: thank them, ask for one alternate name, and close the loop.
- They go quiet: send one follow-up with a new detail, then leave it.

## Doing this with Kinlead

If you are reaching out to several former managers across different companies, Kinlead can run the outreach from your own LinkedIn account. It connects through Unipile and never stores your LinkedIn password. Each account sends at most one action every 5 minutes, inside the daily invite and message limits you set and inside a send window in the lead's time zone.

Import a short list of former managers as a CSV of LinkedIn profile URLs, put them in a lead group, and point a campaign at that group. Build the campaign with the goal and tone, add your own sales playbook if you have one, and the AI writes the messages and follow-ups from that. You can read and edit queued messages on the Actions page before they send, and pause any campaign.

Choose hand-off at the first reply, AI replies until real interest, or AI replies until a meeting is booked with your scheduling link. Replies from every campaign land in one inbox classified by intent, with interested replies first, and you get an email when someone replies. For the account side, [LinkedIn account safety](/features/linkedin-account-safety) explains how Kinlead keeps sends inside your limits and pauses invites if LinkedIn pushes back.

## Related

- [AI outreach for founders](https://getkinlead.com/ai-outreach-for-founder-led-sales.md)
- [Booking LinkedIn demos](https://getkinlead.com/use-cases/book-linkedin-demos.md)
- [Book a demo](https://getkinlead.com/demo.md)

## Common questions

**What if they don't respond to the invite?**

Give it two weeks. If they still haven't accepted, don't push. They may be inactive on LinkedIn or not in a place to reconnect.

**Should I use a formal or casual tone?**

Match the tone you had when you worked for them. If you used first names and joked, stay casual. If there was a strict hierarchy, remain professional.

**How long should I wait before asking for the business favor?**

Wait until the connection is accepted and at least one exchange of pleasantries has occurred. Jumping straight to the ask feels transactional.

**What if we parted on bad terms?**

Keep the first message light and do not rehash the past. If they do not reply, let it go. A forced reconnect rarely helps.

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