Skip to content
Email template

Mutual connection cold email template

Convert a shared relationship into instant trust so the prospect reads your email as a warm referral, not a cold pitch.

  • Email
  • Cold outreach
The template
Subject
{{mutual_name}} suggested I reach out
Body
Hi {{first_name}},

{{mutual_name}} mentioned you're the right person to talk to about {{topic}} at {{company}} — we worked together on {{shared_context}}.

The short version: we help {{role}} teams {{outcome}}. {{mutual_name}} thought it might be relevant given {{reason}}.

Happy to share more, or if it's easier, a quick 15-minute call next week. Whatever works for you.

{{your_name}}

Replace the {{merge_tags}}with the recipient’s details before sending. In Autocloz, these fields fill in automatically from each lead’s record.

When to use it

Use whenever you have a genuine shared connection — a mutual contact, a former colleague, or someone who actually pointed you to the prospect. Never fabricate the connection.

Why it works

The structural reasons this message earns replies.

  • A real referral borrows the trust the prospect already has in the mutual contact, which makes a reply far more likely than a cold pitch.

  • Naming the shared context proves the connection is real, not a name-drop, which protects your credibility.

  • It defers to the prospect's preference (email or call), signalling respect rather than pressure.

How to personalize it

A template only works once it sounds like it was written for one person. Do these before you send.

Only use this if the connection is genuine and the mutual contact knows you are reaching out — a false referral destroys two relationships at once.

Replace {{shared_context}} with the specific project or relationship so the prospect can verify it instantly.

Ask your mutual contact for one detail about why the prospect would care, and weave it into {{reason}}.

Variations worth testing

Forwarded-intro request

Instead of name-dropping, ask the mutual contact to forward a short note. This is the cleanest version when the connection is real but not close.

Hi {{mutual_name}},

Would you be comfortable forwarding this to {{first_name}} at {{company}}?

"{{your_name}} runs {{company_name}}; they help {{role}} teams {{outcome}}. Thought it might be useful given {{reason}}."

No pressure either way. Thank you.

{{your_name}}

Former-colleague version

For when the shared context is a past employer or project. It names the overlap first so the prospect can place you.

Hi {{first_name}},

We overlapped at {{shared_employer}} (I was on {{your_team}}), and {{mutual_name}} mentioned you now run {{topic}} at {{company}}.

We help teams like yours {{outcome}}. Worth a catch-up call?

{{your_name}}

What the follow-up sequence looks like

Suggested follow-up cadence for the mutual connection cold email template: day 0 Email, referral email; day 2 LinkedIn, connect, mention the mutual; day 5 Email, one-line follow-up; day 9 Call, call referencing the intro.
  1. Day 0, Email: Referral email
  2. Day 2, LinkedIn: Connect, mention the mutual
  3. Day 5, Email: One-line follow-up
  4. Day 9, Call: Call referencing the intro

Warm referrals need fewer touches than cold outreach. Four is plenty; after that you risk embarrassing the person who referred you. Tell your mutual contact how it went either way, and use the referral request template when you want to ask a customer for the next introduction.

Deliverability and compliance notes

Naming a third party in a subject line is only honest if that person actually suggested the contact. A fabricated referral is a misleading header in spirit, and under CAN-SPAM a deceptive subject line is a violation in its own right. Get the mutual contact's permission in writing, even a one-line message.

Referral emails usually go to a single person rather than a list, which helps deliverability, but keep them on your normal outreach domain and include your postal address and an opt-out line like any other commercial message. Our cold outreach mistakes article covers the reputation side of name-dropping.

General information, not legal advice. Check the rules that apply where your recipients are.

How to run it in Autocloz

Record the mutual contact as a field on the lead (for example mutual_name and shared_context) so the subject and first line fill correctly. For a handful of referrals you can send directly from the lead record; for a steady flow, a small campaign keeps the follow-ups on schedule.

Log the introducer on the lead's timeline as a note so whoever works the deal later knows where it came from. The CRM is free for up to three users, which covers most founder-led referral selling.

Related templates

Frequently asked

Should I tell the mutual contact before using their name?

Always. Ask permission first. If your prospect circles back to verify and the connection looks blindsided, you lose both relationships. A quick heads-up keeps everyone aligned.

What if the connection is loose — just a shared group or event?

Be honest about how loose it is. "We're both in {{group}}" is fine as long as you don't imply a closer relationship than exists. Authenticity is the whole point of this angle.

Does this work on LinkedIn too?

Yes — a mutual-connection angle is one of the strongest LinkedIn opening lines. See the LinkedIn connection request template for a version sized for a connection note.

Send templates like this at scale — start free

Personalize with merge tags, sequence across email, calling, LinkedIn, SMS and WhatsApp, and track every reply — on a free-forever CRM for 3 users.