Member Introduction Email Templates: 8 Double Opt-In Scripts for Association & Chamber Staff

A member asks if you can introduce them to someone. Or you notice a fit after an event: a buyer who needs exactly what another member sells. The quickest option is one email to both people saying they should meet. It's also the option most likely to backfire. A cold connect puts one person on the spot, makes a polite refusal awkward, and explains why so many "warm" introductions never turn into a conversation. If you want the structural reasons intros stall, read our piece on why warm professional introductions go cold. This page sticks to the copy.

Association and chamber staff need a double opt-in sequence and scripts for specific scenarios. One generic blurb won't cover it. Below you'll find three core emails, five scenario scripts, decline and nudge language, and a short checklist for logging what happens.

How do you make a double opt-in introduction between two members? Don't put both people on one email until each has said yes in private. First, ask the member who wants the intro for a short forwardable paragraph covering who they are, what they need, and what a useful conversation looks like. Second, email the other member alone with that context and an easy "no" or "not now." Third, once both sides have said yes in writing, send a short connecting email that explains why these two people specifically, says who makes the first scheduling move, and takes you out of the thread. If either side declines or stays silent for about a week, close the loop with the requester. Don't force the intro.

What Double Opt-In Means for Association and Chamber Staff

In a double opt-in introduction, both people agree privately before anyone sends the connecting email. The etiquette is well established in personal networking. The Muse's double opt-in intro template is the classic version of the private check.

Staff introductions are different in three ways. You are spending the organisation's trust as well as your own. You may be introducing members who barely know you, so they have less reason to forgive a surprise. And each introduction is evidence of membership value, which means it's worth recording.

One rule makes the system work: if someone hasn't replied after about seven days, treat it as a no and tell the requester plainly. Happenstance's guide to the double opt-in intro applies the same principle. Silence is an answer, and leaving the requester waiting costs you more goodwill than an honest "not this time."

The 3-Step Core Sequence (Scripts 1–3)

The order never changes: get context from the requester, check privately with the other member, then connect them. Every scenario script later in this article adapts these three emails. Replace anything in [brackets].

Script 1: Reply to the requester and ask for a forwardable blurb

A forwardable blurb is a short paragraph the requester writes so you can paste it straight into the private check. The structure in LetsBridge's guide to writing a warm introduction email works well here: who they are, why the conversation helps the other person, the specific ask, and a graceful way out.

Subject: Re: Intro to [Name]

Hi [Requester first name],

Happy to ask [Name] if they're open to a conversation. To make it easy for them, could you send me 4–6 lines I can forward as-is?

• Who you are and what [Company] does

• What you'd like from the conversation

• Why it might be useful for [Name] as well

• What you're asking for (for example, a 20-minute call)

I'll check with [Name] privately and let you know either way, usually within a week.

[Your name]
[Role, Organisation]

Script 2: Private opt-in check to the other member

Subject: Intro to [Requester name]?

Hi [Recipient first name],

[Requester name] from [Company], a fellow member, asked whether I'd introduce you. In their words:

"[Pasted blurb]"

I thought of you because [one specific reason: shared sector, current project, stated need].

They're not copied on this email. If you're open to it, reply yes and I'll connect you both. If it's a no or a not-now, that's completely fine, and I'll pass it on without any detail.

[Your name]

Script 3: Connecting email after both say yes

Subject: Intro: [Name A], meet [Name B]

Hi [Name A] and [Name B],

Thanks to you both for saying yes.

[Name A] leads [role] at [Company] and is [one relevant line].
[Name B] runs [role] at [Company] and [one relevant line].

I think you should talk because [one shared reason].

[Name A], would you suggest a couple of times for a 20–30 minute call? I'll step back from here, but I'm around if you need anything.

[Your name]

Subject-line cheat sheet

• Opt-in check: Intro to [Name]?
• Connecting email: Intro: [Name A] <> [Name B]
• Connecting email (warmer): Intro: [Name A], meet [Name B]
• Scenario-specific: Intro: [Name A] <> [Name B] (re: [topic])
• Post-event: Following up from [Event]: [Name A] <> [Name B]

The connecting email follows the same handoff pattern as The Muse's professional introduction template: introduce both people, give the reason, then hand over. What staff should add is a named owner for the next step. Without that line, both people tend to wait for the other to write first.

Script 4: Supplier or Buyer Match

