How to Write an Introduction Email Using AI

The Two-Yes Intro, Explained

The Two-Yes Intro is the rule that an introduction email is never drafted until both people have said yes privately — and that the email itself runs one short paragraph per yes, so each side immediately sees why the other agreed.

Two yeses in, two paragraphs out. That’s the whole method, and it’s the approach we teach at PromptPeakAI for any email where you’re standing between two people who don’t know each other.

• The first yes is etiquette, and it predates AI by decades.
• The second half is where writing an introduction email using AI actually earns its keep — because two yeses leave you holding exactly the raw material a model needs to be specific.

Skip the asking and no prompt will save you. A model given nothing concrete writes something polite and empty, which is precisely the email nobody answers.

Ask Before You Introduce Anyone

Ask both people privately before you connect them. That single step is what separates an introduction people thank you for from one they quietly resent.

The version to avoid has a name: the single opt-in intro, where you email both people at once and let them work it out. It feels efficient. What it actually does is hand two busy adults a social obligation they never agreed to, in public, with you watching.

What a Permission Note Says

Keep each note to three lines. Who the other person is, why you thought of them, and an easy exit.

That last clause matters more than it looks. “Totally fine either way” is what makes a no cheap. Without it, people say yes out of politeness and then never reply, which costs you more credibility than the no would have.

You are helping me ask two people, separately, whether they want to be introduced to each other.

PERSON A: [name], [role at company]. Concrete detail: [one specific fact].
PERSON B: [name], [role at company]. Concrete detail: [one specific fact].
WHY THEM: [in one sentence, why these two should talk].

Write TWO separate short emails, one addressed to each person, describing the other.

Each email must:
- Run three sentences or fewer
- Name the other person and their one concrete detail
- Say in one line why I thought of them
- End with an easy way to decline, phrased so that saying no costs them nothing

Constraints:
- Do not mention that I am also asking the other person
- No flattery adjectives
- Plain and warm, the way a colleague actually writes

Use AI for these notes if you want, but honestly, they’re short enough to type yourself. The AI earns its keep on the joint email, where you need two people framed accurately in very few words.

When One Side Says No

Drop it, and tell the other person nothing beyond “the timing isn’t right on their end.” No explanation, no apology, no second attempt in a month. The person who said no trusted you with an honest answer; protecting that is worth more than any single connection.

Give the AI the Right Details First

A generic introduction email is almost always a briefing problem, not a writing problem. The model didn’t have anything specific to say, so it said something warm and empty.

Before you open a chat, collect five things. Most of them you already have from the permission notes you just sent.

• Names and roles for both people, written the way they’d write them.
• One concrete fact each — a project shipped, a team size, a specialism. Not an adjective.
• The reason they should talk, in your own words, even if it’s clumsy.
• Who asked for what — one person usually wants something, and the email should reflect that honestly.
• Who moves first after you send it.

If you’re introducing someone to a client or prospect you don’t know well, five minutes of research on the other person using AI will give you the concrete fact you’re missing. And if you keep a professional bio on hand, the “one concrete fact” for your own side is already written.

A Prompt That Holds the Shape

Left alone, most models return five friendly paragraphs. The constraint lines at the bottom of this prompt are what keep it to two.

You are helping me write an introduction email connecting two people who have each already agreed to the introduction.

PERSON A: [name], [role at company]. Concrete detail: [one specific fact — a project, a team size, a specialism].
PERSON B: [name], [role at company]. Concrete detail: [one specific fact].
WHY THEM: [in one sentence, why these two should talk].
WHO ASKED: [which person requested the intro, or "mutual" if neither did].
FIRST MOVE: [who should reply first and what they should propose].

Write the email with:
- A subject line in the format "Intro: [Name A] <> [Name B]"
- Exactly two short body paragraphs, one introducing each person
- One closing line naming who replies first
- A warm but plain tone, the way a busy professional actually writes

Constraints:
- Keep the whole body under 120 words
- Use only the facts I gave you. Do not invent achievements, shared interests, or history between them
- No flattery adjectives. No "I'm excited to connect you two"

Why Two Paragraphs Beats Five

One paragraph per person. That’s the structure, and the reason is practical rather than stylistic: each recipient should be able to find their own sentence instantly, and read the other person’s in the next four seconds.

A five-paragraph introduction buries that. By the time someone reaches the reason they’re reading, they’ve scrolled — and the email that gets scrolled is the email that gets archived with good intentions.

The Line Everyone Forgets

Name who replies first. “Dan, you’re the one with the calendar gap this week — over to you.” Without it, both people wait for the other, and a perfectly good introduction dies of mutual politeness.

