Use a truthful reason for contact, one relevant detail and one small ask. Personalization should change the question, not just the greeting.
Before you write: choose the person and the channel
Do not start with a template and search for people to receive it. Start with the reason a particular person might be able to help. A recruiter can clarify a process. A future peer can explain the work. A former colleague can speak to your capabilities. Asking all three for the same thing wastes the advantage of knowing who they are.
Respect the platform and the recipient. LinkedIn recommends invitations to people you know and trust and offers alternatives to inviting strangers. Where appropriate, use an available messaging channel such as InMail or Open Profile, or seek a consent-based introduction. An invitation acceptance is not permission for persistent promotional outreach. LinkedIn's policies prohibit spam and repetitive unwanted messages.
A useful message has three jobs
- Why youName the shared experience or relevant public work.
- Why thisConnect it to a specific role or question.
- A small askMake a useful answer possible without a meeting.
“I was impressed by your profile” could be sent to anyone. “Your talk distinguished onboarding from implementation; which owns customer handoff on your team?” could not. Be specific without pretending intimacy. Avoid references to family, personal photos or sensitive details that have nothing to do with the work.
Short is usually easier to assess, but brevity is a constraint, not a magic conversion trick. Remove your entire biography, flattery, multiple questions and a calendar link the person did not request. Keep enough context that the ask makes sense.
Four ways to begin
Hi Jo, I'm exploring operations roles after finishing the regional rollout we discussed last year. You moved from logistics into software operations; what was the biggest gap you had to close?
The person already knows you. You ask about a relevant experience, not for access to their entire network.
Hi Sam, we spoke after the finance panel about forecasting demand for a new product. Would you send the public article you mentioned? I'd like to read it before our next meetup.
Use an invitation note like this only when the meeting actually happened. The next step follows the conversation.
Hi Noor, your public walkthrough of Harbor's implementation process caught my attention. I'm considering the implementation manager opening and have led similar customer launches. Does that team own the handoff into customer success, or stop at go-live?
This is a question about the work, through an appropriate available message channel. It is not a disguised demand for a referral.
Hi Alex, I saw your post about hiring a customer operations lead, role CO-214. I rebuilt onboarding handoffs at a B2B services team and can share a short, non-confidential example. Is reducing handoff friction a priority for this hire?
A job ID helps them locate the role. Use this only if the person actually posted about hiring; do not infer hiring authority from a senior title.
Three messages for what happens next
Hi Noor, one follow-up on my question about the implementation role. I read the team's public case study and it looks like ownership may continue after launch. If you can clarify that boundary, I'd appreciate it. No worries if you're not the right person.
Adds relevant context instead of “bumping this.” Our suggested default is one follow-up after roughly a week, then stop unless invited to continue. That is etiquette guidance, not a platform rule.
Thanks, that distinction helps. You mentioned stakeholder handoffs are the hard part. Here's a one-page example of how I mapped ownership on a past project, with private details removed. Does this look relevant to the challenge you described?
Send the example only when sharing it fits the exchange. Demonstrate that you listened; do not attach a large unsolicited work sample.
Thank you for the perspective. I've decided the role is more technical than my current experience supports, so I'm focusing on operations positions closer to my background. Your advice helped me make that call.
A conversation can succeed without producing an interview. A sincere update leaves less work for the recipient than another request.
What makes a message harder to answer
- “Can I pick your brain?” without a subject or specific question.
- A referral request for five unrelated roles.
- A list of achievements with no connection to the recipient's work.
- Invented mutual interests, invented compliments or claims you have followed someone for years.
- Repeated messages, channel-hopping or manufactured urgency after silence.
If someone says no, thank them and stop. If they invite a later follow-up, record that context rather than starting a generic sequence. If they answer a question, respond to the answer before asking for a call. Good messaging is not just the opening sentence; it is how you behave once another person gives you their attention.
When the exchange produces a credible reason for an endorsement, the next step may be a referral. That requires more than good copy. See how a cold message can become a referral for the evidence and permission involved.
Sources & further reading
Sources checked October 21, 2026. Study dates and limitations are noted in the article; organizer pages can change.