Booking the Meeting Before You Hang Up: The Last Forty Seconds of a Cold Call

Go and watch any cold call training video. Count how many minutes go to the opener. The permission-based intro, the pattern interrupt, the tone, the pause, the "I know I'm an interruption." Then count how many minutes go to the part where you actually ask for the meeting.

It's not close. The industry has an opener obsession, and I understand why — the opener is where most calls die, so that's where the coaching went. But the calls that don't die there still have to land somewhere, and I've listened to a lot of recordings where a rep does everything right for four minutes and then fumbles the ball on the one-yard line. Good discovery. Real interest. Prospect leaning in. And then: "Great, well, maybe we could find some time next week?"

That's not a close. That's a wish.

This post is about the last forty seconds of the call. Not the opener, not the pitch, not objection handling. The stretch that starts the moment you hear a buying signal and ends when you put the phone down. It's the shortest part of the call and the part with the least training attached to it, which is a strange thing when you think about it, because it's the only part that produces the outcome you're actually paid for.

What the last forty seconds is for

One job: convert a warm feeling into a specific commitment with a specific person at a specific time.

That's it. You are not selling in the last forty seconds. You are not adding one more proof point. You are not answering a question they didn't ask. Every extra sentence you say after they've signalled interest is a chance for them to remember something else on their to-do list.

The signal is usually small. "Hm, that's a fair point." "Yeah, we've had that issue." "Who else are you working with in this space?" "How long does the thing take to set up?" None of those are yeses. All of them are permission to ask.

The transition I use is boring on purpose:

"Sounds like it's worth twenty minutes. Let me look at my diary."

Said as a statement. Then you go and ask for the time.

Ask for a time, not for time

The single biggest improvement most reps can make to their close is to stop asking for a quantity and start asking for a coordinate.

"Could we find some time next week?" asks the prospect to do work. They have to open a calendar, scan it, pick a slot, weigh it against things they haven't scheduled yet, and then say it out loud to a stranger. That is four decisions you've outsourced to a busy person who does not care about your quota.

"Does Thursday at two work?" asks for one decision. Yes or no. And if it's no, the no comes with information attached — "Thursday's bad, I'm on site" — which you can immediately use.

So the rule is: name the day, name the time, name the length. "Thursday the fourteenth at two, for twenty minutes." All three. The length matters more than people think, because the unspoken fear on the other end of the line is that you're going to eat an hour of their afternoon with a slide deck. Twenty minutes sounds like something a person can survive.

And say the number out loud in the same breath as the day. Reps who say "how does Thursday look?" get "Thursday's fine" and then have to have a second negotiation about the hour, which is where meetings go to die.

Two slots, never five

When you offer options, offer two.

I've watched reps read out their entire week — Tuesday morning, Tuesday afternoon, Wednesday any time, Thursday before eleven, Friday — as if generosity were the point. What actually happens is the prospect stops listening around the third option, hears an undifferentiated wall of availability, and says "send me some times." You have just talked yourself out of a booked meeting by being too accommodating.

Two does something different. Two frames the question as which, not whether. It also, quietly, signals that your calendar has things in it. A rep with two slots sounds like a rep with a business. A rep with nine slots sounds like a rep with a spreadsheet of names and nothing else to do.

Make the two genuinely different. Not "Thursday at two or Thursday at three" — that's one option wearing a hat. "Thursday at two, or Friday first thing, say eight-thirty?" Different day, different shape of day. If they're a morning person you've caught them; if Thursday afternoon is their standing ops meeting you've caught them anyway.

And then stop talking. Genuinely stop. The silence after two named slots is the most productive silence in the whole call, and most reps step on it because four seconds of nothing feels like a minute when it's your commission.

"Just send me a calendar invite" is a soft no

Here's the one that costs the most meetings, because it sounds like a yes.

"Sure, send me an invite for sometime next week and I'll take a look."

