Skip to content

Introduction skills

Introduction Etiquette Across Platforms

A warm introduction that works perfectly in email can feel presumptuous as a LinkedIn connection request, disappear in a Slack channel, or overstep on WhatsApp. The right format depends on the platform, and the platform depends on the relationship. Here is how the etiquette changes across the five primary introduction contexts.

Most warm introduction guidance treats the introduction brief as a single format (usually email) and focuses on what to say rather than where to say it. But a warm introduction does not exist independently of the channel through which it is delivered. The trust level, the character limits, the social visibility, and the implied intimacy of the platform all shape how an introduction lands and whether it converts into an actual connection.

Two rules apply across every platform: get consent from both parties before making the introduction (double opt-in), and tell the connector what happened after (loop-close). Everything else adapts to the platform.

Five introduction contexts and what changes in each

Email: the default format and why it earns that status

Email is the baseline format for warm introductions for two structural reasons: it has no character limit, so the connector can provide the full context that makes an introduction genuinely useful, and it is forwardable, which means the recipient can pass it to an assistant, a colleague, or a future self without the conversation being lost in a messaging app. The mechanics of an email warm introduction are well-established: the connector sends a single email that addresses both parties directly, explains the connection to each and why the meeting would be valuable for both, and usually makes a low-friction ask (a short call, a coffee, a brief reply if interest is there). The BCC variant (the connector emails one party, BCCs the other, and invites the introduced party to "take it from here") is common in B2B contexts where the connector wants to make the connection without being copied on all subsequent correspondence. What email does not do: it does not provide a social proof signal before the introduction lands, because the recipient cannot see anything about you before opening the message. This is why a strong introduction email includes enough context that the recipient can evaluate the relevance of the introduction without needing to click elsewhere.

LinkedIn: connection-request framing and the public profile that replaces the brief

LinkedIn introductions operate under a different constraint than email: the 300-character InMail or connection note limit forces radical compression of the introduction brief, but LinkedIn compensates with something email cannot provide: the public profile. When a connector introduces two people on LinkedIn, the recipient can immediately click through to the introduced person’s full professional history, mutual connections, endorsements, and public posts. The LinkedIn profile is the brief. This changes what the introduction message itself needs to do: it does not need to establish professional context (the profile does that), but it does need to establish why this specific connection is relevant to the recipient right now. LinkedIn DMs are best suited to professional peer introductions where both parties have informative profiles. They are poorly suited to introductions that require nuanced explanation of why the fit is right. For those, email is more appropriate. The connection-request variant (asking a connection to introduce you by sending a connection request with a personalised note) shifts the framing: the connector is not present in the conversation, so the opening message carries a higher burden of establishing relevance. LinkedIn research on message response rates consistently finds that personalised, specific notes outperform generic ones by wide margins, which is predictable given the volume of connection requests the average professional receives.

Slack and Teams: workspace context determines everything

Workplace messaging platforms (Slack, Microsoft Teams) are increasingly used for professional introductions, particularly in tech and startup environments where the professional community uses these platforms for day-to-day communication. The etiquette is more variable than email or LinkedIn because it depends almost entirely on the workspace context. A Slack introduction within a shared community workspace (an industry group, an alumni community, a co-working Slack) operates more like a LinkedIn introduction: both parties are in the same community, the connector is visible to both, and the shared membership provides implicit social context. A Slack introduction where the connector tags someone from another workspace requires a DM rather than a channel mention, and this significantly changes the dynamics: a cold DM on Slack has a low expected response rate unless the connector’s mention in the opening message provides enough credibility that the recipient is motivated to respond. @-mention introductions in shared channels work best when the channel’s purpose and membership is clear to all parties. Introducing two people in a relevant channel with a brief explanation ("@[person A], meet @[person B]: [reason they should connect]") is a lightweight, visible introduction that both parties can follow up in DM. Channel introductions create social visibility that private DM introductions do not, which can be an asset (the community sees you connecting useful people) or a liability (the introduction is visible to everyone in the channel before either party has had a chance to evaluate it). The key principle on workplace messaging platforms: match the formality and privacy level to the relationship you have with both parties.

