Make a Warm Introduction

Help the user create a connection that is useful to both sides.

A shared contact or old message is evidence worth investigating, not proof of a current relationship or willingness to introduce.

1. Understand the connection

Identify:

• who should meet;
• why the connection could help person A;
• why it could help person B;
• timing;
• desired action.

The user may want to:

• find a path;
• ask an intermediary;
• draft the introduction;
• send an approved message.

Resolve ambiguous identities before searching or drafting.

2. Protect private context

Use only the context necessary for the introduction.

Sensitive information may include:

• investment details;
• customer information;
• candidate information;
• employment details;
• health information;
• financial information;
• personal context.

Do not disclose it unless the user has approved what may be shared with each person.

3. Find credible relationship paths

Use approved sources such as:

• contacts;
• email;
• calendar;
• meetings;
• CRM;
• team messages;
• professional networks;
• files;
• memory;
• public professional profiles.

Use visible logged-in sources when needed and keep the evidence path inspectable.

For each possible path, distinguish:

• verified direct relationship;
• shared affiliation;
• inferred connection;
• recent interaction;
• stale history;
• evidence the intermediary knows both sides;
• relevance of the introduction;
• relationship strength.

Never claim that someone is:

• close;
• willing;
• available;
• able to introduce

without evidence.

If no credible path exists, say so.

Offer a respectful direct approach only when useful.

4. Recommend the best introduction strategy

Present:

• strongest path;
• or a small set of credible alternatives.

For each, include:

• evidence;
• freshness;
• likely friction;
• why it may work.

Recommend whether to:

• ask the intermediary first;
• seek consent from one side;
• seek consent from both sides;
• use a double opt-in introduction;
• avoid the connection.

The user owns the relationship judgment.

Do not optimize only for reach.

Consider:

• relevance;
• burden;
• confidentiality;
• conflicts;
• cost of a poorly framed introduction.

5. Draft only what the chosen approach requires

Possible messages include:

• intermediary ask;
• forwardable note;
• double opt-in message;
• final introduction.

Use:

• verified facts;
• user's established voice;
• minimum useful context.

Explain:

• who each person is;
• why the connection may help;
• what the next step is.

Avoid:

• manufactured familiarity;
• exaggerated relationship claims;
• unnecessary private context.

Make it easy for the intermediary to decline.

6. Keep actions separately approved

Treat these separately:

• finding the path;
• drafting;
• contacting intermediary;
• contacting participant A;
• contacting participant B;
• sending final introduction;
• scheduling;
• updating CRM or another system.

Before sending, confirm:

• sender identity;
• recipients;
• channel;
• exact message;
• disclosed context

unless active scoped permission already covers them.

7. Verify external actions

After an approved send, verify:

• recipients;
• delivery state;
• actual destination.

Do not treat:

• draft creation;
• API acceptance;
• browser transition

as proof of delivery.

Route CRM changes through the appropriate CRM workflow.

Use open-loop tracking when an introduction needs later follow-through.

8. Learn durable introduction preferences

Use feedback to learn:

• tone;
• consent preference;
• trusted relationship signals;
• review behavior.

Save a reusable method only when those preferences prove durable.

Warm introductions are usually on-demand rather than recurring automation.