Every rep I have coached hears that and writes "BOOKED" in the CRM. It is not booked. What's been agreed is that you will do some work and they will consider it later, in a context where you are not present and cannot answer for yourself. The invite lands in an inbox alongside forty other things, gets tentatively accepted or ignored, and then declined on the morning of, or worse, no-showed.

The reason it happens is that "send me an invite" is a socially perfect exit. It's polite, it's forward-looking, it costs them nothing, and it gets you off the phone. People aren't being dishonest when they say it. They're being human.

You fix it on the call, and you fix it without arguing. What you do is agree enthusiastically and then narrow it:

"Absolutely, I'll send it across. Let's just pin the slot now while I've got you, otherwise it'll bounce around for a fortnight — Thursday at two, or Friday morning?"

That's the whole move. You've accepted their request, so there's nothing to push back on. You've given a reason — the honest one, that unscheduled things drift. And you've come straight back to two coordinates.

If they resist a second time, that's real information. "Look, I genuinely don't know my week yet" is often true for people who run operations. In that case, don't force a slot — force a call. "Fair enough. Can I call you Monday at nine to grab fifteen minutes in your diary once you can see the week?" A booked call to book a meeting is a much better asset than a floating invite, because you've still got a coordinate and you've still got a reason to ring.

What you should not do is accept a vague yes and hang up feeling good. In my experience the meetings that fall apart between the call and the calendar were never really made in the first place. They were made in the rep's head.

Confirm who's actually going to be in the room

Still in the last forty seconds. You have a day and a time. Now spend one sentence on attendees, because this is the difference between a first meeting and a wasted one.

"Is it just you on the call, or is there anyone on the technical side you'd normally pull in for something like this?"

Note what that isn't. It isn't "are you the decision maker?", which insults people, and it isn't a qualification interrogation. It's a logistics question, phrased as a favour to them, and it does three things at once. It tells you whether you're talking to the person who can act. It gets a second name out of them without a fight. And it slightly raises the stakes of the meeting in their own mind, because a meeting they've invited a colleague to is a meeting they turn up to.

If they say "just me for now," that's fine — don't push. Follow with "perfect, and if it makes sense after twenty minutes we can loop in whoever you'd want for a deeper look." You've planted the next step without asking for it.

Then get the email address out loud and read it back. Yes, you probably have it. Read it back anyway. It takes six seconds and it catches the ones your data provider got wrong, and there is no worse way to lose a booked meeting than to a bounced invite.

The recap that goes out before you make the next dial

The last forty seconds of the call has a tail: the next six minutes.

Send the invite immediately. Not at the end of your block. Not after lunch. Before you dial the next number, while the conversation is still the most recent thing that happened to both of you. If your dialler pulls you straight into another call, pause it. This is worth the pause.

The invite body is one line, and it is their words, not yours. Something like:

Twenty minutes to look at how you're handling the changeover paperwork across the two lines, and whether there's a faster way. Bringing nothing to sell — happy to share what the other three plants we work with in the region did. Tim

That's it. No agenda with four bullets. No attached deck. No "looking forward to exploring synergies." One sentence that repeats the specific thing they told you was annoying them, so that when they see the invite on Thursday morning they remember why they said yes rather than wondering who you are.

If you learned a second name, add them. If you didn't, leave a line in the email — not the invite — saying "if there's anyone else worth having on, forward it over."

The reason for the six minutes isn't magic. It's that the value of your recap decays fast, and the prospect's memory of you decays with it. You want your invite to arrive while the call is still the freshest thing in their head.

Three closes, three personas, same mechanics

The machinery doesn't change: signal, transition, two slots, silence, attendees, recap. What changes is the reason to meet, and the reason has to be theirs. Here's what that sounds like across three very different people.

Plant manager, mid-sized manufacturer

Them: Yeah, the changeovers are a pain. We've talked about it internally.

Me: Sounds like it's worth twenty minutes. Let me look at my diary. I'm not going to demo anything at you — I'd want to walk through how the other two plants in the region sequenced their changeovers and you tell me whether any of it's relevant to your lines. Thursday at two, or Friday first thing, half eight?

