CC in cold email and when to loop in the decision maker

You write a cold email to the VP. Good subject line, tight copy, clear ask. Three days later, nothing. The person who actually owns that problem, the one who’d forward it to their boss with “we should look at this,” never saw it.

That’s the gap. One field fixes it, and it’s not the body copy or the subject line. It’s who you put in To and who you put in CC.

In this post, I’ll show you exactly how cc in cold email works, who belongs in each field, and why the order matters more than most reps think. lemlist internal data shows a first email to the doer with the decision maker in CC replies at 3.35%, 23% higher than a single recipient. I’ll break down the mechanics behind that number, the mistakes that kill it, and how to set it up without turning your email into a group blast.

Why a CC changes how a cold email is read

A CC turns a one-to-one cold email into a team conversation, and that shift changes who pays attention. When the person who runs the topic sees their boss copied, the email moves from “random vendor pitch” to “something my manager might ask me about.”

Here’s what happens mechanically. The doer feels accountable because a senior person can see whether they respond. The decision maker sees the email is about a real problem their team owns, which makes it easier to forward or reply than to ignore. And both people know the other might answer first, which creates a small but real pull toward action.

The data backs this up. According to lemlist internal data, a first email sent to the doer with the decision maker in CC replies at 3.35%, which is 23% higher than the 2.72% average for a single-recipient cold email. That gap comes from one field in your email. No new copy, no new offer, no extra research.

Who goes in To and who goes in CC

The rule is simple: the person who runs the topic goes in To, the decision maker goes in CC.

“Runs the topic” means the person who would evaluate your product, own the workflow you improve, or feel the pain you solve daily. That’s usually a manager or senior individual contributor. Think Head of Demand Gen, Sales Ops Manager, or Staff Engineer. The decision maker is one level up: the VP, Director, or founder who signs off on budget.

You can identify both by looking at the org chart. The To recipient has a title that matches the function you sell into. The CC recipient manages that function or the department above it. If you need a framework for mapping these roles, building a buyer persona is the right starting point.

Why this order and not the reverse? lemlist internal data shows VPs reply 40% more when their team is in the loop: 3.5% compared to 2.5% when they receive the email alone. Sending directly to the VP without context from their team is the exact pattern that gets ignored. Put the VP in CC, and they see the email is relevant to someone they manage. That’s a reason to care.

How many people to include

Two people is the sweet spot. Add a third and the lift disappears.

Source: lemlist internal data

The doer plus decision maker combination wins because the roles are complementary. Two peers from the same team still outperform a single recipient, but the dynamic is weaker since neither person has authority over the other. Once you add a third person, the email starts to feel like a group blast. Nobody feels personally responsible, and the reply rate drops below the single-recipient average.

Keep it to two. One in To, one in CC.

How to write an email to two people

Your email needs to acknowledge both recipients without reading like a committee memo. Here’s the structure.

Open with both names. “Hi Sarah, hi Mark” works. One line should explain why both are included. Something like “looping you both since Sarah runs demand gen ops and Mark oversees the pipeline targets.” That single sentence justifies the CC and prevents the “why am I on this?” reaction.

Then frame the problem for the team, not for one person. The pain point should be something both roles recognize. Follow it with one proof point: a result, a metric, or a customer example that makes the claim concrete.

Close with a question either person can answer. Avoid asking something only the To recipient would know, because that makes the CC feel pointless. A question like “is this on your radar for Q3?” works for both a manager and their VP.

Keep the email short. No links, no attachments, no paragraphs longer than two sentences. The cold email structure guide covers the mechanics of keeping copy tight.

Mistakes that make a CC backfire

• •

  CCing someone who has no connection to the topic you’re writing about

• •

  CCing a CEO purely to apply pressure on a mid-level contact

• •

  Putting five people in CC so the email looks like an internal thread

• •

  Giving no reason for the CC, leaving both recipients confused about why the other is there

• •

  Dropping one recipient from follow-ups without explanation, which makes the thread feel broken

Every one of these turns the CC from a credibility signal into a red flag. The recipient assumes you don’t understand how their team works, and the email gets deleted.

Follow-ups when two people are in the loop

Keep both recipients on every follow-up. Removing one person mid-sequence looks sloppy, and the remaining recipient will notice.

Adapt the angle for each role. Your first follow-up might lean into the operational pain the doer feels. The second might reference a business outcome the decision maker cares about. You’re writing to one thread, but you’re speaking to two sets of priorities. If you need a starting point, these follow-up email templates cover the most common angles.

When one person replies, stop the sequence for both. A reply from either recipient means the thread is alive. Continuing to follow up with the other person creates an awkward parallel conversation. If you’re running multichannel sequences, the same rule applies across channels: one reply pauses everything.

The least used lever in outbound

According to lemlist internal data, only 2.4% of campaigns use lemlist’s CC field. That makes it the least used lever we track.

I get why. Most reps build sequences around a single contact per account. Adding a second person means finding a second email, writing copy that works for two roles, and thinking about who goes where. It’s more work upfront.

But the data says that work pays off. A 23% lift in reply rate from a single field change is hard to find anywhere else in outbound. No subject line test, no send-time optimization, no personalization variable delivers that kind of gap on its own.

The way to test it: pick one segment where you already know the doer and the decision maker. Run the CC version against your current single-recipient sequence. Judge it on replies, nothing else. If the lift holds, expand to more segments.

How to CC a second stakeholder in lemlist

lemlist has a CC field built into email steps. You add the second stakeholder’s email address per lead, and every email in that step goes out with the CC included.

Finding both contacts is straightforward. The lead database holds 650M+ contacts across 65M+ companies, so you can search for the doer and the decision maker at the same account. Waterfall enrichment across 14+ providers verifies both email addresses before your sequence starts.

When either recipient replies, lemlist stops the sequence automatically. No manual pausing, no risk of sending a follow-up after someone already responded.

To validate the approach, use A/B testing on a single email step. Version A sends to the doer only. Version B sends to the doer with the decision maker in CC. Reply rate decides the winner. Once you have enough data, you scale the winning version across the campaign.

Final takeaway

The CC field is the simplest change you can make to a cold email, and it’s the one almost nobody uses. Put the person who runs the topic in To, the decision maker in CC, and keep it to two people. lemlist internal data shows a 23% lift in replies from that one adjustment.

Build your first signal-based sequence in lemlist.