Handle Wrong-Person Replies Without Referral Pressure
Respond to role corrections with a clear no-referral path, verified routing options and upstream record fixes instead of pressuring recipients for introductions.
10/23/20263 min read
A recipient who says they are not the right person has given you useful corrective information. They have not necessarily volunteered to become your researcher or introduce you to a colleague. The appropriate response begins by accepting the correction and reducing the burden on them, not by immediately asking for a name, email address and calendar introduction.
This guide provides a decision path for handling the reply. It does not turn an initial mistaken contact into permission for broader outreach. Review the original purpose, any stated preference and the applicable rules before deciding whether another conversation is appropriate.
Separate three different replies
I no longer handle procurement corrects a role. Please contact our published supplier desk gives a specific route. I am not the right person; stop contacting me includes a restriction. Those statements should not be normalized into the same generic wrong person status.
Record the correction precisely enough that another teammate will not repeat the mistake. Preserve current unknowns: the person may have a different role, but you do not automatically know what it is. There is no need to collect their new responsibilities unless those details are necessary and appropriate for the existing business task.
Worked example: a correction without a referral
Fictional operations adviser Rowan Works contacts a business through an otherwise approved route, believing the recipient oversees warehouse systems. The recipient replies: That moved to another team last year. I cannot help with vendor enquiries.
The completed handling record reads: previous responsibility assumption, incorrect; verified new owner, unknown; referral offered, no; immediate action, acknowledge the correction briefly if a response is appropriate and close the task to this person; research status, reassess whether there is a published vendor route. The team does not ask the recipient to search an organization chart or explain the internal reorganization.
A concise response might say: Thank you for correcting that. I will update our record and will not pursue this with you. It does not promise complete deletion if the organization needs a minimal restriction record, and it does not add a new sales argument. Any data-rights request would follow the relevant privacy process separately.
When a route is explicitly offered
Suppose instead the recipient says that vendor enquiries belong in a public supplier form. Record the exact route and verify that it is the organization's legitimate intake channel before using it. Follow the form's scope. A supplier portal invitation is not permission to email unrelated staff or describe the recipient as endorsing the offer.
If the person offers an introduction, clarify only what is necessary to understand the intended context. Do not write praise or a recommendation in their voice. The new recipient should receive the bounded explanation that was agreed, not a full history of internal notes about the account.
Correct the upstream assumption
Find where the wrong role entered the workflow. It may have come from an outdated profile, a copied account note or a title-based inference. Mark that evidence as superseded or uncertain and update dependent tasks. Merely changing the email draft leaves the same mistake available to other colleagues.
Keep the correction separate from account fit. A relevant company can still have an incorrect contact, and an easy replacement contact does not make a weak-fit company suitable. Decide whether additional research is worth doing based on the business question, not the desire to recover a missed outreach target.
Use a no-referral branch deliberately
A decision tree should contain a valid end state: no appropriate route established, no further action. Without it, every wrong-person response becomes another attempt to obtain access. A respectful process allows the recipient to help less than the seller would like.
Review stop language before creating any new task. The ICO's B2B guidance is relevant to UK contact-data handling, but local requirements and the exact request determine the applicable obligations. The finished record should explain what was corrected, what remains unknown and which actions are no longer appropriate. That is more valuable than a guessed replacement name and a new sequence.