Use this script when a member needs a supplier, buyer, or service provider and another member is a credible fit. Commercial introductions need more detail than social ones: the category, the timing, the location, and whether the conversation is exploratory or tied to an active purchase. Saying "this is exploratory, not a pitch" in the opt-in check makes it easier for the supplier to say yes and stops them treating the call as a qualified lead.

Add this to Script 2:

They're looking for [category] for [project or need], starting around [timing], based in [location]. At this stage it's an exploratory conversation, not a request for a quote.

For the wider practice behind these matches, see our guide to supplier discovery through trusted professional networks.

Illustrative connecting email (details are examples only):

Subject: Intro: [Priya] <> [Tom] (re: packaging supply)

Hi [Priya] and [Tom],

Thanks for saying yes to this one.

[Priya] runs operations at [a regional food producer] and is reviewing packaging suppliers for a new product line launching in [Q2].
[Tom] leads accounts at [a packaging manufacturer] and works with several members in food and drink.

The fit is straightforward: [Priya] needs [recyclable retail packaging at mid-volume], and that's [Tom]'s core business.

[Priya], would you send [Tom] two or three times for a 30-minute call? I'll step out of the thread now.

[Your name]

Script 5: Partner or Collaboration Match

Use this script when two members could partner, bid for work together, or refer clients to each other. The main difference from a supplier match is reciprocity. If the opt-in check reads as one member asking for a favour, the other member will weigh their time against nothing. Show what both sides could gain. Our partnership matchmaking framework explains what makes a partner fit. This script covers the emails.

Add this to Script 2:

I think there could be something in this for both of you. [Requester] has [capability or client base], and you have [complementary capability]. Together you might be able to [bid for larger contracts / cover a service gap / refer work in both directions].

Connecting email adaptation:

Subject: Intro: [Name A] <> [Name B] (re: [joint bid / referral partnership])

Hi both,

Thanks for opting in. [Name A] specialises in [area]; [Name B] covers [adjacent area]. Several members have mentioned [the type of project] needing both, which is why I thought of you together.

[Name B], would you take the first step and suggest a time? A short call to compare client profiles is probably the right start.

[Your name]

Give the next step to whichever person has the clearer reason to move first. In a partner match, that isn't always the requester.

Script 6: Post-Event Continuation

Use this script when two attendees left a conversation unfinished or showed interest in the same session topic. Send it within 24–72 hours, while the event is still fresh in both people's minds. That timing fits the wider cycle we describe in how to keep your association community engaged between events.

You still need double opt-in, with one exception. If both members told you in person that they'd like to be connected, you can skip the private check and send a short connecting email that reminds them they already agreed. If only one of them said it, or you only saw them talking, run Script 2 first.

When both already agreed in person:

Subject: Following up from [Event]: [Name A] <> [Name B]

Hi [Name A] and [Name B],

At [Event] on [day], you both asked me to connect you after your conversation about [topic]. Here you are.

[Name A], you mentioned you'd send over [the case study / some times to talk]. I'll leave it with you both.

[Your name]

When you spotted the fit yourself (opt-in check):

Subject: Following up from [Event]: intro to [Name]?

Hi [Name],

At [Event], [Name B] asked a question in the [session] about [topic], and it reminded me of what you said about [related point]. Would you be open to an introduction? No pressure either way.

[Your name]

Script 7: New-Member Welcome Introduction

Use this script in a new member's first one or two weeks to introduce them to one relevant peer. A single well-chosen person does more for a new member than a welcome pack listing everyone. It sits inside a wider onboarding sequence, which our member onboarding playbook covers in full.

Ask the existing member first. Their time is the scarcer resource, and a new member who just joined will almost always welcome the introduction. You can confirm with the new member in your welcome conversation instead of sending a separate email.

Opt-in check to the existing member:

Subject: Would you welcome a new member?

Hi [Name],

[New member] joined this week. They run [Company], which [one line], and they're keen to meet people working in [area]. You were the first person I thought of.

Would you be up for a short intro call in the next couple of weeks? If now isn't a good time, just say so.

[Your name]

Connecting email:

Subject: Welcome intro: [New member], meet [Existing member]

Hi [New member] and [Existing member],

[New member], welcome again. [Existing member] has been a member since [year], works in [area], and kindly offered to compare notes.

[New member], could you suggest a time that suits you both? If anything gets stuck, I'm your contact here.

