How to Give a Warm Introduction: A Step-by-Step Guide for Connectors

Before you write anything, ask both people separately whether they are open to the introduction. This is the double opt-in, a practice widely recognised in professional networking as the minimum standard of care for a connector. It protects both parties and it protects your relationship with both of them. The mechanic is straightforward. Reach out to the person who is going to receive the introduction first: "I know someone I think would be genuinely useful for you to meet: [one-sentence description of who they are and why the connection matters]. Are you open to an introduction?" If they say yes, do the same with the person making the request: confirm they still want the introduction and give them one sentence on the recipient’s context. Both sides confirmed? Now you write the intro. If either side declines, do not push, and do not reveal that they declined to the other party. The failure mode that destroys connector reputation is making introductions without checking first. The person who receives an introduction they did not ask for and did not want is unlikely to respond positively. And they will remember that you put them in that position. The double opt-in takes two short messages and removes this risk entirely.

The introduction email itself has five components, in order. First, a subject line that names both people explicitly (see the subject line patterns below). Second, a mutual context hook: one sentence that explains why you know both of them and why you are making this introduction now. Third, a blurb for person A: who person B is, their relevant role or context, and why this connection is useful for person A specifically. Fourth, a blurb for person B: the same for person A (who person A is, why this connection matters for them). Fifth, an explicit hand-off: one sentence that passes the conversation to both parties and steps you out of the thread. The blurbs are the most important part and the most commonly botched. Each blurb should be two to three sentences maximum, specific enough to give the recipient something to say in their first response, and framed around what is useful for the reader (not around what is impressive about the person being introduced). Avoid superlatives ("he is the best person I know in this space"). They read as social pressure, not useful context. Be specific instead: title, relevant experience, and the specific reason the connection makes sense.

Three subject line patterns work reliably for warm introduction emails. The first is the explicit name format: "[Person A], meet [Person B]: [one shared context]." For example: "Julia, meet Mark: both working on enterprise sales motion." The second is the topic format: "Connecting you both on [shared topic]", useful when the connection is more situational than role-based. The third is the meeting-forward format: "[Person A] / [Person B]: worth a conversation." Use the explicit name format as the default; it is the clearest for recipients who scan subject lines quickly. The topic format works when the shared context is the most useful framing and the names alone would not signal relevance. Avoid vague subject lines ("Thought you two should meet"). They do not give the recipient enough to act on before opening the email, and they perform poorly when someone is triaging a busy inbox. The introduction email will often be the first email one or both recipients receives from an unknown address (if you are making the introduction from a different email than they know you from); the subject line is what determines whether it gets opened immediately or deferred.

After you send the introduction email to both parties simultaneously, one question arises: should you CC or BCC each person? The standard approach is to CC both people on a single email so that each recipient can see the other’s email address and the full introduction context in one thread. This is the most common format because it gives both parties everything they need to take the conversation forward without involving you. The BCC approach is used in one specific circumstance: when one party has asked you to facilitate a cold introduction to someone who has not yet confirmed they want the connection. In this case, you can send the introduction email to the recipient with the requester BCC’d, giving the recipient the option to ignore without social pressure. This is a softer version of the introduction, more appropriate for cold introductions, and avoids putting the recipient in the position of declining in front of the person who asked for the introduction. For most warm introductions where both sides have confirmed they want to meet (i.e., where you have done the double opt-in), CC both parties on the same email.

Once you have made the introduction, your role as connector is largely complete. Give both parties five business days to connect. If you see or hear that the conversation has started, a brief note is sufficient: "Glad you two connected." If after five days there has been no visible response (no reply-all, no message to you), you can nudge the person who asked for the introduction: "Just checking in. Did you manage to connect with [Name]?" This gives the requester the cue to follow up directly with the recipient without requiring you to follow up with the recipient on their behalf, which would feel like pressure. One nudge is the maximum. If the connection does not happen after the nudge, it means either the timing was wrong or the fit was less strong than expected. Do not send multiple follow-ups or check in with the recipient to ask why they have not responded; that would undermine the trust both parties have placed in you as the connector.

The most common and most damaging connector mistake is making an introduction that one or both parties did not ask for and did not confirm they wanted. It puts both recipients in an awkward position: they either have to engage with a conversation they did not invite, or they have to ignore an email from someone they respect (you), which also feels uncomfortable. And when the recipient does not respond, the person who asked for the introduction often interprets the silence as a reflection on them, when in fact it is a reflection on the introduction not being welcome. The fix is the double opt-in, and it takes two messages. There is no introduction urgent enough to skip it.

