How agencies route wrong-person replies into a find-someone-else path without restarting the campaign

"I'm not the right person" is not a closed-lost. It is a handoff signal with a clock on it.

Agencies that run multi-client outbound still waste these replies. The sequence stops (good), someone tags "negative," and the account dies. Growtoro's referral write-up calls that out directly: a named handoff from inside the account is warmer than another cold first touch, and most teams treat it like a polite no.

ConnectSafely's 2026 reply taxonomy puts wrong-person in its own bucket with a pivot action, not a hard suppress. The GTM Lab's reply-classification piece says the same: extract the referred contact and open warm outreach. Dobble and 30 Minutes to President's Club both push for a name drop ask, not a demand that the stranger write a formal intro.

Stop the thread, keep the campaign

On a wrong-person reply inside a client-isolated workspace:

1. Stop the live sequence on that contact. Sequences must stop on reply. Do not keep nudging someone who already said they are the wrong seat.
2. Classify the reply as wrong-person / referral, not hard unsubscribe, unless they also asked to be removed.
3. Suppress the original contact for this campaign so find/qualify does not re-pick them next week.
4. Capture any named referral, title, or team hint into the prospect record with a source note.
5. Ask once, politely, for permission to mention them when you reach out. Growtoro and ConnectSafely both treat that 30-second ask as the highest-leverage message in the exchange.

If they give no name, one short follow-up asking who owns the function is fair. If they decline or go silent, treat it as a soft close. Do not restart the cold cadence on them.

Open find/qualify for the referred seat, not a cold restart

The mistake is dumping the referred contact into step one of the same cold sequence. Growtoro is blunt: warm intros need a tighter, more direct ask. 30MPC's cold-call framing is useful in writing too. Ask for the name drop, not a full referral email from a stranger.

Agency ops pattern that holds up:

• Create or match the referred contact in the client workspace with provenance that names the referrer and the original campaign.
• Write a fresh first touch that leads with the referrer, the topic they flagged, and one clear ask.
• Keep the original account on the campaign, but shift the active contact. Do not clone a brand-new campaign just because the seat changed.
• Log a reason code so weekly scorecards separate wrong-person yield from true positives.
• Time the new touch inside the client's send window the same day when you can. Referral goodwill cools fast.

Do not CC the referrer on a recycled cold email. Do not invent a title for the new contact if enrichment is empty. Write from evidence or ask a clarifying question.

GTM runs find → qualify → write → send/reply/book inside client-isolated workspaces, with a compliance gate before send and sequences that stop on reply. Wrong-person handling is the reply step feeding find again without nuking the campaign.

If you want reply triage and warm-handoff paths built into the outbound motion, join the waitlist.