InMail costs credits, so every one should earn a reply. These are short, specific and built around one reason to write now, with subject lines that look like a person wrote them.
15 templatesSubject lines includedUpdated October 2026
A LinkedIn InMail that gets a reply is short (three to five sentences), opens with the specific reason you're writing to this person now, names one problem they likely have, offers one piece of proof, and ends with an easy question. The subject line should name the topic plainly. Save InMail for people a connection request won't reach.
Use it when a request won't do. Senior people, time-sensitive reasons, or someone who ignored a well-chosen request.
Lead with why them, why now. A trigger, a post, a shared contact. Put it in the first sentence.
Three to five sentences. InMail is read on phones too.
One easy question. "Worth a look?" or "Is this on your list this quarter?"
Check for Open Profile first. Some members can be messaged without spending a credit.
The 15 templates
Replace everything in {braces}. Use them as they are, or as a starting point in your own voice.
Senior buyers
Brief and respectful
Subjectquestion about {area} at {company}
Hi {first name}, I know your inbox is full, so I'll be brief. {Company} is {trigger}, and teams at that stage usually run into {problem}. We helped {customer}{result}. Would a 15-minute walkthrough help, or is someone on your team closer to this?
Peer reference
Subjecthow {peer company} handled {topic}
Hi {first name}, {peer company} faced the same {problem} as they grew past {milestone}. They fixed it by {one-line approach} and saw {result}. Happy to share the details if it's on your radar.
Strategic idea
Subjectan idea for {initiative}
Hi {first name}, saw {company} is {initiative}. One thing that helped similar teams: {specific idea}. If it's useful, I can send a short note on how others set it up.
Trigger events
New role
Subjectyour first 90 days at {company}
Hi {first name}, congratulations on the new role. New {role}s often inherit {common problem}. We put together a short checklist from {number} teams who solved it. Want it? No strings.
Hiring
Subjectyour {role} hire
Hi {first name}, saw you're hiring a {role}, which usually means {work} is piling up. While you hire, {product} can take on {task}. Open to a quick look?
Launch or funding
Subjectcongratulations on {news}
Hi {first name}, congratulations on {news}. The next few months usually bring {growth problem}. {Customer} handled it without adding headcount; happy to share how.
Shared context
Same event
Subject{event}
Hi {first name}, we were both at {event}. Your point about {topic} stuck with me, because we see {related problem} with {type of customer}. Worth comparing notes for 15 minutes?
Mutual connection
Subject{mutual name} suggested I write
Hi {first name}, {mutual name} mentioned you're working on {topic}. We helped {customer} with something similar. Happy to share what worked, if useful.
Their post
Subjectyour post on {topic}
Hi {first name}, your post on {topic} described a problem we hear weekly from {type of customer}. Curious: did you find a fix for {specific detail}?
After an ignored connection request
Second attempt
Subject{topic}, briefly
Hi {first name}, I sent a connection request a couple of weeks ago, so this is my one follow-up. {Reason it's relevant now}. If it's not a priority, no reply needed.
Different angle
Subjectone idea for {company}
Hi {first name}, a quick idea instead of a request: {specific suggestion}. Teams that tried it saw {result}. Happy to explain if it's useful.
Partnerships
Overlapping customers
Subjectour customers overlap
Hi {first name}, we both sell to {type of customer} without competing. Our customers often ask about {their service}. Worth a call to see if there's something useful we could do together?
Integration
Subject{your product} and {their product}
Hi {first name}, {your product} and {their product} cover two halves of the same job for {type of customer}. A few of our customers use both. Would you be open to exploring an integration?
Following up an InMail
Useful nudge
SubjectRe: {original subject}
Hi {first name}, one more thing that might help with {topic}: {resource or idea}. No reply needed if the timing's wrong.
Closing the loop
Subjectclosing the loop
Hi {first name}, I won't keep messaging. If {problem} becomes a priority, I'm here, and I'll keep following your posts either way.
Siela AI's LinkedIn outreach agent finds the right people, writes messages like these for each one and sends them from your own accounts, within the daily limits you set.
Siela · NorthwindExample
You
You 9:41
Message the five heads of operations who didn't accept last month.
AI SDR 9:41
The AI SDR doesn't use InMail credits. These five fit, so each gets a connection request with a short note about why you're reaching out, and I pick up from it when they accept.
AI SDRToday
5 connection requests today
FromYour LinkedIn account
UsesNo InMail credits
ThenPicks up from the note when they accept
Questions
How do I write a good LinkedIn InMail?
Keep it to three to five sentences: why you're writing to them now, the problem they likely have, one piece of proof, and one easy question. Use a plain subject line that names the topic.
Is InMail better than a connection request?
Not usually. A connection request is free and opens an ongoing relationship. InMail is worth a credit for senior or hard-to-reach people and time-sensitive reasons.
Do I get InMail credits back?
LinkedIn returns the credit when your InMail gets a reply within its stated window, so well-targeted InMails cost less than they seem.
Can I message someone on LinkedIn without InMail?
Yes, if they're a connection, or if they've turned on Open Profile, which lets anyone message them without a credit.
Can Siela send InMails for me?
No. Siela's AI SDR reaches people with connection requests and messages from your own LinkedIn account, which needs no Premium or InMail credits. Use these templates when you send InMail yourself.