A double opt-in introduction starts with permission, not a path

A double opt-in introduction means the connector checks privately with each person and brings them together only after both agree. It sounds simple. The awkward part begins one step earlier, when you can see a relationship path and start treating it like permission.

A path can show that two people are connected through relationships you have recorded. It cannot tell you whether those relationships are current, close or suitable for this request. It also cannot tell you whether the person you hope to meet wants the conversation.

The practical rule is short: map the path, verify the context, ask privately, wait for both people to opt in, then record what happened.

Four states that look similar but are not

Introduction etiquette gets easier when you separate what you know from what you are still assuming.

Each state needs its own evidence. A line on a relationship map supports the first state. Only the people involved can move it any further.

The shortest relationship path is a starting point

A relationship path describes structure. It does not measure warmth.

The shortest saved route might pass through a former colleague, a company, a group or an event. Those connections can restore useful context, but they carry different meanings. Two people who attended the same event may never have spoken. A former colleague may know someone well but have lost touch. An introduction recorded years ago preserves where the relationship began, not how close it is today.

A longer route with fresh, specific context may be more appropriate than a short, stale one. Sometimes the honest result of checking is that there is no warm path at all.

Before you ask for an introduction, check five things:

1. Identity: Is this the right person, in their current role?
2. Relationship: How does the possible connector actually know them?
3. Recency: Is that relationship current enough for the connector to judge the request?
4. Relevance: Why might the conversation be useful to the recipient as well as to you?
5. Shareability: Which details are accurate and appropriate to pass on?

If you cannot answer those questions, you have a research lead. You do not yet have a warm introduction path.

Ask the connector to check, rather than commit

The first request should preserve the connector's judgement. They may know that the timing is poor, the relationship has changed or the topic is outside the other person's interests. Their reputation is involved too.

Ask whether they would be comfortable checking with the intended recipient. That is smaller and more respectful than asking them to put you in touch immediately.

Give them enough detail to make the decision:

• the recipient's name
• one specific reason for the conversation
• why it may be relevant to the recipient
• the narrow next step you want
• a short note they can forward
• an easy way to decline or pause

For example:

Would you be comfortable checking whether Priya is open to an introduction about community data governance? I am hoping to ask one specific question about how her group handled member consent. I have included a short note you can forward if useful. No pressure if the fit, relationship or timing is not right.

The wording matters because it asks for a private check, not access on demand. It also avoids claiming a relationship you have not verified. If your map only shows a shared company or event, do not write, “I saw that you know Priya.”

The recipient needs a separate choice

A connector's yes only means they are willing to ask. The recipient still needs enough context to decide for themselves.

Harvard Business Review recommends contacting both people individually, clarifying why the connection is being requested and asking permission before sending the joint introduction. Stanford Graduate School of Business offers similar guidance: check with both parties and explain why the connection makes sense.

The connector should send the request privately, without placing the requester on the same thread. Silence is not consent. A pause or decline is a complete answer, and it should not trigger repeated nudges through another route.

This is professional introduction etiquette, not the mailing-list meaning of double opt-in. It is also not a universal law. It is a practical way to protect attention, privacy and the connector's relationship with both people.

Share enough context, then stop

A forwardable note helps the recipient assess the request. It should not become a bundle of private history.

Useful context includes who is asking, the specific topic, why it may be relevant and the proposed next step. Personal disclosures, confidential work, health details or comments supplied in confidence stay out. Contact details should be shared once the introduction is accepted, not merely because you have them stored.

Once both people have opted in, the actual introduction can be brief:

• name both people clearly
• restate the agreed reason for connecting
• include only the context each person has approved or would reasonably expect
• state the next action, if one was agreed
• let them continue directly

Keep the request within the scope they accepted. Permission for a short conversation about one topic does not silently expand into a sales pitch, recruitment approach or fundraising request.

Record the introduction after it happens

A possible path is not an introduction record. Neither is a request that was declined, paused or left unanswered.

After the connector has brought both people together, record the facts: who introduced whom, the actual introduction date, the purpose and any agreed next action. Keep the introduction date separate from the date of a later call or meeting.

This is where a private relationship map can help. Kinnetly shows the shortest chain of relationships you have deliberately saved between two people already on your map. You can inspect the context, verify it outside the product and, after the introduction happens, record who introduced whom with the correct date. Private notes can preserve the purpose, and a one-off reminder can hold a real next action.

Kinnetly does not contact either person, verify consent or decide which path is warmest. Those decisions stay with you and the people involved.

Map, verify, ask, opt in, introduce, then record. If a step remains uncertain, stop at the last confirmed state.

Start a private relationship map in Kinnetly.

Sources

• Harvard Business Review, “Before Making an Email Introduction, Ask Permission”
• Stanford Graduate School of Business, “Eight Tips for Building, Maintaining, and Leveraging Your Professional Relationships”
• Royal Geographical Society, “Expanding your network through professional introductions”