AI Prompt: Draft a Warm Intro Request Email

The warm intro request email is the single most under-engineered artifact in B2B sales. Most reps draft it themselves, write something awkward and overly long, and wonder why the connector never replies. This AI prompt generates a request that's: (1) short enough to forward as-is, (2) written in the connector's voice, (3) clear about the specific ask, and (4) easy for the target to say yes to. Use it before every connector ask.

The prompt

You are drafting a warm-intro request email for me to send to [CONNECTOR_NAME].

Context:
- I am [MY_NAME], [MY_ROLE] at [MY_COMPANY]
- The connector is [CONNECTOR_NAME], [CONNECTOR_ROLE] at [CONNECTOR_COMPANY]
- My relationship with the connector: [describe — e.g., "former colleague at Mindtickle, last spoke 6 months ago"]
- The target I want to be introduced to: [TARGET_NAME], [TARGET_ROLE] at [TARGET_COMPANY]
- Why I want the intro: [be specific — e.g., "we're building a champion-tracking product and TARGET_COMPANY just announced a big GTM ops investment"]
- What the connector knows about the target: [describe — e.g., "they worked together at Stripe"]

Task:
Draft an email I send to the connector that:
1. Is short (under 120 words)
2. Opens with one line of genuine catch-up (not fake small talk)
3. Makes the ask in 1-2 sentences
4. Includes a 2-3 sentence "forwardable blurb" the connector can paste directly into an intro email to the target
5. Gives the connector an easy out ("no worries if not")
6. Avoids the word "introduction" (it triggers friction); use "intro" or "connect"

Return just the email body, no subject line.

Variables to customize

  • MY_NAME, MY_ROLE, MY_COMPANY — who you are
  • CONNECTOR_NAME, CONNECTOR_ROLE, CONNECTOR_COMPANY — the person you're asking
  • Relationship context — be honest about how/when you last interacted
  • TARGET_NAME, TARGET_ROLE, TARGET_COMPANY — the buyer you want to meet
  • Why you want the intro — specific and current; not "we'd love to chat"
  • What the connector knows about the target — gives the connector context to position the intro

Example output

Hey Sarah,

Hope the kids are surviving the school year. Quick favor — I saw Maria Lopez just took the CRO role at Acme Corp. You two overlapped at Stripe, right?

We're building Boomerang, the warm-intro orchestration layer for B2B sales. Acme's new GTM operating model looks like a direct match for what we do. Worth an intro?

Forwardable blurb if it's easier:
"Maria, meet Shankar (Boomerang founder). They've built the activation layer Sarah and I have been talking about for years — turning customer + investor relationships into pipeline. Worth a 15-min chat. He'll take it from here."

No worries if the timing's bad. Either way, coffee soon?

— Shankar

When to use this prompt

1. Every connector ask, every time. The cost is one AI prompt call; the upside is dramatically higher acceptance.

2. Especially for high-stakes connectors. Your top investor or biggest customer champion — the email needs to be tight enough that they don't have to think before forwarding.

3. When you're asking a connector you haven't talked to in 6+ months. The reactivation context matters; the prompt forces you to acknowledge the gap.

Common mistakes the prompt prevents

Burying the ask in paragraph 3. The ask should be in the first 3 sentences, not after a wall of context.

Asking the connector to "see if there's a fit." That's their job, not yours. Tell them what you want.

No forwardable blurb. If the connector has to write the intro email themselves, friction kills the ask. Give them the paste-ready version.

Fake catch-up. "Hope you're doing well!" is hollow. The opening line should be specific and human.

No easy out. If the connector can't gracefully say no, they ghost. Always include "no worries if not."

How Boomerang automates this

Boomerang's agent (Rudy) drafts this email automatically every time a rep needs a connector ask. The agent uses email + Slack history to write in the connector's voice, includes the forwardable blurb pre-formatted, and routes through Slack or Salesforce for one-click approval. See forwardable email and how to write a warm intro request email for the broader mechanics.

Bottom line

The warm-intro request email is engineered, not improvised. Use this prompt before every connector ask. The acceptance rate difference between an engineered ask and an improvised one is roughly 3x.

Related Glossaries

Related Glossaries

Related Glossaries

Related Glossaries

We value your privacy
We use cookie to improve your experience on our site. By clicking “Accept All Cookies”, you consent to our use of cookies.Privacy Policy for more information.