[Your name]

Script 8: Re-Engagement Introduction

Use this script when a member has gone quiet or looks at risk of not renewing. A "we miss you" email blast asks for attention and gives nothing back. Offering a specific person gives them something concrete. For the reasons members drift and the wider recovery approach, see why members become inactive and how to re-engage them.

Reverse the usual order: check with the quiet member first. Keep the ask small, so that replying is easy. A reply is a sign of re-engagement in its own right, whatever they decide.

Subject: An intro that might be useful?

Hi [Name],

I was looking at who's working on [their area] at the moment, and [Other member] at [Company] is [doing something relevant: expanding into X, looking for Y]. I wondered whether a conversation might be useful to you.

If you're interested, reply and I'll check with them first. If not, no problem at all.

[Your name]

If they say yes, run Script 2 with the other member, using a sentence or two from the quiet member's reply as context. Then send Script 3 and make the quiet member the next-step owner only if their reply suggested real energy. Otherwise give that job to the more active member, so the introduction doesn't depend on the person who has been least active.

Decline, "Not Now," and One Follow-Up Nudge

These aren't counted among the eight scripts, but you'll need them every week.

Decline to the requester (the other side said no or didn't reply):

Subject: Re: Intro to [Name]

Hi [Requester],

I checked with [Name], and it isn't the right time on their side. That happens, and it says nothing about your ask. Two options: I can try [Alternative member], who also works in [area], or I can keep your blurb on file and suggest a fit when one comes up.

[Your name]

Don't pass on the other member's reasons, even if they gave you some.

Reply to the member who said no:

Thanks for letting me know, [Name]. I won't connect you, and I appreciate the quick reply.

That's all you need to write. Adding guilt or a second ask makes it harder for them to say no the next time.

One nudge, around four or five days after the connecting email, sent only to the named next-step owner:

Hi [Name], just checking the intro with [Other name] reached you. Shout if you need anything from me.

Send one nudge at most. If nothing moves after that, log it as unknown and stop.

Before You Hit Send: Staff Checklist

☐ Send from a named person. Never use a no-reply address.
☐ Get a private yes from both sides, unless they already agreed face to face.
☐ Include one reason, one call to action, and one next-step owner.
☐ Log the date, both parties, the scenario, and the outcome (accepted, declined, meeting held, or unknown).
☐ Check the log before introducing the same pair again.
☐ Refuse or redirect requests that read like spam, involve competitors without both parties' consent, or go beyond what your relationship with either member can support.

The log matters most at renewal time. A record of introductions made and meetings held gives you real evidence for a member value report. Doing this by hand works at low volume. Once the number of introductions grows, Boardro helps staff see which members to introduce, based on what members offer and need, and keeps track of the outcomes.

Frequently Asked Questions

How do you make a double opt-in introduction?

Ask both people privately before putting them on the same email. Get a short forwardable paragraph from the requester, check with the other person with context and an easy no, and only then send a connecting email that explains why these two and who takes the next step.

What should a member introduction email say?

Name both people, give one specific reason they should speak, add one line of relevant context on each, and assign who schedules the first call. Keep it short. Thank them for opting in if you already checked.

What is a forwardable blurb?

A short paragraph the requester writes so staff can paste it into the private opt-in check. It covers who they are, why the conversation helps the other person, the specific ask (for example a 20-minute call), and a graceful out.

Should association staff still use double opt-in after an event?

Yes, unless both members already agreed in person to be introduced. If they did, a short connecting email that reminds them of the shared context is enough. If they did not, run the private check first.

How do you follow up after an introduction email?

Wait a few days, then send one short nudge only to the person named as the next-step owner. Do not chase both sides repeatedly. If there is still no movement, log it and stop.

What if one member says no?

Thank them, do not connect the pair, and tell the requester plainly that it is not the right time. Offer an alternative member or a later date when you can.

How is this different from a cold LinkedIn intro request?

Staff intros carry the organisation's reputation. Double opt-in protects both members and the association or chamber. The templates here assume you are brokering inside a membership, not blasting your personal LinkedIn graph.

Start With a Private Yes

Each script follows the same rule: get a private yes from both people, then send a short connecting email that names who acts next. Getting the conversation started is only part of the job. To understand what keeps an introduction moving afterwards, read why warm professional introductions go cold and what happens after the connection.