Getting a reply to a networking email isn’t easy. Many templates are structured around what the sender needs rather than what would give the recipient a reason to respond. That problem is often why emails go unanswered, and it is the thing worth fixing before reaching for a template.
A networking email template works when it's built around a specific reference, a single clear ask, and a reason for the recipient to respond. The templates here cover common scenarios: cold outreach, post-event follow-up, reconnecting with a lapsed contact, referral requests, mutual connection introductions, call requests, follow-up after no reply, and LinkedIn. According to Fyxer's Admin Burden Index 2026, a survey of 5,000 UK and US office workers, email is the number-one daily time-waster; meaning every email you send is competing for attention from a very crowded inbox.
For sales reps and account managers sending outreach at volume, the overhead of networking well for every contact is where most people get stuck.
Networking email templates for different scenarios
The templates below each cover a distinct scenario. Pick the one that fits your situation, fill in the specific reference and adjust the tone to match how you normally write. The structure handles the rest.
1. Cold outreach to someone you don't know
When reaching out to someone with no prior connection, the specific reference carries more weight than in any other scenario. Without it, there is little reason for the recipient to engage.
The structure of a networking email: a specific reference, one sentence of context about who you are, a bounded ask, and an explicit no-obligation line so the recipient can decline without awkwardness.
Subject: Question about [specific thing they've worked on or published]
Hi [Name],
I came across [specific article / talk / project] recently. Your point about [specific detail] shifted how I've been thinking about [relevant topic].
I'm a [your role] at [company], and [one sentence on the connection between their work and what you're working on]. I'd welcome the chance to ask you one question about [specific topic], if you have fifteen minutes sometime in the next few weeks.
No obligation either way. Happy to share what I'm working on if it's useful context.
Thanks, [Your name]
2. Following up after meeting someone
Send within 24 hours of meeting, ideally the same day. The longer the gap, the more context the email needs to include.
Keep it short. The introduction happened in person; this email just maintains the connection.
Subject: Good to meet you at [event]
Hi [Name],
Really good to meet you at [event] yesterday. [One genuine, specific thing from the conversation: not generic praise].
I'd like to stay in touch. [Optional: one thing you mentioned you'd follow up on, such as a link, an article, or a connection].
Let me know if you'd ever want to continue the conversation properly.
[Your name]
3. Reconnecting with a lapsed contact
Opening with an apology for the time elapsed tends to make the email about the gap rather than the reconnection. A brief acknowledgment works, but there is no need to dwell on it.
The reference to something specific from the past relationship is what distinguishes this from a generic check-in.
Subject: Catching up
Hi [Name],
It's been a while. I've been thinking about [specific thing you discussed or worked on together], and it reminded me I hadn't been in touch.
[One sentence on what you're working on now]. I'd genuinely like to hear what you've been up to. Are you still at [company]?
If you're up for a brief call sometime, I'd welcome it. No agenda, just catching up.
[Your name]
4. Asking for a referral or introduction
This is the scenario where making it easy to decline matters as much as making it easy to say yes.
Giving the recipient an easy out tends to make the conversation more likely to happen, not less. It reduces the social pressure of saying no, which means people are more willing to engage.
Subject: A small favour
Hi [Name],
I hope things are good with you. I'm currently [brief context, such as exploring a move, working on a new project, or looking for advisors in a specific area].
I noticed you know [person's name] at [company]. If you think it would be appropriate, I'd love an introduction. I'm specifically interested in [what you want to discuss with them and why].
Completely understand if it doesn't feel right, and happy to share more context if that helps you decide.
Thanks either way, [Your name]
5. Reaching out via a mutual connection
If someone has offered to make an introduction, use their name in the subject line. If you're reaching out because of a shared contact without a formal introduction, mention the connection in the first sentence.
With a mutual contact named in the subject, the email itself just needs to be clear and brief.
Subject: [Mutual name] suggested I get in touch
Hi [Name],
[Mutual name] mentioned you might be a good person to speak with about [specific topic]. [One sentence on what you're working on and why it's relevant].
Would you be open to a brief call? Fifteen minutes would be plenty, and I'm happy to work around your schedule.
Thanks, [Your name]
6. Requesting a brief call or informational conversation
This template is for situations where you want to ask for someone's time directly, without a shared connection or a specific project hook. The key is to be clear about why them specifically, and to make the time commitment feel genuinely light.
Committing to keeping it focused and offering to share a summary both signal that you respect the recipient's time. That tends to make people more willing to agree to the call.
Subject: 15 minutes re: [specific topic]
Hi [Name],
My name is [your name]. I'm a [role] at [company], and I'm currently [one sentence on what you're working on].
I came across your [work / writing / role] in the context of [topic], and I'd welcome 15 minutes to hear your perspective on [specific question or area].
I'll keep it focused and follow up with a short summary of anything useful that comes out of it. Would any time in the next two weeks work?
Thanks, [Your name]
7. Following up after no reply
A single follow-up is standard and expected. Two is acceptable. Three or more starts to feel like pressure. The follow-up email should be short, presume good faith, and leave the door open without pushing.
A short follow-up is less likely to feel like pressure than one that restates the full original request.
Subject: Re: [original subject]
Hi [Name],
Just following up on the below in case it got buried. Happy to hear back whenever suits you, and no worries if the timing isn't right.
[Your name]
8. LinkedIn networking message
The character limit on LinkedIn connection requests keeps things short by necessity. A specific reference and a brief context line is usually enough.
If you're sending a message after already being connected, slightly more space is available but the same principles apply: specific reference, one-sentence context, clear but low-pressure ask.
Hi [Name], I came across your piece on [specific topic] and found your point about [specific detail] genuinely interesting. I'm working on something related from the [your angle] side. Would love to connect.
What every good networking email has in common
The emails that get replies tend to share four characteristics, regardless of the specific scenario.
A reason specific enough to be credible: The most common problem in networking emails is a reason that could apply to anyone. "I admire your work" or "I've been following your career" are phrases that take no research to write, and recipients tend to read them accordingly. A reference to something specific you actually read or attended is what tells the recipient this email was written for them.
Something of value before the ask: The instinct is to get to the request quickly. Emails that get replies more often lead with something useful to the recipient first: an observation relevant to their work, a piece of information, a specific reference that shows genuine attention. That gives the person a reason to engage before having to decide whether to help.
A single, specific ask: Emails that ask for multiple things, or that leave the next step unclear, tend to get deferred. A bounded request is easier to act on and easier to decline if the timing is wrong. For most first outreach, the goal is a reply, not a commitment.
A subject line that reflects the email's content: The subject line is what the recipient reads before deciding whether to open the email. Ones that reference a shared connection or something specific about the recipient tend to perform better than generic options. "[Mutual name] suggested I reach out" is the most reliable formulation when a warm connection exists. For cold outreach, something direct works better than something clever: "Question about your work on [topic]" or "Met you at [event] last week".
The patterns that make networking emails not work
Common problems in networking emails often come from what is included rather than what is missing.
Opening with your own credentials: "I'm a senior manager at [company] with ten years of experience in [field]" as an opening line is about you, not the recipient. It positions the email as a pitch rather than an introduction. Background information is useful once there's a reason for the person to want it. Lead with what's relevant to them.
The vague flattery opener: "I've long admired your work" or "I've been a huge fan for years" are easy to write and easy to discard. Admiration expressed in general terms reads as a formula. Admiration expressed through reference to something specific reads as genuine.
Asking for too much too soon: A cold networking email that asks for a referral, a job recommendation, or an hour of someone's time is asking for a level of investment that the relationship hasn't established yet. The goal of most first outreach should be a reply. Work toward the bigger ask across a relationship, not in one email.
Over-explaining: A networking email that runs to four or five paragraphs is asking the recipient to do significant reading before they can evaluate whether they want to respond. Shorter emails tend to convert better not because people are lazy readers but because a concise email signals clarity of purpose. If you know what you want and why, you can usually say it in 100 words.
Subject lines that read like cold outreach: "Quick question" works as a subject line when it follows a specific reference. On its own it reads like a sales email and gets treated accordingly. "Following up" as a subject line tells the recipient nothing. "Re: [previous subject line]" is better for a follow-up than anything invented from scratch.
The subject line is what gets the email opened, and a few consistent patterns work across scenarios.
“[Mutual name] suggested I reach out”: When a warm introduction exists, using the mutual contact's name in the subject line tends to produce significantly higher open rates than other options.
“Met you at [event]”: Works well for immediate post-event follow-up. The shared experience is the reference, and there's no ambiguity about context.
“Question about [specific topic]”: For cold outreach where you have a genuine specific question. Avoids the generic quality of "quick question" while still keeping the ask clear.
“Re: [Original subject]”: For follow-ups. Keeps the thread visible and avoids the slightly pushy quality of inventing a new subject line.
“[Their name] / [your name] Re: [Shared context]”: Useful when the connection between two people is the substance of the email. Slightly more formal but appropriate for certain professional contexts.
Subject lines to avoid: "Following up", "Checking in", "Quick question" (without a specific question that follows), "[Your company] x [their company]" (reads like a sales outreach), and anything with an exclamation mark.
The networking email template that works is the one adapted to a specific person, not copied and sent in bulk. The templates here are structured to make that adaptation straightforward: each one has a slot for the specific reference, the personal detail, the concrete ask. Fill those slots with real information and the email will feel like it was written for the person rather than at them.
For professionals who do a lot of email outreach, the limiting factor is rarely knowing what to write. Rather, it is the time and friction of writing it well, repeatedly, for different people and contexts. The framework above handles the what. The work of the specific reference is still yours to do.
Using AI to draft networking emails
The templates above are starting points. What makes any networking email worth sending is the specific detail: the exact reference that shows you read something, the precise ask that reflects what you actually need. That specificity can't be automated, but the drafting around it can.
Office workers receive an average of 29 emails per day requiring a response, according to the Fyxer Admin Burden Index 2026. That's the volume your networking emails are competing against. Getting the structure right isn't a nice-to-have.
The most productive use of AI in networking outreach is as a first-draft generator, not a replacement for thinking. Feed it the specific detail you want to include, the scenario, the tone you want to strike, and let it produce a draft. The draft is rarely the final version, but it breaks the blank-screen problem and gives you something to react to rather than construct from nothing.
The risk is using AI to generate the specific references themselves. A fabricated detail, a misattributed quote from someone's article, a claim about their work that's slightly wrong, is worse than no reference at all. It signals that the email wasn't genuine. The research has to be real; the drafting can be assisted.
For professionals sending outreach at volume, the friction of moving between researching a contact, drafting a message, and sending adds up across dozens of emails a week. The most effective tools for this are ones that live inside the email client and generate drafts in the user's own voice, so the specific context you've researched doesn't have to be re-entered somewhere else.
The networking email that gets a reply
The framework is straightforward. The hard part is finding the specific detail for each person, and then making time to write it well for every contact. For sales reps and account managers managing a full pipeline, that's where most of the overhead lives. Getting the structure right frees you up to spend that time on the part that actually requires you: the research.
Networking emails FAQs
How long should a networking email be?
Under 150 words for cold outreach. A post-event follow-up can be shorter still: three or four sentences is enough when the relationship has already been established in person. Longer emails signal that you have not thought carefully about what you actually want, or that you are trying to pre-empt objections rather than letting the person decide. Either way they tend to convert worse.
What is the best time to send a networking email?
Tuesday through Thursday morning, roughly 9 to 11am in the recipient's time zone, tends to produce higher open rates across email types, according to research by MailerLite. The difference is real but not dramatic. A well-written email sent on a Friday afternoon will outperform a weak email sent on a Tuesday morning. Timing is a marginal variable, not a primary one.
How many times should you follow up on a networking email?
Once, after 5 to 7 days. A second follow-up is acceptable if you have a genuine reason to resurface the message, but it should be even shorter than the first and should make it easy for the person to decline. Beyond two follow-ups, the dynamic shifts from networking to pressure, and most people will stop engaging entirely.
Should you personalize every networking email?
The specific reference is not optional. Without it, the email reads as a template, and most people either delete template emails or ignore them. The personalization does not need to be elaborate: a single sentence that references something real about the recipient's work or background is enough. That sentence is what separates a networking email that gets a reply from one that doesn't.
How do you write a networking email to someone you don't know?
The same way you'd write one to someone you do know, except the reference has to work harder because there's no relationship to rely on. Find something specific: an article they wrote, a talk they gave, a project they worked on, a company they built. Reference it precisely, explain in one sentence why it's relevant to you, and make a small bounded ask. The specificity is what makes a cold networking email read as written for the person rather than sent indiscriminately.
