The Redirect-Reply Playbook: Wrong-Person Reply to a Booked Owner Meeting

A prospect has replied "not me, talk to our ops lead", or just "not my area". This playbook is for founders selling their own product, account executives, SDR leads, and partnerships teams who need to turn that reply into a meeting with the person who actually owns the problem. It runs from sorting the reply on Day 0 to one of three end states by Day 10: a booked meeting, a re-mapped account, or a logged close-out. Every stage has a time box and a definition of done.

How common is a wrong-person reply, and what is it worth?

A wrong-person reply is uncommon but not rare. In one study of 1,288,605 cold emails, "wrong person or company" made up 4.1% of human replies, and one single campaign saw 20%. Each one is a live thread with someone inside the account, so it is worth working properly instead of filing it as a rejection.

The figures vary widely because they measure different things:

Two numbers from the sales.co counts give a sense of scale. Wrong-person replies work out to about 0.29 per 1,000 sends, roughly 12% as often as interested replies (0.24% of sends). These are my calculations from the study's own counts.

Three points to keep in mind before you build a process around these numbers:

• The rate tells you about your list, not your message. The 20% campaign blamed its result on "general admin contacts at target companies instead of decision-makers." If your wrong-person rate is climbing, fix the list build first. The copy is probably not the problem.
• Redirect conversion is not published anywhere. The sales.co study counted "referring us to the right person" as an interested reply, so referrals vanish into the headline number. Instantly's benchmark report recommends tracking referral as its own reply category, but does not break its own figures out that way. If you want to know your own redirect-to-meeting rate, you have to tag it yourself (see the final section).
• The 10-30% figure is not a meeting rate. It is the reply rate to an SDR asking "who owns this?" Nobody has published how often a redirected first touch becomes a meeting compared with a cold one.

The four redirect types and how to sort a reply

Every wrong-person reply is one of four types: named person, function only, generic inbox, or a push to procurement or a portal. The type decides your next move, so sort the reply before you write anything back. It takes about five minutes on Day 0.

What each type proves, and how it misleads you

• Named person proves the referrer thinks this person owns the problem. It misleads when the referrer's information is out of date. People change roles faster than they change inboxes, which is why the verification stage exists.
• Function only proves an owner exists. It misleads in a different way: reps log "not my area" as a closed-lost objection, and an account that had an owner looks dead. The test is simple. If the reply contains a function noun (ops, finance, IT, security), it is function only, not a rejection.
• Generic inbox proves only that mail gets routed somewhere. Treat it as a hint about which function to look in. Do not treat it as the owner.
• Procurement or portal is a classic case of process owner versus problem owner. One procurement-side writer puts it this way: "The Process Owner is Procurement (or sometimes IT, Legal)." The person who signs the purchase order is usually not the person whose problem you solve.

If you sequence in Outreach, its sentiment model already labels replies as positive, objection, referral, unsubscribe, or other. It stops at "referral", though, and does not split referrals into these four types. Add your own tag on top so you can tell later which types turn into meetings.

Who owns this at the account after a redirect?

The owner is the person who currently works at the account, holds a title that matches the problem, and has a working mailbox. All three checks have to pass, and they are separate checks. Budget about 15 minutes, on Day 0 or Day 1, before you send the one warm touch you have.

The rule exists because job data goes stale faster than email data:

On top of that, B2B email decays at about 2.1% a month, which compounds to about 22.5% a year. A report from one email verification provider found at least 23% of the addresses it checked were invalid or risky. A name the referrer gives you from memory is probably right about the person, and much less reliably right about what that person does today.

The three checks

1. Current employer. Is the person still at the account? Look for a recent, dated employment record, not a cached profile.
2. Title matches the problem. Does the current title cover what you solve? A "Director of Operations" who has moved to a strategy role still has the old mailbox and no longer owns the problem.
3. Valid mailbox. Does the address accept mail? This check matters, but it is the weakest of the three.

No public source sets out a combined check of how recent the employment record is, whether the role fits, and whether the mailbox works for referred contacts. The order above is my own recommendation. Test it against your own bounce and no-reply data.

What an "ops lead" redirect usually points to

When a referrer at a software company says "talk to our ops lead", the target is usually one person. In Refolk's index of professional profiles, the operations-leader slice for Computer Software is small and spread one per company:

These counts come from one filtered slice of the index (an industry tag plus exact title strings). They are not market sizes. The US has four times as many matches as the UK in this slice. The two UK matches are at Gretel and Playrcart, based in London and Hove. Eight people at eight companies means that inside any one account, "the ops lead" is usually a single person, so the work is confirming who that person is, not choosing from a crowd.

The US title strings show how exact-match searching goes wrong:

Of the six Directors of Operations, four write "of" and two write "Of". If your search tool treats those differently, it misses a third of the most common title. The procurement row is the bigger warning: an exact-title search returned zero US software procurement leaders. One explanation, which I have not verified, is that procurement at smaller software firms sits under other titles. In practice, a procurement deflection cannot be solved with a title search. You have to ask who owns the problem.

