A good warm introduction depends on more than finding a shared contact. The intermediary needs a real relationship, the reason for connecting should make sense to both sides, and private context should not leak into a message simply because it helped identify the path.

Strawberry can inspect approved email, calendar, meetings, CRM, team messages, professional networks, files, memory, and public profiles in the same visible browser. It distinguishes verified relationships from inferred connections, then prepares the smallest considerate ask or introduction for review.

Start with why both people should meet

The first question is not who can reach whom. It is why the connection could help each person now. Strawberry establishes the people, timing, purpose, and whether the user needs a path, an intermediary ask, a double opt-in, or a final introduction.

Want to try it?

Ask your Strawberry companion: “Find the strongest credible path between these people, explain the relationship evidence and sensitivity, and prepare the right introduction or intermediary ask for review.”

Skill

Make a thoughtful warm introduction

Find a credible path and prepare the right ask or introduction without exposing private context.

Verify the relationship before using it

  • A direct relationship versus a shared affiliation or inferred connection.
  • Recent interaction versus stale history.
  • Evidence that the intermediary knows both sides versus a profile-level connection.
  • The relevance of the introduction versus the apparent strength of the relationship.
  • Context safe to share versus information that must stay private.

A shared company, school, event, or social-network edge can reveal a path worth investigating. It does not prove that the intermediary is close, willing, or able to introduce. Strawberry shows the evidence and freshness so the user can make that judgment.

Choose a considerate path

SituationPossible approach
The intermediary is well placed but consent is unclearPrepare a concise ask with an easy way to decline
The intermediary wants something forwardableDraft a short note explaining who the requester is and why the meeting may help
The context is sensitive or the relationship is valuableUse a double opt-in before connecting the two sides
No credible warm path existsSay so plainly and consider a respectful direct approach

The strongest path is not always the most relevant one. The recommendation should consider the intermediary's burden, conflicts, confidentiality, timing, and the cost of a poorly framed ask.

Draft with the minimum useful context

The message explains who each person is, why the connection may help both sides, and what a sensible next step looks like. It uses the user's established voice, avoids manufactured familiarity, and does not reveal sensitive investment, customer, candidate, employment, financial, health, or personal details simply because they were available during the search.

Finding the path, drafting an ask, contacting the intermediary, contacting either participant, sending the introduction, scheduling, and updating a record remain separate actions. Before any send, Strawberry shows the sender, recipients, channel, exact message, and context being disclosed unless an active scoped permission already covers them.

Verify the follow-through

After an approved send, Strawberry checks the actual destination and reports the delivery state instead of treating a draft or accepted request as proof. Promised introductions can move into open-loop tracking, and approved relationship changes can move into the CRM without collapsing those jobs into the introduction itself.

Skill

Find work that is slipping

Track a promised introduction or follow-up that should not be lost.

Skill

Keep my CRM up to date

Apply separately approved relationship or activity changes to the CRM.

Feedback can preserve the user's tone, consent preference, and trusted relationship signals. Warm introductions usually remain on demand; the judgment and privacy involved make them a poor candidate for unattended automation.

Run your whole company from one placeConnect introductions with fundraising, hiring, customers, and company building.
Official Strawberry skill
Copy skill file Download skill file
name
make-a-warm-introduction
description
Find a credible path between people and prepare a considerate warm introduction using approved relationship context. Use when someone wants to connect a founder, investor, customer, candidate, expert, partner, or colleague; verify the relationship, protect private context, and keep drafting, asking, sending, and recording the introduction separately controlled.

Make a Warm Introduction

Help the user make a connection that is useful to both sides. A shared contact or old message is a lead to inspect, not proof of a current relationship or willingness to introduce.

1. Understand the connection

Identify who should meet, why the connection could help each person, the timing, and whether the user wants to find a path, ask an intermediary, draft the introduction, or send an approved message. Resolve ambiguous identities before searching or drafting.

Use only the context needed for this connection. Sensitive investment, customer, candidate, employment, health, financial, or personal details stay private unless the user has approved what may be shared with each person.

2. Find and verify a credible path

Search approved contacts, email, calendar, meetings, CRM, team messages, professional networks, files, memory, and relevant public profiles. Use visible logged-in sites when relationship evidence lives there, keeping the path inspectable for the user.

For each plausible path, distinguish:

  • a verified direct relationship from a shared affiliation or inferred connection;
  • recent interaction from stale history;
  • evidence that the intermediary knows each side from evidence that they merely appear connected;
  • the likely relevance of the introduction from the strength of the relationship; and
  • private context from details safe to share.

Never claim that someone is close, willing, or able to introduce without evidence. If no credible path exists, say so and offer a respectful direct approach only when useful.

3. Recommend the best approach

Present the strongest path or a small set of alternatives with the evidence, freshness, likely friction, and why each may work. Recommend whether to ask the intermediary first, seek consent from one or both sides, prepare a double-opt-in introduction, or avoid the connection.

The user owns the relationship judgment. Do not optimize only for reach; consider relevance, burden, confidentiality, conflicts, and the cost of a poorly framed ask.

4. Prepare the messages

Draft only what the chosen approach needs. This may include:

  • a concise ask to the intermediary, with an easy way to decline;
  • a forwardable note that explains who the requester is and why the meeting may be useful;
  • a double-opt-in message for each side; or
  • the final introduction after consent is clear.

Use the user's established voice and verified facts. Share the minimum useful context, state why the connection may help both sides, avoid manufactured familiarity, and make the next step easy.

5. Send and verify only the approved action

Treat finding a path, drafting an ask, contacting an intermediary, contacting either participant, sending the introduction, scheduling, and updating a record as separate actions. Before sending, confirm the sender identity, recipients, channel, exact message, and context being disclosed unless an active scoped permission already covers them.

After an approved send, verify the recipients and delivery state in the actual destination. Do not treat a draft or accepted API request as proof of delivery. Use strawberry/sales/keep-crm-updated for separately approved CRM changes and strawberry/operations/close-open-loops when a promised introduction needs later follow-through.

Use feedback to remember the user's tone, consent preference, trusted relationship signals, and review behavior. Save a custom or team skill only when those choices prove durable; warm introductions usually remain on demand rather than becoming an automated Routine.