Agency Cold Email: How to Reach the Right Person

“This isn’t my area” does not necessarily mean your agency’s cold email campaign has failed. It does not signal buying interest, either. It gives you a small piece of information about how the target company works. Your next message can clarify that information—or create enough extra work for the recipient to end the conversation. The difference usually comes down to describing the responsibility you are looking for and asking a question that is easy to answer.

This article follows a hypothetical demand generation agency approaching B2B software companies. All company names, people, messages and developments in the example are fictional; they are not customer results or performance evidence. The scenario shows how to handle a reply from the wrong department, narrow your research and record a referral accurately in campaign reporting.

The first mistake: A suitable company does not mean a suitable contact

In our hypothetical example, Northline Agency wanted to work with companies selling subscription software to business customers. Its offer combined paid acquisition, content and lifecycle marketing, with measurement connecting demand generation to sales opportunities. The ideal customer profile looked reasonable: B2B software companies with sales teams, demo requests and plans to develop their marketing. The problem was that contact selection received less attention than company selection.

At a fictional target account, CedarStack, the team found contact details for Alex, a corporate communications manager. Alex’s title and involvement in public marketing activity seemed like enough evidence of relevance. The first email discussed advertising performance, demo conversion and visibility into customer acquisition cost, or CAC. Alex, however, handled media relations, event communications and brand messaging. Demand generation budgets sat elsewhere.

Alex replied: “Thanks, but this isn’t something I look after.” Northline’s account manager initially considered explaining the offer in more detail. Perhaps mentioning content production would reveal some common ground. But that would overlook the boundary Alex had just stated. An overlap between communications and part of the agency’s service did not make Alex the owner of the proposed project.

The team’s first lesson was to assess account fit and contact fit separately. CedarStack could still be a suitable account while Alex was the wrong person for this particular offer. Keeping that distinction prevents you from discarding an entire company because one employee is not responsible. It also helps you treat that employee as someone who has provided useful information, rather than an obstacle to persuade.

Northline kept CedarStack on its account research list and recorded that Alex was outside the scope of this offer. It also stopped the original follow-up sequence for Alex. That simple operational step mattered: further research could continue without sending reminders that ignored the reply already received.

Read the reply carefully: Responsibility, timing and refusal are different

Previously, Northline had grouped most short, non-positive replies together. But “I don’t handle this,” “We don’t need this right now” and “Please don’t contact us again” carry different meanings. The first concerns responsibility; the second may concern need or timing; the third states a preference to stop contact. Treating them as one follow-up category weakens both reporting and the recipient’s experience.

Alex had not made an explicit purchasing decision on behalf of CedarStack. Nor had Alex invited the agency to contact someone else. The only established fact was that this person did not own the area in question. Northline therefore recorded a responsibility mismatch, rather than a lost opportunity or an interested lead, and kept its next step narrow.

Avoid reading more into a reply than its wording supports. “Procurement handles suppliers” may describe vendor administration rather than ownership of the underlying business need. “Try marketing” identifies a department, but does not establish that any particular employee wants to hear from you. Preserve those distinctions in your research notes.

Northline used three short fields: the recipient’s exact wording, what that wording established and what remained unknown. For Alex’s reply, the outstanding question was: “Who owns demo demand generation and its conversion into sales opportunities?” This prevented internal interpretations from gradually becoming accepted as verified facts.

An explicit request to stop contact calls for a different response. Apply the request to the relevant records and follow your process for its stated scope. Do not try to get around a company-level refusal by approaching employees one after another. Asking for direction is a way to clarify responsibility when appropriate; it should never be used to bypass a clear preference.

The second message had one job: Clarify who owns the work

Northline’s first draft opened with another long explanation of its services. It then asked Alex for the right person’s name, email address, availability and current agency arrangements. For someone who had expressed no buying interest, that was a research assignment. The team reduced the message to one question.

Hypothetical reply to Alex: “Hi Alex, thanks for clarifying. Which team at CedarStack owns demo demand generation and the conversion of those enquiries into sales opportunities? A team name is enough—I can research the relevant person from there. Thanks.”

The question described a business responsibility instead of asking broadly who was “in charge of marketing.” It did not request private contact details, an introduction or meeting availability. Alex could answer with a department name, leaving the agency responsible for the remaining research.