WhatsApp and iMessage: personal network, highest trust, mandatory brevity

WhatsApp and iMessage introductions operate in the highest-trust, highest-intimacy tier of professional communication. Using these platforms for an introduction carries an implicit signal: the connector knows both parties well enough to have their personal phone number, and considers the introduction important enough to use the most personal channel available. This signal is valuable: a WhatsApp introduction lands differently than a LinkedIn DM because the social weight behind it is higher. The format constraints are strong: WhatsApp message discipline is brief, voice notes are common in many professional communities (particularly in European and Latin American business cultures), and the expectation of prompt response is higher than email. WhatsApp introductions work best when both parties already know the connector personally, the introduction is to someone the connector knows closely, and the ask is specific enough to fit in a short message. A multi-paragraph introduction brief is out of place on WhatsApp; the effective format is a two or three-sentence message explaining the connection and a direct ask ("Can I introduce you two? I think [one sentence reason]."), with the detailed brief following only after both parties have confirmed interest. The double opt-in is especially important on personal messaging platforms, because an unsolicited group chat or forwarded contact feels like a privacy boundary violation in a way that a BCC’d email does not.

In-person hand-off: the 30-second verbal brief and why the follow-up email matters

In-person introductions at events, meetings, or social occasions are the oldest form of warm introduction, and their limitations are also the oldest: they are ephemeral. Unless the connection is anchored by a follow-up, the in-person introduction, no matter how well-positioned verbally, often decays within days because neither party has the other’s contact information in a retrievable form, or because the brief delivered verbally is too compressed to be fully recalled later. The 30-second verbal brief has a specific job: establish relevance quickly enough that both parties are interested in exchanging contact details and following up. The connector does not need to tell the full story in person. They need to say enough that the two parties are motivated to continue the conversation. The follow-up email that anchors the in-person introduction is what converts the encounter into an actual connection. Best practice: the connector sends a brief email within 24–48 hours of the event that recaps the introduction, adds the fuller context they could not include verbally, and gives both parties a written record with contact details. This follow-up is not optional. Without it, the in-person introduction is often lost to the volume of contacts exchanged at any professional gathering.

Two rules that never change

Universal rule 1: Double opt-in applies on every platform

The principle of double opt-in (asking both parties whether they want to be connected before sending the introduction) applies across all platforms, not just email. The mechanics vary by platform: on email, this means checking with both parties before sending the group email; on LinkedIn, it might mean a quick DM to one party asking if they’re open to a connection before tagging them publicly; on WhatsApp, it means asking before creating a group chat or forwarding a contact. The core reason does not change across platforms: forcing an introduction on someone who has not indicated interest puts them in the awkward position of having to either engage with a connection they do not want or visibly ignore one someone else vouched for. This damages the recipient’s relationship with the connector more than with the introduced party. The double opt-in is not a formality; it is how a connector protects both their own credibility and the quality of their network.

Universal rule 2: Loop-close is always required, regardless of platform

The loop-close, telling the connector what happened after the introduction, is a norm that applies across every platform where a warm introduction was made. On email, this means a brief reply to the original thread (or a separate note to the connector) after you have made contact with the introduced party. On LinkedIn, a quick DM to the connector. On WhatsApp, a voice note or message to the group or to the connector directly. The loop-close matters for two reasons that do not change by platform. First, the connector’s credibility is on the line: they vouched for the meeting, and their vouching carries future weight only if the people they introduce remember them as someone whose referrals lead to real conversations. A connector who never hears what happened to their introductions receives fewer signals about which referrals are working and gradually loses the feedback loop that makes them better at making introductions. Second, the connector is the person most likely to be in a position to help again (with more context, with an escalation, or with a different introduction), but only if they know how the first one went.

Quick reference: platform selection

Email: default choice; no character limit, forwardable, creates a written record. Right for any introduction that requires explanation.

