Most InMail goes ignored because senders default to longer, more formal copy than connection requests. That's backwards. InMail should be shorter and more direct than a connection note — the prospect granted you the inbox; honor it by being concise.
Template 1 — Open Profile / no-credit InMail
Context: Reaching a prospect with Open Profile (free InMail). Volume play.
Hi [name] — quick note since you're an Open Profile member. [One specific reason you're reaching out tied to their work]. Want me to share a one-pager, or talk more later?
Use when: Open Profile prospects. Free, so volume tolerance is higher.
Expected reply rate: 8–14% reply rate. Lower than connection-note reply rate but free, so the math works.
Template 2 — Subject-line-driven cold InMail
Context: When you only have InMail credits and need to maximize conversion.
Subject: [3-5 word subject that's specific, not 'Quick question']
[name] — [one specific reference to their work]. [One sentence on why I'm reaching out]. [One sentence on the ask]. Worth a quick reply?
Use when: High-value prospects who didn't accept the connection request.
Expected reply rate: 12–20% reply rate. Subject line drives most of the difference.
Template 3 — Question-only InMail
Context: Lead with a question, no pitch.
Hi [name] — single question: [specific question tied to their work]. Trying to learn from operators in [their role] before going deeper on [domain]. Open to a one-sentence reply or a 15-min call?
Use when: When you can ask a question that flatters their expertise.
Expected reply rate: 20–30% reply rate. Questions disarm; they don't trigger 'sales' defenses.
Template 4 — Mutual-connection InMail
Context: Use the mutual to break in via InMail.
[name] — [mutual] suggested I reach out. They thought you'd be the right person for [specific thing]. Connecting first to understand whether the timing/context fits.
Use when: Real mutual referral, with the mutual's blessing.
Expected reply rate: 30–45% reply rate. Mutual referral via InMail performs nearly as well as via connection note.
Template 5 — Trigger-event InMail
Context: Recent funding, leadership change, or product launch within 30 days.
Hi [name] — saw [trigger event]. Reaching out because [specific implication for their team]. We work with [similar accounts] on exactly this. Worth a quick chat?
Use when: Within 30 days of a real public trigger.
Expected reply rate: 15–25% reply rate. Trigger-event timing makes the InMail feel relevant.
How to use these with AI personalization
These templates are scaffolds, not scripts. The strongest version of each comes from AI personalization that fills in the [specific reference] placeholders with real, prospect-specific details. Most of the reply-rate variance comes from the quality of those references — mail-merge filling them with generic strings underperforms hand-written, which AI synthesis can match at scale.
See how AI personalization works in Infonet.
Run these templates with Infonet
Upload these as your starting templates, configure your voice library, and AI personalization handles the per-prospect references. Free 14-day trial.
Start free trial