Then step out. Move yourself to BCC on the send, or say plainly that you’re dropping off the thread. Staying in a CC you don’t need turns every future reply into a performance for an audience.

Writing an Introduction Email Using AI, Start to Finish

Here’s the whole thing on a real-shaped scenario: you’re an ops manager, and a vendor you trust could solve a problem a peer at another company mentioned last month.

Two separate emails, three lines each, sent the same afternoon. Both come back yes within a day. You now have four usable facts — two roles and two concrete details — that you didn’t have yesterday.

Paste the prompt from the previous section, swap the bracketed slots for your five details, and send it. The first draft is usually close. Read it once for accuracy, not for style.

Change something. One phrase in your own voice stops a well-formed email from reading like a template — and both these people know how you write.

If either person doesn’t reply within a week, that’s a nudge, not a failure — the same follow-up email structure works here, aimed at whoever was supposed to move first. Building this kind of thing into a repeatable habit is the point of networking with AI rather than treating each intro as a one-off. Our free AI work templates include prompt formats built the same way.

Which AI Tool Fits This Job

All three major assistants handle this on their free plan. The only meaningful difference is where you can write — inside your inbox, or in a separate tab.

According to OpenAI’s plan page, the free ChatGPT tier includes unlimited text chats, which is far more than this task needs. Claude’s free tier covers the same ground and lets you save the prompt into a project you can reopen.

Gemini is the one with a wrinkle worth knowing. The free Gemini app will write the email happily — but drafting directly inside Gmail is listed on Google’s subscriptions page as a Google AI Plus feature, starting at $4.99 a month. If you want Gemini working inside Gmail, that’s the gate. Otherwise, draft in the app and paste across — it costs you ten seconds.

What You Can Safely Paste

You’re about to put someone else’s name, employer, and a detail they told you into a chat window. Worth thirty seconds of thought, especially if either person is a client.

Use initials or a generic role in the prompt and swap the real names back in when you paste the draft into your email client. It takes seconds. If you’re going further and wiring an assistant into your actual mailbox, read up on connecting AI to your email safely first.

When the Draft Comes Back Wrong

Three failure modes account for nearly everything that goes wrong here, and each has a one-line fix.

Here’s what most guides get wrong: they treat the generic-sounding draft as a prompt-engineering problem and hand you a longer, cleverer prompt. It isn’t. It’s an input problem. A model given “Maya is great” will write filler, because filler is the only honest output available to it.

When the facts are there and the draft is still bloated, one follow-up message fixes it without starting over.

Rewrite the introduction email below so that it is:
- Exactly two body paragraphs, one per person
- Under 120 words in total, not counting the subject line
- Closed with one sentence naming [name] as the person who replies first

Cut in this order: flattery adjectives, background context neither person asked for, any sentence about how I know them, and anything describing the connection as exciting or valuable.

Do not add any fact that is not already in the draft.

DRAFT:
[paste the draft here]

Introducing Two People vs. Introducing Yourself

Two different emails share the name “introduction email,” and mixing them up is why so much advice on this feels beside the point.

Everything above covers the connector version — you know both people, they don’t know each other. The other version is a self-introduction, where you’re reaching out to one person who doesn’t know you at all. No permission step exists there, because nobody has agreed to anything.

A self-introduction carries a burden the connector version doesn’t: you have to earn the reply yourself, by naming the specific thing that prompted you and making one small ask.

You are helping me write a short self-introduction email to someone who does not know me.

ME: [your name], [role at company].
THEM: [their name], [their role at company].
WHAT PROMPTED THIS: [the specific article, talk, mutual contact, or event that made me reach out].
MY ASK: [one small, specific request — a 20-minute call, a question answered, a pointer].
WHY THEY'D CARE: [what is genuinely in it for them, or "nothing yet" if that's honest].

Write it as:
- A subject line under 8 words
- Two short paragraphs: who I am and what prompted this, then the ask
- Under 100 words total

Constraints:
- Do not open with "I hope this email finds you well"
- No flattery. Reference only the specific thing I named above
- Make the ask easy to decline

Neither of these is a cold sales email, which is a third thing again with its own rules — if that’s what you’re actually writing, the cold email approach is a better fit. And an onboarding welcome message for a new hire is a fourth, since that audience already knows they’re joining.

Making This a Habit, Not an Event

The Two-Yes Intro is worth keeping because the discipline outlives any particular tool. Save the prompts somewhere you’ll find them — a saved project in your assistant, a note app, wherever your other outreach templates live.

Most people who are known as good connectors aren’t doing anything elaborate. They ask first, they keep it short, and they name who moves next. The AI just removes the friction that used to make them put it off until Friday.