Sales email templates

Introduction Email Templates

A good introduction email says who you are and why you're writing in the first two lines, then asks for one next step. The 7 templates below cover introducing yourself, taking over an account, asking for a warm intro, making one and adding a colleague.

Template 1 as a Ken Sequence Step

Ken sequence step

Query

Sequence step 1 - Introduction email

Subject
[topic] at {company}
Body preview
I'm the [your role] at [your company], where we help {industry} teams [outcome]. I'm writing because [reason now]. Want me to show you how ...
Variables
{company}, {firstName}, {industry}, {sender_first_name}
You write
[topic], [your role], [your company], [outcome], [reason now]

Template 1 below, "Introduce yourself to a prospect", set up as the first step of a Campaigns sequence.

Use this template in KenAI personalization: 300 credits per 1,000 contacts

When to Use

In short Send an introduction email when someone needs to know who you are before they'll talk to you: a new prospect, a new account or a new person on a deal.

  • You're writing to a prospect for the first time and want to say plainly who you are.
  • You've taken over an account from a colleague and the customer needs to meet you.
  • A mutual contact knows the person you want to reach, and you want a warm intro.
  • You're connecting two people who should talk.
  • A colleague, such as a solutions engineer, is joining the deal.

Templates

In short Copy any of the 7 templates below, replace each [bracketed] part and cut any line that isn't true for you. Ken fills the {firstName}-style variables.

Variables

The templates use Ken's editor syntax. Ken fills {firstName}, {company} and {industry} from each contact and {sender_first_name} from the sending inbox. {{First Line}} is an AI variable. Ken's AI personalization writes it for each contact from the prompt of that name. To cover an empty field, add a fallback after a pipe, such as {firstName|there}. Replace every word in [brackets] with your own before you paste.

Your signature

For cold and other commercial email, put your postal address and a one-line opt-out in the signature under {sender_first_name}, such as "Reply stop and I won't email again." The FTC's CAN-SPAM guide requires both, B2B email included.

Template 1: Introduce yourself to a prospect
Subject: [topic] at {company}

Hey {firstName},

I'm the [your role] at [your company], where we help {industry} teams [outcome]. I'm writing because [reason now].

Want me to show you how it would work at {company}?

{sender_first_name}

Why it works: Who you are and why you're writing now fit in two sentences, so the reader can decide in one skim.

Template 2: Take over an account
Subject: your new contact at [your company]

Hey {firstName},

I'm taking over the {company} account from [previous owner], who has moved to [new role]. I've read your account notes, so you won't have to repeat yourself.

Can we meet on [proposed day] so I can hear what you need this quarter?

{sender_first_name}

Why it works: Saying you've read the history removes the customer's biggest worry about a new account owner.

Template 3: Ask a mutual contact for a warm intro
Subject: intro to [target name]?

Hey {firstName},

Would you introduce me to [target name] at [target company]? I think they'd want to hear about [topic], because [reason].

Please check with them first. If they're open, here's a note you can forward:

{sender_first_name} at [your company] helps {industry} teams [outcome]. They'd like to show you how it works.

{sender_first_name}

Why it works: Asking your contact to check first (a double opt-in) protects their relationship, and the ready-made note makes the favor take a minute.

Template 4: Make an introduction
Subject: intro: [person A] and [person B]

Hi both,

[person A], meet [person B]. [person B] [what person B does], and I think they can help with [topic].

[person B], [person A] [what person A does] and asked me for a name.

I'll let you two take it from here.

{sender_first_name}

Why it works: One line on each person and why they should talk lets both reply without asking you for context.

Template 5: Bring a colleague into the deal
Subject: [colleague name] joining us on [day]

Hey {firstName},

I've asked [colleague name], our [colleague role], to join on [day]. They've set up [topic] for teams like {company} and can answer the [technical area] questions you raised.

Can you send over [document name] before then so they can prepare?

{sender_first_name}

Why it works: Saying why the colleague is joining and what they need to prepare makes the extra person read as help.

Template 6: Reintroduce yourself to a past user
Subject: [your company] at {company}

Hey {firstName},

You used [your company] at [previous company], and I saw you've moved to {company}. I look after accounts in your region, so I wanted to say hello.

If [topic] is on your plate there too, want me to set up an account for your new team?

{sender_first_name}

Why it works: Someone who already used your product needs no pitch, only a reason to bring it to the new team.

Template 7: Introduce yourself to a new leader at a customer
Subject: your team's [product] setup

