Warm Introduction Email: Templates and Permission Checks

A warm introduction connects two people through someone they already know. A useful introduction email explains why the conversation could help, gives the connector enough context to decide and leaves the recipient free to decline.

Before writing it, establish whether your connector actually knows the person and feels comfortable approaching them. A visible connection gives you a possible route to investigate. It doesn't establish a current relationship or permission to use it.

That distinction has come up in our conversations about consulting business development. A contact record can look promising while the person who owns the relationship has a very different view. The email should follow that conversation.

This guide gives you the email sequence, a permission check and an illustrative example.

A warm introduction email template for each step

Use these templates as a sequence. Check with the connector first, give them a note they can forward, and let them ask whether the recipient wants the introduction. An agreement to consider the request isn't an agreement to send it.

Replace every bracketed field. If you can't explain the relevance in one sentence, finish your account research brief before requesting an introduction.

1. Ask the connector privately

Subject: Do you know [recipient] well enough for an introduction?

Hi [connector],

Do you know [recipient] at [company] well enough to consider an introduction?

I help [type of team] with [specific work]. [Verified context] made me think a conversation about [specific question] could be relevant, although I don't know whether it's a current priority for them.

If you're comfortable, I can send a short note for you to share. If you don't know them well, or the timing feels wrong, no problem.

Thanks, [your name]

The question lets the connector correct your understanding before their name becomes part of your approach. Avoid attaching a long deck or asking them to compose the explanation for you.

2. Supply a forwardable note

Subject: Introduction request: [your name] / [specific topic]

Hi [connector],

Here's a note you can forward if it fits. Please edit anything you'd prefer to describe differently.

I'm [name], [role] at [firm]. We help [type of team] with [specific task]. I noticed [verified public fact] and wanted to ask how [recipient's team] is approaching [relevant question].

If that question is on their agenda, I'd welcome a short conversation. If another person owns it, or it isn't a priority, I understand.

[Name, role and one relevant link]

Keep the claim about your work within what you can substantiate. The connector should be able to forward the note without endorsing capabilities they've never seen.

3. Let the connector ask for an opt-in

The connector can adapt this message before sharing contact details or adding both people to a thread:

Subject: Would this introduction be useful?

Hi [recipient],

[Requester], whom I know through [accurate relationship context], asked whether I'd introduce you. They work on [specific task] and would like to discuss [question]. Their note is below.

Would you like me to connect you? No problem if it's outside your remit or the timing isn't right.

The recipient can accept with a boundary:

Thanks for checking. Yes, please introduce us. A conversation about [topic] would be useful. [Optional limit: I'm exploring the issue, rather than choosing a provider yet.]

Or decline without needing to explain:

Thanks for thinking of me. Please hold the introduction for now.

4. Introduce both people after they agree

Once both people agree, the connector can start a shared thread with this introduction email:

Subject: Introduction: [requester] / [recipient]

Hi [requester] and [recipient],

Thanks for agreeing to connect about [specific topic].

[Requester] works on [specific task]. I know them through [accurate relationship context]. [Recipient] is [confirmed role] at [company] and agreed that a conversation about [question] could be useful.

I'll leave you to decide the next step. Let me know if more context from me would help.

Keep the introduction within the scope both people accepted. Agreement to an exploratory conversation doesn't imply that either person has approved a proposal or purchase.

Check the relationship before requesting the introduction

Work through these checks in order. A positive answer to one doesn't answer the next.

Use a relationship mapping template if several colleagues could provide a route. Record the evidence and who confirmed it. A shared employer, an imported contact or a social connection should remain unconfirmed until someone can explain the relationship.

Also ask whether the account already has an owner inside your firm. A colleague may be protecting a sensitive discussion or coordinating another approach. A second introduction can complicate that work even when everyone means well.

A worked example: when the apparent connection is weak

Illustrative scenario: A consultant helps businesses integrate finance processes after acquisitions. A target company announces an acquisition, and a colleague appears connected to its finance director.

The first draft of the request says: “You know their finance director. Can you introduce me to discuss the integration?”

That sentence assumes both a usable relationship and relevant work still available. The consultant checks first. The colleague explains that they met once at an event and haven't spoken since. They do, however, know the person leading the company's finance operations team.

The consultant revises the request:

Would you be comfortable asking your finance operations contact whether a conversation about reporting integration would be useful? I don't know whether they've already assigned the work. I'm happy to send a short note, and there's no need to ask if you think it's poorly timed.

If the colleague agrees, they seek permission from their contact before connecting anyone. The introduction may lead to a conversation, a different owner or a clear “already covered.” Each answer is more useful than a thread started on an assumption.

What a warm referral should and shouldn't imply

A connector can truthfully say how they know you. If they've worked with you, they can describe that experience within any confidentiality limits. If they only know you through a professional community, the introduction should say so.

Don't draft “I highly recommend their work” for someone who hasn't used it. Don't put the connector's name in a direct email as implied approval when they only agreed to review your request.

If there's no confirmed route, you can decide whether a direct approach is appropriate. Describe it honestly. Borrowed familiarity isn't a substitute for a relevant reason to contact someone.

After the introduction

Reply with thanks and restate the specific question. Avoid turning a small introduction into an unsolicited proposal or calendar invitation.

Ask how the connector prefers to leave the thread, then handle the conversation yourself. Update them later with a brief outcome if appropriate. You can acknowledge their help without forwarding confidential details from the discussion.

If the recipient doesn't respond, don't recruit several colleagues to chase the same person. Reconsider the timing and relevance before following up. Permission for one introduction doesn't authorize an open-ended outreach sequence.

Common questions about introduction emails

How long should a warm introduction email be?

Make it short enough for the connector to assess without opening another document. Include the accurate relationship context, the reason for the conversation and a clear request. The templates above provide a starting point, rather than a universal word limit.

Is a referral email template enough?

A referral email template helps with wording after you've established familiarity, relevance and permission. It can't tell you whether the relationship is current or whether the recipient wants the conversation. Keep those checks outside the drafting step.

What if the connector declines?

Thank them and leave the request there. If they volunteer another route, check that route on its own terms. A decline may reflect timing, trust or context you don't know, and the connector doesn't owe you those details.

For teams coordinating introductions across colleagues, alkemy's Warm Intros is the relevant product area to explore. Keep the human confirmation in the process: someone still needs to decide whether this relationship is appropriate for this request.