You get a response from someone at the company - but it's not the person you originally emailed. Maybe they forwarded your message. Maybe they're replying on behalf of the original contact. Maybe the decision maker left and someone else took over the thread.

Most people panic here. They either ignore the new person, reply awkwardly acknowledging the switch, or worse - they treat it like a dead end and move on.

The reality is simpler: a decision maker change mid-conversation is actually a good sign. It means your email got attention. Now you just need to handle the transition without losing momentum.

Why This Happens (And What It Tells You)

Before you respond, understand what likely happened. The original contact either forwarded your email to someone with actual buying authority, delegated it to someone who handles vendor relationships, or left the company and someone inherited the inbox.

All three scenarios are positives - it means your message broke through the noise and got routed to the right place. The risk is fumbling the handoff.

The Response Structure That Works

Don't acknowledge the change like it's awkward. Don't pretend you expected this person. Just answer their question directly and move forward as if they were your target contact all along.

Your response should follow this structure:

Let me show you what this looks like in practice.

Let's say you originally emailed Sarah (VP of Operations) about improving their incident response process. Sarah forwarded it to Mike (the actual head of security) with "thoughts?" and Mike replies asking how long implementation typically takes.

Here's the wrong response:

Hi Mike, Thanks for jumping in on this - I appreciate Sarah looping you in. Implementation usually takes 3-4 weeks depending on your environment. Happy to answer any other questions. Best, John

This is awkward and signals you're confused about who the decision maker is. Now try this instead:

Hi Mike, Implementation usually runs 3-4 weeks. We handle all the heavy lifting on our side - your team mostly reviews the plan and gives feedback on their specific workflow. If that timeline works, I'd like to send over a couple questions about your current setup so we can nail down what week 1 looks like. Does Thursday or Friday work for a quick 20-minute call? John

This approach does three things right: it answers the question directly, doesn't make the conversation weird by acknowledging the switch, and moves immediately toward a concrete next step. Mike becomes your contact now. That's it.

The Critical Detail: Don't Ask Clarifying Questions

A common mistake is using the response to confirm who you're talking to or what they do.

Hi Mike, Thanks for your interest. Just to clarify - are you the decision maker on security tools? Or are you reviewing this for Sarah? Looking forward to hearing from you.

This kills the conversation. You've just made it feel like work for Mike. He has to explain his role and justify his involvement. Instead, assume he's there for a reason and move forward.

The One Exception: When They're Asking You to Follow Up With Someone Else

Sometimes the new person replies saying something like "Thanks - actually, you should talk to David about this." This is different. They're not taking ownership; they're directing you elsewhere.

In this case, your response is short:

Got it - I'll loop David in. Do you want me to CC you on that email, or should I reach out to David directly? Thanks, John

This shows respect for their time and keeps everyone in the loop if they want to stay informed. If they say "reach out to David directly," you've just qualified a warm introduction because Mike clearly told David you'd be calling.

Timing and Tone Matter More Than You Think

Respond within 4 hours if possible. A decision maker change in email can lose momentum fast if you let it sit. The person who forwarded it or took over the conversation is typically at peak interest right then.

Keep your tone conversational and slightly faster-paced than your original cold email. You're no longer breaking through noise - you're moving a conversation forward. Short sentences. Direct language. No fluff.

The Multithreading Angle

If you've been running multithreading to multiple contacts at the same company, a decision maker change becomes even more valuable. You now have confirmation that your original contact was in the right company, in the right department, and that people are talking about your offer.

If you've been reaching out to other people in the org, don't suddenly stop. Keep those other sequences going but adjust the tone slightly - you can reference that you're already in conversation with Mike's team: "I see you're connected with Mike over there - he's been asking some great questions about implementation timeline."

What This Means for Your Campaign

Track these conversations separately. A decision maker change in the middle of your sequence isn't a bounce or a rejection - it's advancement. Mark it as such in your follow-up notes.

The biggest mistake is treating the new person like a fresh lead. They're not. They're a warmer conversation than your original cold email. Act like it.

When You Need This Running at Scale

Knowing the framework is one thing. Actually executing it while managing 50+ conversations, tracking who the real decision maker is at each company, and handling the dozen other variations of decision maker changes that happen across a campaign - that's different.

Most agencies that handle cold email campaigns build systems specifically for this so responses don't get lost in the chaos and every conversation moves forward instead of stalling when a new person shows up. If you're running your own sequences and noticing decision maker changes are slowing you down, that gap between knowing what to do and having it actually done well at scale is worth paying attention to.

Related Guides