Them: Friday's easier. Half eight's fine, I'm in at six anyway.

Me: Friday half eight, twenty minutes. Is it just you, or would you normally have your maintenance lead sit in on something like this?

Them: I'd probably grab Dave.

Me: Grab Dave. I'll send the invite in the next five minutes — is it still initial dot surname at the dot com?

Note the reason to meet: what comparable plants did. Not a product. A plant manager's currency is what other plants are doing, and if you want to see how you'd get to that point in the conversation in the first place, the whole manufacturing cold call script builds toward exactly this kind of ending.

CRO at a growth-stage software company

Them: Okay. So how does this actually work with our existing stack?

Me: That's the right question and it's a twenty-minute answer, not a two-minute one. Let me look at my diary. What I'd want to do is get your RevOps lead on with us and go through where your data actually lives today, so I can tell you honestly whether this is a fit or not. Tuesday at eleven, or Wednesday at four?

Them: Tuesday. Send me an invite.

Me: Will do — Tuesday the ninth, eleven o'clock, twenty minutes. Who's the RevOps name I should put on it?

Them: Priya. I'll forward it.

Me: Perfect. Invite's with you before you've finished your coffee.

The reason to meet here is whether this is a fit or not — a CRO has been sold to constantly and responds better to a rep willing to disqualify than to another enthusiast. The SaaS cold call script for reps dialling CROs, VPs of Sales and RevOps leaders sets that tone from the first line, and this close only lands if the rest of the call earned it.

VP of clinical operations, hospital system

Them: We're mid-way through an Epic optimisation, so honestly the bandwidth isn't there right now.

Me: Understood, and I'd rather not be another thing on that pile. Here's what I'd suggest — twenty minutes now while the optimisation is live is worth more than an hour after it's frozen, because the discharge workflow piece is the bit that's hardest to change later. Twenty minutes, no build required from your side. Monday at eight, or Thursday at four?

Them: Thursday. Four's tight, make it four-fifteen.

Me: Four-fifteen Thursday. Would you want your informatics lead on it, or is that a later conversation?

Them: Later.

Me: Fine. I'll keep it to the two of us and twenty minutes.

Different reason again: timing, and specifically the cost of waiting. Clinical operations leaders live inside project cycles, and the close has to attach to the cycle rather than to your quarter. The healthcare cold call script for getting a CMIO or VP of clinical operations to give you twenty minutes goes deeper on how to talk about those cycles without pretending you understand their organisation better than they do.

Three industries, three completely different reasons, one identical set of mechanics. That's the point. You don't need a new close for every vertical. You need one close and a genuine answer to "why would this specific person spend twenty minutes on this specific thing."

The part nobody practises

Here's what I noticed after years of dialling and years of listening to other people dial, including my own calls when I sold inside AWS and Dell: reps rehearse the opener out loud and rehearse the close in their heads.

The opener gets said a hundred times a day, so it gets smooth whether you practise it or not. The close gets said a handful of times a week, only after a call has gone well, under the specific pressure of not wanting to break something that's working. That's the worst possible conditions for a skill you've never drilled. Which is why the close comes out as a mumble — maybe-we-could-find-some-time — from reps whose opener is razor sharp.

So drill it separately. Take the transition line, the two slots, the silence, the attendee question, and run them cold, twenty times, without the rest of the call attached. Then run the "just send me an invite" version. Then the "my week's chaos" version. You want the words to arrive without you having to build them, because at the moment of truth your attention should be on their tone, not on your own sentence construction.

If you want to rehearse that against something that pushes back rather than against your own reflection, that's the whole reason I built DrillCall — you can run the last forty seconds on repeat with a prospect who says "send me an invite" and then says it again, until agreeing-then-narrowing is the thing your mouth does automatically. If you're selling into ops-heavy worlds, the same drilling applies to the construction and trades close, where the person you want is standing on a site and has about ninety seconds of patience left.

Book the time. Name the day. Two slots. Then shut up.