LinkedIn: peer introductions where both parties have informative public profiles. The profile replaces the brief; the message establishes specific relevance.

Slack/Teams: shared community or workspace context; @-mention in relevant channel for visibility, DM for privacy. Formality follows the workspace culture.

WhatsApp/iMessage: personal network only; both parties must be personal contacts. Brief by design; double opt-in before group chats or contact sharing.

In-person: ephemeral without a follow-up email; the verbal brief establishes interest, the email anchors the connection.

FAQ

Introduction etiquette FAQs

Which platform should you use to make a warm introduction?

Default to the platform where you have the strongest relationship with both parties and where the context of the introduction will come through most clearly. Email is the safe default for most professional introductions because it has no character limit, is forwardable, and creates a written record. Use LinkedIn when both parties have informative public profiles and the introduction is between professional peers. Use WhatsApp or iMessage only when you have personal phone relationships with both parties and the introduction is genuinely personal-network level. The rule is to match the platform to the intimacy level of the relationship: an introduction that requires nuanced explanation of why the fit is right should go via email, not a character-limited DM.

Does double opt-in apply on LinkedIn?

Yes, and it is especially important on LinkedIn because connection requests are visible and persistent. Before tagging someone publicly or sending a connection request on their behalf, a quick DM to confirm they are open to the connection takes less than a minute and prevents the awkward situation where the recipient receives an unexpected request they feel obligated to either accept or visibly ignore. On LinkedIn, the opt-in check can be as simple as "Would you be open to connecting with [name]? I think [one-sentence reason]." Most people will say yes to a well-framed opt-in request. The value of the check is not filtering out unwilling recipients but ensuring the introduction lands with informed consent on both sides.

How do you make a warm introduction in a Slack community?

The most effective Slack community introduction is a brief @-mention in the most relevant channel: "@[Person A], meet @[Person B]: [one sentence reason they should connect], [one sentence why now or what the specific opportunity is]. DM each other if you are open to a chat." This gives both parties public context and makes it easy for them to follow up privately. The channel should be relevant to the subject of the introduction (a product introduction in the #product channel, a founder introduction in the #founders channel), and the connector should be a recognisable member of that channel, so the mention carries the weight of their community reputation rather than arriving as noise.

When is a WhatsApp introduction appropriate?

A WhatsApp introduction is appropriate when: you have both parties’ personal phone numbers (meaning you know them at a genuinely personal level), the introduction is time-sensitive or the subject matter is personal enough that email feels too formal, and both parties are in a professional community where WhatsApp is the normal communication channel (common in many European, Middle Eastern, and Latin American business contexts). A WhatsApp introduction to someone you only know professionally, where the WhatsApp relationship exists because of a work context rather than a personal one, should be treated with the same care as any other high-trust personal channel. When in doubt, confirm via DM that both parties are open to the introduction before creating a group or forwarding contact details.

What is the best way to follow up on an in-person introduction?

Within 24–48 hours of the event, send a brief email to both parties that recaps the introduction, adds any context you could not deliver verbally, and includes both parties’ contact details. The email should be short (three to five sentences is sufficient) and should reference the event and the conversation so both parties can immediately place the context. This follow-up converts an ephemeral in-person encounter into a retrievable written record. The introduced parties can then follow up directly, and the connector has a natural loop-close point when they hear how the conversation developed.

Does LetsBridge support multi-platform introductions?

LetsBridge is designed to make the warm introduction process structured and trackable at the professional network level, ensuring that the right introduction reaches the right person through the right connector, and that the value of that introduction is properly attributed. The platform mechanics of how the initial contact is made (email, LinkedIn, in-person) are up to the connector and the parties involved. What LetsBridge adds is the layer above platform mechanics: a clear way to identify who can make which introduction, a structured brief that works across delivery formats, and a way to track outcomes so connectors are recognised for the value they create.

Make introductions that actually convert

LetsBridge gives the warm introduction process structure and trackability, so the right introduction reaches the right person through the right connector, and the value of every connection is properly recognised.