How to Write a Warm Introduction Request That Actually Gets Forwarded

Most intro requests fail not because the connector won't help, but because they're written in a way that makes helping feel like work. Here's the format that gets results.

Glowing cream broadsheet letter with amber network nodes emerging from it on dark navy grid representing how to write a warm intro request — Scout editorial illustration

Most warm introduction requests fail not because the connector doesn't want to help — it's because the request is written in a way that makes helping feel like work.

The connector has to figure out who you want to meet, why the meeting is relevant, what to say when they introduce you, and whether this is worth the social capital. If any of those steps require effort on their part, the request goes to the bottom of the to-do list and stays there.

Frequently Asked Questions

Why do most warm introduction requests fail?
Not because connectors won't help — they fail because the request makes helping feel like work. The connector has to figure out context, relevance, and what to say. When you do that work for them upfront, acceptance rates jump to 65-75%.
What should a warm intro request email include?
Three things: (1) the specific person you want to meet, (2) a one-sentence reason the intro is mutually relevant, and (3) a ready-to-forward draft intro they can send with no edits. The goal is to make saying yes take 10 seconds.
What is the acceptance rate for a well-written intro request?
A well-structured introduction request that includes a pre-drafted forwarding email sees connector acceptance rates of 65-75%. Poorly written requests that require the connector to do the work see rates under 20%.
How long should a warm introduction request be?
The request to your connector should be under 100 words. The pre-drafted intro they forward should be 3-5 sentences. Brevity signals you respect their time and have thought this through carefully.