Many introduction emails open with social context, background, and pleasantries before getting to the actual connection. This is a mistake. Both recipients are likely busy; the most useful thing you can do is get to the point immediately. The mutual context hook (why you know both of them) should take one sentence, and the blurbs should follow directly. A well-structured introduction email can be read and understood in under thirty seconds. An email that takes three paragraphs to explain why the connector knows both parties before explaining who the people are will be deferred, misunderstood, or ignored. If you feel the need to write a long preamble, it is usually a signal that you have not been specific enough about why the connection makes sense, and the fix is to sharpen the blurbs, not to add more context around them.

The introduction email should include a clear signal of what the requester is looking for: not a hard ask (that is for them to make in their follow-up message), but enough context that the recipient knows what kind of conversation is being proposed. "Julia is building out her enterprise sales motion and would love to get your perspective on how you approached it at [Company]" is useful context. "Julia would love to meet you" is not. The difference is that the first version gives the recipient enough to decide whether they can be helpful; the second gives them nothing to respond to. The blurb for the requester should always include the specific topic, problem, or question that makes the connection relevant, so the recipient can say yes or no with confidence, and so the first conversation has a clear starting point rather than beginning with two people figuring out why they are talking.

The temptation when introducing someone you respect is to lead with their credentials and accomplishments: their title, their company, their track record. This is natural but often counterproductive. A blurb that lists what is impressive about someone does not help the recipient know whether the conversation will be useful for them; it creates social pressure to engage because the person sounds important, not because the connection is relevant. The blurb should answer one question for each recipient: why is this specific person worth talking to for you, right now? That question is almost always answered by the problem the requester is trying to solve or the perspective the recipient can uniquely offer, not by the list of credentials that makes the person sound impressive in the abstract.

Short. A well-written introduction email is five to eight sentences: a subject line that names both parties, one sentence of mutual context, two to three sentences per blurb, and one sentence of hand-off. Total reading time should be under thirty seconds. If you find yourself writing more than that, you are probably explaining the connection rather than showing it. The connection itself should be self-evident from the blurbs. The one exception is when the context genuinely requires more background, such as a highly technical connection where the recipient needs to understand the requester’s problem to know whether they can help. Even then, aim for one short paragraph per person, not two.

Generally not. Your role is to make the introduction and step out. The explicit hand-off at the end of the email ("I’ll leave you both to take it from here") signals that both parties should reply to each other directly, not to you. Staying in the thread creates confusion about who the conversation is between and puts you in the position of managing a conversation that should belong to both of them. The exception is when you have a reason to be involved in the conversation itself (for example, if you are a mutual partner in a project the introduction is facilitating). Otherwise, step out and let the introduction do its work.

Match the channel to the person who is harder to reach. If one party primarily uses LinkedIn messaging and rarely checks email, make the introduction via LinkedIn DM and either CC the other party’s preferred contact method or ask the LinkedIn party to connect with them directly once they have confirmed interest. The mechanics of the double opt-in and the five-element formula still apply. The channel is just different. For introductions between people who primarily use WhatsApp or iMessage, a brief text introduction is appropriate, though you lose the ability to CC and must do two separate messages to facilitate the connection.

Ask the person you do know well to give you a sentence about what the other person should know. If the requester is asking you to introduce them to someone you know less well, ask the requester to write a one-sentence description of themselves that you can include in the blurb, or review their LinkedIn profile and summarise their most relevant context yourself. The key information is their current role, the relevant experience or perspective they bring to this connection, and the specific reason this introduction makes sense for the other party. You do not need a deep relationship with someone to write a useful blurb; you need to know the specific reason the connection is worth making.

No. Each introduction should be a separate email between three parties: you, person A, and person B. Grouping multiple introductions into a single email creates confusion about who is being introduced to whom, makes the blurbs harder to write clearly, and puts recipients in the awkward position of knowing about each other’s introduction context. Make each introduction separately, even if you are facilitating several introductions for the same person in the same week. The exception is a group introduction, where three or more people with a shared context genuinely benefit from a group thread, but this is a different thing from multiple separate introductions combined for efficiency.

LetsBridge handles the double opt-in mechanics programmatically: when someone requests an introduction through the platform, both the requester and the prospective connector receive a structured prompt that confirms whether they are open to the connection before any introduction is sent. For connectors who agree to make an introduction, the platform provides the context needed for the blurbs automatically: the requester’s purpose, the specific reason this connection was requested, and the relevant background from both profiles. This removes the most friction-prone step for connectors (finding out what to say) and ensures that every introduction made through the platform has been opted into by both sides.