In the scenario, Alex replied: “The Growth team handles that. Jordan would be the person to speak to.” This narrowed the search; it was not a sales success. Northline thanked Alex and closed that exchange. It did not automatically copy Alex into subsequent messages. Sharing a name does not imply a wish to stay involved in every conversation that follows.

Short drafts for different replies

If the recipient only says you have reached the wrong department, a suitable hypothetical response is: “Thanks for letting me know. Which team evaluates the quality of demo enquiries from paid channels? Just the department name would help.” Adapt the responsibility to your actual offer. An agency selling content operations support might ask who owns content planning and distribution.

If the recipient has already identified a team, there may be no need for another question: “Thanks for pointing me towards the Growth team. I’ll research the relevant role from here.” If they explicitly offer to forward your message, provide a short, self-contained summary. Keep the task proportionate to the help they offered.

If your question receives no answer, silence does not justify a fresh sequence of reminders to that person. Northline receives a reply in this fictional example; your campaign may not. You can continue appropriate research using public business information without treating the original recipient as your internal company guide.

A name is a research lead, not proof of decision-making authority

Once Jordan’s name appeared, the account manager wanted to send a new email immediately. A colleague suggested one more check: What was Jordan’s current role, and which parts of the proposed work did it cover? Growth, performance marketing, product marketing and marketing operations can report to different people. A title alone does not establish budget authority or responsibility for selecting an agency.

Northline compared CedarStack’s public team information, current professional profiles on LinkedIn and relevant job listings. In this hypothetical research, Jordan appeared to lead growth activity, while marketing operations covered CRM reporting. The job descriptions offered clues about the organisation, but an open role’s responsibilities did not prove the authority of existing employees.

The team created a simple responsibility map rather than assigning one broad “decision-maker” label. Jordan was a plausible first contact for discussing demand generation. Marketing operations might need to assess measurement and data access. Budget approval remained unknown. Separating the problem owner, implementation stakeholders and budget approver keeps the first conversation focused.

Source and date notes were useful here. An old conference biography might describe someone’s previous employer. Similar names or related companies can also create false matches. Check role information against the current company context, and avoid presenting unconfirmed details as facts in your message.

Finding an email address is a separate task. A technically usable address does not establish that its owner is responsible for your topic. Identifying the right person does not establish that an address is current. Optional email verification can help reduce technical uncertainty, but it cannot confirm authority, establish contact preferences or guarantee delivery.

The research goal was now specific: gather enough evidence to approach someone who could assess the relevant business problem. Northline did not need a directory of everyone at CedarStack. A clear stopping point helped contain preparation time and reduced the temptation to contact multiple employees simultaneously.

Describe the referral without turning it into an endorsement

The most sensitive part of Jordan’s email was how to mention Alex. “Alex strongly recommended that we meet” would overstate the exchange. Alex had identified a team and a person, without assessing the agency, endorsing its services or promising a meeting. The new message needed to preserve that limited context.

Hypothetical email to Jordan: “Hi Jordan, Alex mentioned that Growth handles demo demand generation and suggested you were the relevant person to contact. Looking at CedarStack’s public demo request process, I was interested in how your team evaluates acquisition channels alongside sales opportunity quality. Our agency helps B2B teams plan paid acquisition and content around that measurement. If this sits with you, would it be useful if I sent three short questions to see whether our approach is relevant?”

The message did not diagnose CedarStack’s internal performance. It made no claim to know the company’s CAC, conversion rates or attribution gaps. It used a public observation to frame a question. Personalisation should reflect what you actually know; it should not turn an unseen problem into a confident assertion.

In this fictional exchange, Jordan confirmed responsibility for channel reporting and said the company was not evaluating new agencies. Jordan was nevertheless open to receiving the three questions. Northline recorded those as separate facts and sent a brief reply: How far into the sales process do you track channel performance? How do you define opportunity quality? Do marketing and sales use the same source information?

The questions were intended to establish whether the offer matched a relevant need. They did not make the exchange a meeting opportunity. If Jordan had declined further contact, the conversation would have ended. If the answers revealed an area worth exploring, that would require a separate qualification step.

The scenario’s progress remained limited: the agency had reached someone responsible for the relevant work, learned the current buying position and clarified the context for its offer. There was still no meeting, budget approval or sale. Recording those limits keeps both the narrative and the campaign report credible.

Update the records so follow-ups reflect the conversation

