Messaging
How to respond when a prospect says not interested
Short answer
Most of the time you should send nothing back, and the reason is in what they actually rejected.
They read one message. They know your name, your company, and the single sentence you gave for why you wrote to them. That is not enough to evaluate a product, and they did not try to. What they evaluated was your reason for picking them. Not interested means that reason does not describe them, or does not describe them now.
Once you see it that way, the standard advice looks strange. Objection handling assumes they weighed the offer and it came up short, so you counter with a benefit they must have missed. They did not weigh anything. There was nothing on the scale.
Why a no is the most useful reply you get
Silence tells you nothing. It could be a full inbox, a filter, a holiday, or a person who read the message and felt nothing worth typing. A refusal is different: someone spent ten seconds telling you their verdict on your reason, which is the one part of your outbound you fully control and the one part you cannot otherwise check.
The catch is that all three refusals arrive in the same words. They are opposite problems needing opposite responses, and if you treat them as one thing you will reply the same way to all of them and be wrong two times out of three.
Reading one: wrong person
You wrote to someone whose job does not touch the problem. Common tells: they mention a colleague, they say it is not their area, or the reply is oddly gentle, because a person with no stake in a topic has no reason to be sharp about it.
This one earns a reply, and it is the only reply that should contain a question about your own business.
Thanks for coming back to me. Sounds like I picked the wrong person. Who looks after renewals over there now?
Once. If nothing comes back, that is the end of it. A second chase asks a stranger to do unpaid internal navigation for a company they do not work for.
Two things to leave out. Do not restate what you sell, because the person you are asking about will never read this thread. And do not ask them to forward it.
Reading two: wrong time
The problem is real, the person is right, and it is not what this quarter is about. Tells: a date, a hedge, or an explicit later.
Leave. No reply improves this, because the thing standing between you and a conversation is their priority list, and you are not on it.
The part people get wrong is what happens next. The usual move is a reminder set for the date they mentioned, which produces a message saying some time has passed and asking whether anything has changed. From their side that message carries no new information, and worse, it makes obvious that nothing prompted it except your calendar.
Go back when something changes on their side, not on yours. A new person taking over the function. A change upstream of the problem. Them saying something in public about the thing they told you was not urgent. A product launch on your side is a change on your side, and the fact that it is genuinely news to you is exactly why it reads as a message about you.
Why your outbound stopped working covers how to tell a wrong-time failure from a wrong-person one across a whole batch rather than one reply at a time.
Reading three: wrong reason
The person was right, the timing may well have been right, and the sentence you led with did not survive contact. This is the most common of the three, and the only one where the correct response is nothing at all.
The mechanism is simple. Your reason was too general to be about them. If you write a second message now, everything you can put in it is a defence of that same reason: more detail on the benefit, a customer who resembles them, a request for fifteen minutes. None of that makes the original reason more specific, and sending it demonstrates that the first message was the strongest version you had. The second one proves the first was your best shot.
There is no message that recovers a wrong reason. There is only a better reason, found later, which is a research problem rather than a writing problem. How to say why you are reaching out is about finding one.
The case for replying to none of them
Take the argument seriously, because it is stronger than it sounds.
Here is a hypothetical week. The numbers are invented to show the shape. You send 200 messages and get 14 replies. Eleven are some version of no, two ask you to send something over, one wants to talk.
Writing a considered rebuttal to each of the eleven takes maybe four minutes, so 44 minutes in total. The same 44 minutes, at six minutes a head, finds you seven new people you can write a true and specific sentence about.
I have no number for how often a rebuttal turns into a deal, and neither does anyone who quotes one at you. What is knowable is the other side of the ledger. A reply keeps a thread open in the inbox of someone who has already closed it, and it takes a person who declined politely and asks them to decline twice. The second no is the one that arrives with an unsubscribe, or a spam report, or nothing at all and a name that will never open you again.
You already have their answer. Sending nothing costs you a possibility you cannot measure and saves you a relationship you can.
Send me more info in writing
This is the reply that gets misread most often, because it looks like progress and gets filed as progress.
Most of the time it is a polite no. It ends the exchange without anyone having to say a hard word, it costs the sender nothing, and it moves all the remaining work to you. The tell is that it contains no question. Real interest is specific: people who want to know something ask the thing they want to know.
One sentence separates the two.
Happy to. What would be most useful for it to answer?
If a specific question comes back, the interest was real and you now know exactly what to write, which is worth more than the document you would otherwise have guessed at. If nothing comes back, it was a no, and you found out for the price of one sentence rather than an afternoon.
What you should not do is answer with a deck. A general overview sent in reply to a vague question answers nothing they were wondering about, which is a fair description of most sales collateral.
We already use someone else
This is the only one of the three that deserves a real reply, and the reply is not a comparison.
Two reasons. Arguing that your product is better asks them to accept they chose badly, and almost nobody concedes that to a stranger by email. And they use the thing every day while you do not, so on how it performs inside their company they are the expert and you are guessing.
What you can say something useful about is timing and scope, because both are facts they hold and you do not.
Makes sense. When does that come up for review?
Or a question about the part of the job the vendor was never bought to do, if you genuinely know of one. Not a weakness in the product. A part of the problem that sits outside what it was chosen for.
Then leave it. If a contract has a year to run and it is doing its job, they are not a buyer this year, and the honest move is to note the date and stop spending messages on them. A displacement sale that happens at all usually happens because something broke, and you cannot cause that from outside.
What to do with the nos you have already collected
The pile of refusals in your sent folder is the most useful thing your outbound has produced, and almost nobody reads it back.
Sort the last thirty into the three readings. The proportions tell you what to fix.
| Mostly | What it means | What to change |
|---|---|---|
| Wrong person | Your list is built from job titles, not from people | How the list is made |
| Wrong time | Your list is right and your timing is blind | When you go back, and what triggers it |
| Wrong reason | Your list may be fine and your first line is generic | What you say in the opening sentence |
Most people find the third category largest and conclude they need better copy. Look closer before acting on that, because a generic first line is usually generic for a reason: there was nothing specific to say about that person, and the writing was covering for it.
Where this advice does not apply
If someone asked you to contact them and then said no, this is not cold outreach and none of the above holds. Ask them plainly what changed.
If you sell something cheap into a very large market, where a contact costs almost nothing and the decision is close to instant, volume genuinely does beat care, and this page is over-thinking your problem.
If your total market is forty accounts you can name, do not delete anybody. A wrong-person reply in that world is worth working properly, because there is no supply of replacements and the cost of the effort is small against the size of the account.
And if the reply was hostile rather than uninterested, there is no reading to do. Take the name off the list and move on.
Where a tool helps and where it does not
The tedious half of all this is the going back: noticing, months later, that something has actually changed for one of the people who told you it was not the right time. That is a memory problem more than a judgement problem, and it is the part Trendle is built to carry, by putting a name back in front of you with the reason attached.
It is the wrong purchase if your list is forty accounts you already know by name, or if your refusals are mostly the wrong-reason kind. No tool fixes a generic first line. That one is yours.
Questions people ask next
- Should you reply to a not interested email at all?
- In most cases no, and the default should be silence. The exception is when their reply contains information you can act on, such as telling you the area belongs to someone else or naming the vendor they already use. If the reply contains nothing but the refusal itself, there is nothing to answer, and answering anyway turns a closed thread into an open one they now have to end twice.
- What should I say when a prospect asks me to send more info in writing?
- Ask what they want it to answer before you send anything. A request for information with no question attached is usually a polite way to end the conversation without saying no, because it costs them nothing and moves all the work to you. If they come back with a specific question, the interest was real and you now know what to write. If nothing comes back, you learned that for the price of one sentence instead of an afternoon building a document.
- How do I respond when someone says they already use another vendor?
- Do not reply with a comparison. Arguing that their current choice was wrong asks them to agree they made a bad decision, which almost nobody does in an email to a stranger, and they know that vendor far better than you do. Ask instead when the arrangement is next reviewed, or about a part of the job the vendor was never bought to cover.
- How long should I wait before contacting someone who said no?
- Do not think in months, think in changes. A calendar reminder produces the follow-up that everyone ignores, because nothing has happened on their side since the last one and your message quietly says so. Go back when something in their situation has actually moved, and open with that thing rather than with the fact that time has passed.
- Is it worth asking a prospect why they are not interested?
- Rarely, because the question asks a stranger to do unpaid work explaining a decision they have no stake in. You can usually infer the answer from which of the three refusals you got, and that inference is free. The one time it is worth asking is when someone has already replied twice, which means they are willing to spend attention on you and the question is no longer an imposition.