Voicemail, day four: "Hi Corinne, it's Anouk at Palisar. Just circling back on the proposal we sent through last week. Give me a shout when you get a chance."
Voicemail, day eleven: "Hi Corinne, Anouk again. Just checking in to see whether you had any thoughts. Happy to jump on a quick call whenever suits."
Both are polite. Both are short. Both are dead on arrival, because neither gives Corinne a reason to call back that is stronger than the reason she already has for not calling back.
The situation behind them is ordinary. Five weeks ago Anouk ran a forty minute discovery call with Corinne Vasse, operations director at Two Rivers Bakehouse, a fictional supplier of packaged breads to regional supermarkets. Corinne described a production plan rebuilt by hand every time a supermarket moves a delivery window, named the two people it costs a day a week, and asked for a proposal. It went out. Then nothing, for thirty-two days.
The instinct now is to treat silence as an absence of information, which is why a follow-up call after no response becomes a nudge: no data, so no content, so just a reminder that you exist. Silence has a cause, the cause is usually knowable from the last conversation you had, and there are only about four of them.
Why did the buyer go quiet?
Displacement. Something larger landed between your call and now. An audit, a peak season, a resignation, a migration. Your project did not lose an argument, it never got into the room where arguments happen. This is the most common cause by a distance, and the one that punishes nudging hardest.
A blocker they cannot answer. Your champion took it to someone who raised an objection they have no response to. Nobody enjoys writing "my ops lead thinks your timeline is fantasy and I could not argue with him", so they write nothing. The deal is alive and stuck against one sentence you have never heard. An answer that only survives while you are in the room was never portable, which is the failure the objection handling guide is built around.
A decision already made. They chose a competitor, chose to build it internally, or chose to do nothing this year. The silence is not strategy, it is discomfort. Telling a vendor no produces nothing the buyer wants, so it slides down the list forever.
A champion with no route to a signature. Genuinely enthusiastic, genuinely powerless. They hit the point where somebody has to ask a budget holder for money, found they have no standing to do that, and stopped. You will not hear about this one, because admitting it is embarrassing.
Only the third is a no. The other three are recoverable, and each needs a different opening sentence. "Just checking in" fits none of them, because it hands the diagnostic work back to the person who has already shown they will not do it.
Say the reason out loud and make it cheap to correct
The play is to arrive at the call with a guess and lead with it.
Not a vague guess. A specific one, drawn from something the buyer told you last time. Corinne mentioned in passing that Two Rivers was being audited by its largest supermarket customer in August, and that Yusuf, her plant manager, would be tied up in it. That is the raw material, and it is now September.
So the opening is not "did you get a chance to look at the proposal". It is:
"I'm guessing the audit swallowed August and this has been sitting behind it. If that's right I don't need anything from you today, I just want to know whether I'm checking back in October or closing it out."
Three things happen in those two sentences.
You supply the reason so they do not have to. The awkwardness of the silence is what keeps it in place. Naming a plausible, blameless cause dissolves it, and the buyer's job drops from "explain and apologize" to "yes" or "not quite".
You lower the ask to almost nothing. Not a meeting, not a decision, not a review of the proposal. A timing signal, which costs six words to give.
You put the no on the table yourself. "Closing it out" is an option you offered, which is what makes the whole thing safe to answer.
A wrong guess is a good outcome too, because wrong guesses get corrected and the correction is the information you have been missing for a month.
Practicing this is mostly practicing the pause after the guess. The sentence is easy to write and hard to say, because the reflex when a buyer goes quiet is to fill the space with reasons they should still be interested.
A follow-up call after no response, annotated line by line
Same rep, same buyer, same thirty-two days of silence. The difference is what Anouk says in the first fifteen seconds.
The reminder call
Anouk: Hi Corinne, it's Anouk from Palisar. I know it's been a while. I just wanted to follow up on the proposal we sent through and see whether you had any questions.
Corinne: Hi. Yes, sorry, it's been on my list. Things have been mad here.
Anouk: No problem, completely understand. We talked about the replanning time and the day a week it was costing, so I thought it might be worth fifteen minutes on the implementation piece, because that's usually where people have questions. Would something next week work?
Corinne: Let me look at my calendar and come back to you.
Anouk: Perfect, I'll send a note over. Thanks Corinne.
Anouk hung up believing that went fine. She learned nothing she did not know before dialling, and left with a commitment ("let me come back to you") carrying no date, no owner and no consequence, which is the same silence with a politeness layer on top. Worse, she re-pitched value Corinne agreed with five weeks ago, signalling that the problem is Corinne's understanding. It never was.
The reason call
Anouk: Hi Corinne, Anouk at Palisar. I'll be quick. I'm guessing the supermarket audit swallowed August and this has been parked behind it. If that's right I don't need anything from you today, I just want to know whether I'm checking back in October or closing it out.
Corinne: The audit was part of it. To be honest it's more that Yusuf looked at the changeover and reckoned it would cost him most of a shift, and I didn't have a good answer for that.
Anouk: That's useful, thank you. Was it the shift itself, or that it lands in a week where he can't spare one?
Corinne: Both, really. He's flat out until the November range change.
Anouk: Then the honest answer is that the changeover is about four hours, not a shift, and we've run it on a Sunday twice this year so nothing comes off the line. But that's exactly the claim a plant manager should not take from a vendor. Can I send the two things Yusuf would want: the hour by hour changeover sheet from a site your size, and a number for their production lead so he hears it from someone who has done it?
Corinne: That would help. He'd trust that more than a deck.
Anouk: Both over tomorrow morning. And rather than leaving it with you to chase, can I call you the Friday after the range change, so it lands when Yusuf has room to look at it?
Corinne: Yes, that works.
The call runs under three minutes and the deal moves further in it than in the previous month.
Look at what the opening guess bought. It was wrong, and being wrong produced the real answer: an objection from a person Anouk has never spoken to, unaddressed for a month. No amount of "any thoughts on the proposal" reaches that.
Then notice what she does with it. She does not argue Yusuf down by proxy. She hands Corinne two portable artifacts and a person to call, because the argument has to survive a room Anouk is not in. And she takes the follow-up burden back onto herself, with a date tied to something already in Corinne's calendar.
The exit line that earns more callbacks than another nudge
"If this is dead, just tell me and I'll stop calling. That's a completely fine answer and I'd rather have it than keep guessing."
Say it, and mean it. It works for a mechanical reason: a person who owes you an uncomfortable message will keep not sending it, but a person offered a one word way to close the loop will often take it. Often enough, what comes back is "no, it isn't dead, it's just parked".
The version that fails is the passive-aggressive one, usually by email, which frames the exit as a small punishment ("I'll assume this is no longer a priority and close the file"). Buyers read the difference instantly. One is a door held open. The other is a door slammed loudly enough that you are supposed to come back and hold it.
What makes the third call worse than the second
Calling with no new information and no guess. If you have nothing to say beyond your own existence, the call is a tax on the relationship. Get a guess or get a reason, then dial.
Escalating frequency instead of changing content. Five identical touches in ten days is one message delivered louder. Change what the touch contains before you change how often it arrives.
Using the last call's value case as the new hook. They agreed with it. Repeating it argues with a position nobody holds.
Leaving the next step with the buyer. "Let me know" is how a deal goes quiet twice. Name a date, tie it to something in their calendar, and own the action.
Treating a soft "not now" as a hard no. Displacement expires on its own. Close the loop with a date, not with a deletion.
Fixing this after the fact every time. Most of it is upstream. A call that ends with an agreed next step and a reason to speak again never produces this problem, which is the argument of the sales follow-up guide. Silence is what an unended call sounds like a month later.
Rewrite the two voicemails from the top of this page and you can hear the difference without changing a single fact.
Day four: "Hi Corinne, Anouk at Palisar. You mentioned the supermarket audit was landing this month, so I'm assuming this is parked behind it, and that's fine. I'll try you the first week of September. If it's dead before then, tell me and I'll stop."
That message answers itself and needs no callback to do its job. If Corinne does call back, she calls back with the actual reason. That is all a follow-up call after no response is trying to buy.