Northline’s main operational risk was allowing Alex’s original sequence to keep running. Sending “Did you see my last email?” after receiving a clear reply would suggest that nobody had read it. The team therefore defined how a human reply should pause automated follow-up and prompt a review of the contact and account records.

Contact status remained separate from account status. Alex was the wrong contact for this offer. CedarStack remained an account under research. Jordan had confirmed responsibility but had not expressed active buying interest. Without those distinctions, Alex’s reply could incorrectly close the whole account, or Jordan’s response could be counted prematurely as an opportunity.

A practical starting record included:

• The meaning of the initial reply and any request to stop contact.
• The exact referral wording and the team or person identified.
• The source and date of the new contact’s role information, plus any unresolved responsibility questions.
• One account follow-up owner, the latest contact and the reason for the next step.

Assigning one follow-up owner is particularly useful in agencies. Researchers, account managers and campaign specialists may all approach the same company. Without a shared record, Jordan could receive a contextual introduction and a second, unrelated pitch on the same day. Planning across channels should help those contacts make sense together.

LeaderMix can support the company discovery, contact enrichment and message preparation stages of this workflow. It uses Google Places for discovery and Apify for contact enrichment. AI creates message drafts, which users review; users send email campaigns. Enriched contact information still needs to be assessed for freshness and relevance to the responsibility you are researching.

Reacher verification is available for technical email checks, but not all email addresses are verified. Keep that distinction visible in your process. Discovery, enrichment, verification and sending address different questions. For the CRM fields, reply handling and follow-up behaviour described here, check what your chosen setup supports rather than assuming every step happens automatically.

Measure contact relevance alongside reply volume

Northline’s initial report placed Alex’s and Jordan’s replies in the same total. That showed activity without explaining commercial progress. A campaign could look productive while generating many replies from people who did not own the relevant work. Those exchanges also consumed research and follow-up time that a headline reply rate did not reveal.

The team defined several separate measures. The share of human replies indicating a responsibility mismatch provided a signal about contact selection. The proportion of referral requests receiving usable direction helped assess whether the question was clear and answerable. Neither measure, on its own, established sales effectiveness.

Further along the process, Northline tracked how many referred accounts reached a two-way exchange with someone responsible for the topic. It counted accounts rather than treating several replies from the same company as separate successes. It also defined a qualified conversation more carefully than a calendar invitation: there needed to be a relevant problem, an appropriate stakeholder and an agreed next step.

For attribution, the initial cold email remained the recorded source of the first account contact. Alex’s referral was documented as an interaction that helped the conversation progress. If Jordan later read an article and returned, that interaction would also be evaluated under the team’s chosen attribution model. Assigning the entire value of a future opportunity to one referral could distort channel decisions.

Research and follow-up effort should be treated consistently within the agency’s cost measurement approach. Time spent contacting unsuitable people is part of the operational work required to run the campaign. However, this fictional scenario provides no basis for claiming lower CAC or higher monthly recurring revenue. Those conclusions require actual costs, acquired customers and an appropriate measurement period.

Northline’s next proposed evaluation was to examine whether responsibility-based contact research improved relevance. Comparable account groups would need similar industries, company sizes and offers. Changes in small samples would remain tentative. The purpose was to learn which research choices helped the team reach suitable contacts with fewer unnecessary messages.

Give the next message a smaller, clearer purpose

In Northline’s hypothetical experience, progress came from accepting Alex’s stated responsibility, asking one focused question and accurately describing the referral when contacting Jordan. The exchange did not produce a buying conversation. It did clarify which part of the company owned the work and whether there was current interest in an agency.

The original long follow-up would have asked Alex to assess the service and navigate the company on Northline’s behalf. The shorter version asked a question Alex could answer, while leaving the research with the agency. That is a useful principle for outreach: give each message one clear purpose that fits the recipient’s role.

Reaching the right person does not mean that person is ready to buy. It does make a more informed discussion of relevance and timing possible. Any later contact should have a reason grounded in the exchange: a stated need, an accepted offer to share information or an agreed time to reconnect. Finding a name does not justify indefinite follow-up.

One practical step to use today: When a reply clearly says “This isn’t my responsibility” and contains no request to stop contact, consider asking: “Which team owns this business outcome? A team name is enough.” Review the full wording before responding; a general “not interested” is not automatically a responsibility mismatch. To explore support for company discovery, contact enrichment and message preparation, see how LeaderMix works.