A bare "not interested" reply to a cold email gets one short, polite exit and nothing else. Thank them, confirm you will not follow up, and leave a way back. No rebuttal, no second pitch.
If the reply gives a reason, such as "we already have someone for this", you can ask one clarifying question before you let it go. If it says "remove me", you stop everywhere.
The other objections that show up in a B2B inbox follow the same idea, one small step per reply:
- "Send me more info": ask which part matters to them, then send one short thing that answers it.
- "No budget": ask whether that means no or not yet, and when budget for this gets decided.
- "Bad timing": agree on a month, write it down, and come back in that month.
- "Who are you?" or "How did you get my email?": say plainly who you are and where the address came from, and give them something to check.
Smirnov Consulting Group is a Prague-based B2B outbound lead generation agency that runs cold email and LinkedIn campaigns for founder-led B2B companies and books qualified sales calls.
The example threads below all use one made-up sender: a small IT consulting firm that emailed operations directors at mid-size logistics companies, offering a two-week review of their warehouse software. Swap in your own offer.
Each reply goes in the same thread, under their subject line, and is short enough to read on a phone without scrolling.
How to reply to "not interested", with or without a reason
Someone who looks like an ideal client can still be busy, not ready, not interested or simply not in buying mode.
A two-word reply does not tell you which of those you hit, and an argument will not find out. So the reply to a bare no is an exit that costs them nothing to read.
Them: Not interested.
You: Understood, thanks for letting me know. I won't send anything else about this. If the warehouse review ever becomes relevant, my details are below.
Then take them out of the sequence the same day, so no automated step fires later as if they had never answered.
An explained no is different. The prospect has told you something, and one question can show whether the reason is final.
Them: Thanks, but we already have an IT partner who handles this.
You: Good to hear, and thanks for the context. One question and then I'll leave it: does that partner also look after the warehouse system, or only the office IT? If they cover both, I'm happy to close this here.
If the answer confirms the no, close the thread in one line. One question is the limit. A second one starts to feel like a negotiation they never asked for.
What to reply when they say "send me more info"
This reply is sometimes a real request and sometimes a polite way to end the thread, and a few signals in the wording tell the two apart. A generic deck attached under "as requested" treats both the same way, and it gives them nothing to answer.
Ask what they want to know, and make the question easy to answer in one line:
Them: Can you send me some more information?
You: Happy to. Which would help more: a one-page outline of what the two-week review covers, or a short example of what it turned up at a logistics company your size?
Whatever they pick, send one short thing that answers exactly that, in the body of the email, with the next step in the last line. If they never answer, that is your answer too.
Outbound has an order to it: conversations before calls, calls before clients. A "send me info" reply is a conversation that has not started yet, and your reply is the attempt to start it.
What to write when the answer is "no budget"
"No budget" covers two situations. Some prospects mean this will never be a line item. Others mean the money for this year is already spent. Your reply finds out which one, without pushing.
Them: We don't have budget for this right now.
You: Thanks for being straight with me. Is that a no for this kind of work in general, or a question of when the budget gets set? If there's a planning month, tell me and I'll come back then with something short.
If it is a general no, treat it like the explained no above: accept it and close. If there is a month, the reply has turned into a timing objection, and the next section applies.
What you do not send is the pressure play: a discount that expires on Friday, or a message whose only job is to force a yes.
A "buy or die" email is a lottery ticket. A reply to an objection is the worst place to buy one, because the prospect has just told you where they stand.
Answering "bad timing" so it is still there next quarter
A "not right now" can turn into a signed client months later, and it is also an easy reply to lose. Writing the reply is simple. Keeping the promise is the hard part.
Them: Interesting, but the timing is bad. We're in the middle of a system migration.
You: Makes sense, a migration is the wrong moment for this. Which month would be better to pick it up? I'll put it in the calendar and send one short note then, nothing before.
Then do exactly what you said. In the follow-up sequence I use the line that matters here is this one: "A 'not now' in March is a real opportunity in September, but only if somebody wrote it down."
Put the month in a CRM. Which CRM does not matter. What matters is that no lead gets lost.
Record three things: the month they named, the reason they gave and their exact words. The note you send in that month can then mention their migration instead of starting cold.
Answering "who are you" and "how did you get my email"
These two can arrive in the same message, and they deserve a straight answer. A vague "we came across your company" makes the second message worse than the first.
Them: Sorry, who are you? And how did you get my email?
You: You're right to ask. I run a small IT consulting firm that works with logistics companies, and my LinkedIn profile is below. Your address came from [name of the data provider you used], a business contact database, filtered for operations roles in logistics. If you'd rather not hear from me, say so and I'll remove you.
Fill that slot with the actual provider's name. "A database" on its own does not tell them where their data came from.
If GDPR applies to your outreach, that is also what the law asks for. For personal data you did not collect from the person, Article 14 lists "from which source the personal data originate" among the things you must tell them.
When you use the data to contact them, that is due at the latest at the first communication.
That comes from the official GDPR text, Articles 14(2)(f) and 14(3)(b), checked September 2026. Article 14(5) lists exceptions. This is not legal advice.
The "who are you" half is answered less by your reply than by what they find when they look you up, so expect them to look.
I made this argument in a post on why the same email gets two different reply rates: a weak message sent from a strong profile does better than a perfect message from a sender nobody can find.
If your track record is still thin, there is more to point at than a first instinct suggests:
- A LinkedIn profile that says who you help and with what
- Real work you did before, described honestly, including where you did it
- A claim narrow enough to check, in place of a big promise
- Something they can look at, such as a short video or a written teardown
- People who will vouch for you
When the reply means stop
A reply that says "remove me", "unsubscribe" or "stop emailing me" ends the conversation. Nothing above about clarifying questions applies.
In the US, the FTC's CAN-SPAM compliance guide says you must honor an opt-out request within 10 business days (checked September 2026).
B2B email gets no exemption, and the guide puts the penalty at up to $53,088 for each email in violation (checked September 2026).
In the EU, GDPR Article 21 gives people the right to object at any time to the use of their data for direct marketing. Once they object, the data "shall no longer be processed for such purposes" (Article 21(3), same official text, checked September 2026).
None of this is legal advice, and the rules differ by country, so check the ones that apply to your list. In practice, reply once, in one line:
You: Done, you're removed and won't hear from us again. Sorry for the interruption.
Then remove them from every sequence and every list you send from, including any LinkedIn steps tied to the same campaign.
When the same objection keeps coming back
Answering objections one at a time is the daily work. Reading them as a batch tells you what to fix in the email that caused them.
What the replies look like as a group says more than how many there are. Near-silence means the email asked for more than the trust it had built.
A run of polite declines means the ask arrived too early, before the email had explained your offer, which points at the body copy. Questions coming back mean the ask was about right, and they deserve a real answer in place of a calendar link.
| Objection that keeps repeating | The reply move | What to check in the original email |
|---|---|---|
| Not interested, no reason given | Thank them, confirm no more emails, leave a way back | Whether the list holds the right people (how I take a list apart) |
| Explained no ("we already have someone") | One clarifying question, then close | Whether your offer reads as different from what they already have |
| Send me more info | Ask which part matters, send one short answer | Whether the email says plainly what you do and for whom |
| No budget | Ask no or not yet, and when budget gets set | Whether you are writing to the person who owns that budget |
| Bad timing | Agree on a month, record it, return then | Usually nothing; this is pipeline for later |
| Who are you, how did you get my email | Name the source, point to your profile | The sender's profile, as a stranger sees it |
| Remove me | Confirm in one line, remove everywhere | Where the list came from and how tightly it was targeted |
Questions about answering objections by email
Should I use objection-handling scripts word for word?
Use them as a starting shape, then rewrite each reply around what the prospect actually said. A reply that picks up their words, like their migration, shows a person read it. A pasted script reads like the automated follow-up they were trying to stop.
How many times should I follow up after an objection?
After a bare "not interested" or any removal request, zero. After "bad timing" or a not-yet on budget, once, in the month you agreed. After an explained no, one clarifying question is the limit.
Does GDPR or CAN-SPAM change how I can answer objections?
Mostly at the edges. A request to stop has to be honored: within 10 business days under CAN-SPAM, and under GDPR Article 21 the data can no longer be used for direct marketing once the person objects (both checked September 2026).
Under GDPR, if someone asks where you got their address, Article 14 generally expects you to have told them already (checked September 2026). None of this is legal advice.