This is where describing the person you want, rather than guessing title strings, saves the 15 minutes. With Refolk you can ask for the role, the company profile, and "currently in role" in one sentence, and get people back whose current employment is already part of the match.

What the first referral touch must disclose

The first message to the referred owner has to say where you got their details, identify you, and offer an opt-out. You can name the referrer only if they have given permission. These requirements come from GDPR Article 14, which also sets the deadline: the information is due "at the latest at the time of the first communication to that data subject" when the data is used to contact them.

What Article 14 requires at first contact

The notice has to cover:

• who you are (the controller's identity)
• why you are processing the data and on what legal basis
• the categories of data you hold
• who receives the data
• "from which source the personal data originate, and if applicable, whether it came from publicly accessible sources" (Article 14(2)(f))

The source requirement is the one that shapes this playbook. One compliance guide lists "using vague descriptions like 'third parties'" as a failure. That leaves two compliant options: name the referrer, or name the referrer's function. Naming the referrer needs their permission. That is why the Day 0 reply to the referrer always asks for it.

Handling the referrer's permission

Ask in writing, and take a non-answer as a no. Naming someone without permission can go wrong quickly: the new contact forwards your email to the referrer's manager, and the referrer stops replying, which kills both threads. "A colleague in operations suggested I reach out" meets the source requirement and costs very little warmth.

MESSAGE 1 (Day 0)
Subject: Re: [original subject]

Thanks, [Referrer first name] - that saves us both time.

Two quick questions before I reach out to [Owner name]:
1. OK if I mention you pointed me their way? If you'd rather I didn't, I'll just say a colleague in [function] suggested it.
2. Is [Owner name] still the person who owns [problem] day to day, or has that moved to someone else?

One line back is plenty.

MESSAGE 2 (Day 5 to 6)
Subject: Re: [original subject]

Hi [Referrer first name], I wrote to [Owner name] on [date] and haven't heard back. No action needed on your side unless one of these is true:
- Someone else now owns [problem] - who should I talk to?
- It's not a priority for [Company] right now - I'll close it out.
- They're the right person and just busy - I'll wait.

Subject: [Referrer first name] suggested I reach out about [problem]

Hi [Owner first name],

[Referrer full name] in [function] mentioned you own [problem] at [Company], so I'm writing to you directly.
[No-permission version: A colleague in [function] at [Company] mentioned you own [problem], so I'm writing to you directly.]

[One sentence on the specific problem and what you have seen at similar teams.]

Worth a short call next week?

[Your name], [Your company], [Postal address]

Where I got your details: [Referrer name / a colleague in [function]] pointed me to you, and I confirmed your work email from [public professional profile / company website]. How I handle your data: [privacy notice link]. If this isn't relevant, reply "stop" and I won't email again.

Checking the jurisdiction before you send

Base the jurisdiction check on where the recipient works, not where the company is headquartered. Germany is the one country every source agrees on: its unfair competition law (§7 UWG) treats unsolicited email advertising as unreasonable harassment. Beyond Germany, the sources contradict each other:

• Austria appears under consent (TKG 2021) in one source and under legitimate interest in another.
• One list adds Spain, Italy, Poland, Austria, and Belgium. Another names Austria, Germany, Greece, and Switzerland.
• In the UK, PECR's consent rule does not apply to corporate subscribers, but you must identify yourself and provide an address to opt out.

No regulator source was retrieved for this guide, and whether a colleague's referral counts as consent is not publicly established. Take the lists above as a reason to check, not as the answer, and confirm your position with counsel for each country you send to.

The 10-day redirect procedure

The procedure has nine stages, starting on Day 0 and ending on Day 10 in one of three outcomes: a booked meeting, a re-mapped account, or a logged close-out. Sources disagree on one ordering question. A widely used template guide says to send the referral follow-up within 24 hours, and no ranking page puts verification before the send. My view: verification and the jurisdiction check fit inside that 24 hours, so do them first.

The calendar, laid out:

Where the timings come from, and where they are weak

• Two follow-ups. One practitioner's "Referred to" sequence has two follow-ups after the first touch. The 3 to 5 business-day spacing comes from the template guide's check-in interval.
• The loop-back on Day 5 to 6. No source publishes timing for re-engaging the referrer, or how well it works. I put it after follow-up 1 so the owner has had two chances before you go back to the referrer.
• Day 10 close. No source recommends a time limit before re-mapping an account. The template guide puts a breakup email 7 to 14 days after the last follow-up. I use 10 business days so a redirect cannot sit open indefinitely. Adjust it if your sales cycle is longer.
• Why the first touch carries the most weight. One benchmark found the first email captures 58% of all replies. A referral gives you a warm first touch only once, so verify before you spend it.

What "re-mapped" means on Day 10

If the referrer names someone else, or the owner turns out to be wrong, start again at stage 3 with the new name. If the deflection was to procurement or a portal, ask your contact "who reviews, approves, and signs off on purchases of this size", then confirm the answer by threading two to three contacts. A re-mapped account is one with two to three new verified threads, each with its own cadence. If you are left with no owner and no threads, log a close-out with a reason. Do not leave the account open.

How redirects go wrong: failure modes and false positives

Most redirect failures are false positives: a check seems to pass, the rep goes ahead, and the warm touch is spent on the wrong person or in the wrong way. Each failure below has a specific check that catches it.

A verified inbox can belong to someone who stopped owning the problem months ago.

1. Misclassifying "not my area".

   • What happens: the reply is logged as a closed-lost objection.
   • Why it is false: the account had an owner. The reply just did not name them.
   • Check: any reply containing a function noun is function only, and it goes into the cadence, not the lost pile.

2. Out-of-date employment.

   • What happens: the referrer names someone who has since changed role.
   • Why it is false: title changes run at 65.8% a year, almost twice the 37.3% email-change rate, so the old mailbox still accepts mail.
   • Check: compare the current title against the problem, not just the inbox.

3. Relying on mailbox validation alone.

   • What happens: a valid address is taken to mean "right person".
   • Why it is false: validity says nothing about ownership.
   • Check: run the ownership check separately, as in the matrix above.

4. Vague source disclosure.

   • What happens: the first touch says "I got your details from a third party."
   • Why it is false: it looks like disclosure but fails Article 14(2)(f).
   • Check: name the referrer, or name their function.

5. Naming the referrer without permission.

   • What happens: the owner forwards the email to the referrer's manager, and the referrer goes quiet.
   • Why it matters: you lose both threads, including the loop-back you would need on Day 5.
   • Check: get written permission before stage 5, and take silence as a no.

6. Treating the referral as consent.

   • What happens: a Germany-based owner gets the same send as everyone else.
   • Why it is false: sources say UWG §7 still applies.
   • Check: base the decision on the recipient's location, not the company's headquarters.

7. Attribution lost across CRMs.

   • What happens: the referral link is stored as a HubSpot label, but the stack syncs to Salesforce.
   • Why it is false: labels do not sync, so the link disappears on the Salesforce side.
   • Check: copy the link into a synced property.

8. Pitching procurement as if it owned the problem.

   • What happens: the rep pitches procurement and gets put into a vendor process with no sponsor.
   • Why it is false: procurement runs the process, not the problem.
   • Check: ask who uses the tool and who signs, then thread two to three contacts.

Failures 2 and 3 are the expensive ones because they look like progress. When I find the same failure more than once in a month of redirects, I treat it as a process gap, not a mistake by one rep.

Recording the redirect so credit and suppression survive

Record four things on the same day each happens: the referred-by link between the two contacts, the source you disclosed, the reply disposition, and the opt-out scope. If the link is missing, the referrer gets no credit. If the opt-out scope is missing, someone may email a person who asked you to stop.

What each tool does

• HubSpot. Build "Referred by" as an association label between two contacts. Labels need a Professional or Enterprise subscription and can be set in bulk through import. They are one-to-many by default, and admins can limit them, for example to one contact labelled Billing contact per company. HubSpot's own documentation says association labels do not sync through the HubSpot-Salesforce integration.
• Outreach. The sentiment model labels referral replies automatically. Sequence states include finished (replied), finished (no reply), and opted out, which give you the terminal dispositions on Day 10.
• Salesforce. I did not retrieve documentation for how Salesforce should store a referred-by link, so I cannot describe a native method. Check your org's contact relationship options with your admin.

Opt-out scope

No CRM documents how an opt-out should apply across a referrer and the contact they referred. That is not publicly established. My default: suppress the person who opted out, add a note to the other contact's record, and do not ask the referrer about the topic again without a new reason. Write your rule down so the whole team applies it the same way.

Keeping the redirect motion measurable

Benchmarks fold referrals into "interested", so your own tags are the only source of a redirect-to-meeting rate. Tag every redirect with its type and terminal outcome. Each month, review which types turn into meetings and how often each failure mode came up.

Review these each month:

• Wrong-person rate against list source. If it climbs from the 4.1% of human replies seen in the large study toward the 20% seen in the admin-heavy campaign, rebuild the list before you rewrite the copy.
• Conversion by type. Named-person redirects should convert better than generic-inbox ones. If they do not, look at stage 3 first.
• Loop-back outcomes. Count how often the referrer confirms, forwards, names someone new, or goes quiet. No published figure exists, so your data is the benchmark.
• Close-out reasons. If many accounts end in "no owner found" after a procurement deflection, the re-mapping step needs more threads, not more follow-ups.

Re-mapping is where the time goes. Asking Refolk for "the current head of procurement or vendor management, plus whoever runs operations" at one account gets you the two to three threads in a single request, with no title-string guessing.