Hey {firstName},

Welcome to {company}. I'm the account manager for your team's [product] setup, which [usage highlight].

Want me to walk you through how your team uses it today?

{sender_first_name}

Why it works: A new leader inherits your product without context, so a plain hello with their team's usage keeps the account safe.

Timing

In short For a warm intro, reply the day it lands and send one follow-up in the thread if it goes quiet.

Introduction email cadence
DayStepGoal
Day 1Ask your mutual contact (template 3)Get a yes from both sides
The day the intro landsReply, thank your contact and move them to BccOffer two times to meet
3 days later, if no replyOne follow-up in the same threadMake the next step easy to say yes to

Ken's view. Moving the person who introduced you to Bcc lets them see you replied without keeping them in the thread.

Examples

In short 3 filled-in versions for architecture firm, solar installation and physical therapy clinics, all with fictional companies.

Kestrelgate Architects is a fictional company. The account lead at a time-tracking company introduces themselves to the operations partner at a 30-person architecture firm.

Example: Architecture firm
Subject: project hours at Kestrelgate

Hey Elena,

I'm the account lead at a time-tracking company that works with architecture firms on billable hours. I'm writing because Kestrelgate just won the library project, and fixed-fee jobs that size are where unbilled hours pile up.

Want me to show you how it would work at Kestrelgate?

Noah

Corvanne Solar is a fictional company. A new account manager takes over a solar installer's account from a colleague who moved teams.

Example: Solar installation
Subject: your new account manager

Hey Marco,

I'm taking over the Corvanne Solar account from Jess, who has moved to our partnerships team. I've read your account notes, including the permit backlog you raised in May, so you won't have to repeat yourself.

Can we meet on Wednesday so I can hear what you need this quarter?

Iris

Tamberlin Physical Therapy is a fictional company. A consultant connects the billing lead of a clinic group with a peer who fixed the same claims problem, after both said yes.

Example: Physical therapy clinics
Subject: intro: Nadia and Felix

Hi both,

Nadia, meet Felix. Felix runs billing for Tamberlin Physical Therapy's six clinics and is working through a backlog of denied insurance claims.

Felix, Nadia fixed the same problem at her clinic group last year and offered to share what worked.

I'll let you two take it from here.

Dev

Mistakes to Avoid

  • Making the introduction about you. One line on who you are is enough; spend the rest on why you're writing to them now.
  • Asking for a warm intro without letting your contact check first. Ask them to get a yes from the other person, then send the note they can forward.
  • Keeping the person who introduced you on every reply. Thank them and move them to Bcc in your first reply.
  • Ending with no next step. Ask for a meeting, a document or a day, not "let me know if you have questions".
  • Opening with "I hope this email finds you well" or "I came across your profile". Ken's skills reject both as dead phrases.

FAQ

How do you write a sales introduction email?

Say who you are in one line, say why you're writing now in the next and ask for one next step. Keep it under 80 words, following Ken's copy rules.

How do you ask someone for an introduction?

Name the person, give one reason they'd want to talk and ask your contact to check with them first. Include a two-line note your contact can forward as is.

What is a double opt-in introduction?

An introduction where the connector asks both people before connecting them. It protects the connector's relationships and means both sides want the conversation.

How do you introduce yourself as a new account manager?

Name the person you're replacing, say you've read the account history and ask for a meeting on a specific day so the customer can tell you what they need.

How do you reply to an introduction email?

Thank the person who introduced you, move them to Bcc and offer two specific times in the same reply.

Do This in Ken

Send This Sequence in Ken

Run these templates as a Campaigns sequence in Ken. Campaigns finds and qualifies leads, writes personalized email and LinkedIn sequences, and sends them from your outbound inboxes. AI personalization, priced below, can fill the personal lines for each contact.

  1. Create a campaign and paste template 1 as the first email step.
  2. Add the next steps from this page on the days in the timing table.
  3. Replace every [bracketed] part, and add a fallback such as {firstName|there} where a field can be empty.
  4. Add your contacts and launch.
Module
Campaigns
Open in Ken
/waitlist
Cost
AI personalization: 300 credits per 1,000 contacts

The new Ken opens to the waiting list in batches.

Sources

Every source, with the date we checked it
SourceChecked
FTC, CAN-SPAM Act: A Compliance Guide for Business
Ken cold email skills (MIT), email-copywriting and campaign-strategy

Changelog

  1. Page published.