Booking the meeting

Spot the moment

Stop selling the instant any of these happen: they ask you a question; they volunteer a detail you didn't ask for; they say "we've looked at that before"; or their voice drops out of brush-off mode into normal speech. That is interest, and interest decays. Ask now.

The specific ask

Weak asks are vague and open-ended. "Would it be worth grabbing some time?" invites "send me something". A strong ask has four properties: short duration, named purpose, two options, and a clear statement of what you need from them.

"Here's what I'd suggest. Twenty minutes, not an hour. I'll show you how two trusts handle spoke-site traceability, you tell me where your gaps actually are, and if it's not relevant we both save an afternoon. Thursday at two, or Friday morning — which is easier?"

The two-option close works because it replaces a yes/no decision with a much smaller one, and most people find it easier to pick than to decide. Two caveats: offer two options, not five — a menu sends them off to check a diary they never come back from — and only deploy it once interest exists. Used to force a lukewarm prospect it feels like a technique, and being handled is the fastest way to lose a stranger's goodwill.

Twenty or twenty-five minutes outperforms thirty and hugely outperforms an hour: it signals you respect their day, and it slips into calendar gaps a half-hour won't.

Confirming, so it actually happens

Send the invitation while you are still on the phone — "I'll send it now, can you confirm your email so I don't get it wrong?" Reading it back catches errors and creates a second small commitment. Ask who else should be there ("anyone in digital or governance who'd want to hear this?"): your first multi-threading move, and it raises the show rate, because meetings with two attendees are harder to drop quietly. And put substance in the invitation — three lines covering why we're meeting, what you'll show, and one question for them to think about. An invitation with an agenda is a meeting; an invitation with a Zoom link is an option.

Preventing the no-show

Between a quarter and a third of cold-booked meetings evaporate — the section 2 model assumes 75% held, a reasonable planning figure worth measuring for yourself. Three cheap habits move it:

• The pre-meeting note, sent within an hour of the call, while you're still a real person to them. Three lines, no attachment, ending on a question they can answer in one line. Any reply at all roughly doubles the odds they attend.
• The day-before nudge — and make it a question, not an administrative confirmation. "Quick one before tomorrow — is the traceability gap mostly between sites, or within the main lab?" A confirmation invites cancellation; a question invites engagement.
• The easy out. "If it's slipped down the list, just say and I'll move it — no hard feelings." Counter-intuitively this increases attendance, because the meeting stops being a trap they need to escape.

The arithmetic is worth seeing. Moving the held rate from 75% to 85% takes the model from 1.125 to 1.275 held meetings per 100 dials — 13% more held meetings for zero extra dials. Show-rate work is the cheapest yield in outbound.

When they ghost the booked call

Wait five minutes on the line — people are late. At minute five, ring their direct dial once; often enough they're on another call and will join. Then email within the hour, assuming good faith: "looks like today ran away with you — happens to all of us. Same time Thursday, or Friday at ten?" Two options again, and never "I guess this isn't a priority" or a note about the time you set aside. One more follow-up 48 hours later, then a light cadence; three no-shows and they go to nurture, because repeated ghosting is a decision. Finally, log it honestly — a no-show recorded as a reschedule corrupts your own conversion rates, the only data you have to improve with.

The full annotated call — gatekeeper to booked meeting

Fictional throughout. Alex Rowe is an SDR at Corvus Labs, which sells Corvus Trace, specimen tracking and chain of custody for pathology networks. The target is Ruth Vance, Pathology Operations Manager at Kingsmoor NHS Foundation Trust, a district general that has recently taken on lab work for two smaller spoke sites. Alex has read the trust's April board papers, which list specimen turnaround on the risk register, and has screened the number against the TPS and CTPS. Time: 10:20am on a Thursday.

Switchboard: Kingsmoor Trust, how can I help?

Alex: Morning — could you put me through to Ruth Vance in pathology, please?

→ The straight ask. No explanation, no "I wonder if you could possibly", no company name volunteered. Alex sounds like someone who rings this trust regularly, and switchboards route people who sound routed.

Switchboard: Can I ask what it's regarding?

Alex: It's about specimen traceability between the main lab and the spoke sites — she'll have the context. Happy to hold if she's mid-something.

→ The specificity play. "Just a quick chat" is what gatekeepers are trained to block; an unglamorous operational subject sounds like work rather than selling. Offering to hold signals patience, not pressure. Note what Alex does not say: not "she's expecting me", not "I'm returning her call".

Ruth: Ruth Vance.

Alex: Hi Ruth, it's Alex Rowe from Corvus Labs. [pause] I know I'm interrupting your morning — can I take thirty seconds to tell you why I rang, and you can tell me if it's nonsense?

→ Name, company, beat, permission. The pause is deliberate: it lets Ruth place the name and it is the single clearest audible difference between a person and a recording. "Tell me if it's nonsense" gives her a scripted way to say no, which paradoxically makes yes easier.

Ruth: Go on then. Thirty seconds.

Alex: Thanks. We work with pathology teams at district generals, and the thing that comes up over and over is specimens that arrive fine but can't be evidenced end to end when someone asks — so a repeat gets ordered, the patient gets re-bled, and it ends up on Datix. I rang you because you've picked up the work for two spoke sites recently, and that's usually the stage where it starts to bite. Is that close to your world, or have you got it nailed?

→ The four-part problem statement, spoken in about twenty-five seconds. Peer group ("district generals" — comparable, not a teaching hospital). The problem as a scene, not a category: re-bleeding a patient and a Datix entry are things Ruth has personally dealt with. The trigger ("two spoke sites") answers "why me, why now". And the escape hatch — "or have you got it nailed?" — makes an honest no easy, which is exactly why honest yeses come out.

Ruth: I mean... it's not brilliant. But look, we're in the middle of a procurement round, can you just send me an email?

Alex: Happy to, I'll do that today. Just so I don't send you something generic you'll delete — when you say it's not brilliant, is that mostly the handover between the spokes and the main lab, or is it inside the lab as well?

→ Textbook "send me an email": agree immediately and completely, then spend the goodwill on one qualifying question. Note that Alex quotes Ruth's own words back to her ("not brilliant"), which is both accurate and flattering, and that the question offers two concrete options rather than asking her to compose an answer from nothing. This is the single highest-value move on the call.

Ruth: It's the handover. Once it's here we're fine — we've got tracking in the LIMS. It's the transport leg. Nobody can tell me where a sample was between eight and eleven.

Alex: That's the one everybody has. Can I ask — when that happens, who ends up chasing it? Is that you, or the site?

→ Two things happening. "That's the one everybody has" normalises the admission so Ruth doesn't feel she's confessed to a failing — critical with public-sector buyers who are cautious about vendors hearing weaknesses. Then a question about who bears the cost, because pain with a person attached converts to a meeting far more reliably than pain in the abstract.

Ruth: It's my team. It's probably two or three hours a week of somebody ringing round porters.

Alex: Right. And I'd guess the awkward bit isn't the two hours, it's when someone from governance asks for the audit trail and there isn't one.

Ruth: [laughs] That's exactly it.

→ The "poke the bear" move: Alex names the consequence that is worse than the one Ruth volunteered, and offers it as a guess rather than an assertion. She either corrects him, which is useful, or confirms it, which is better — the laugh is the moment the call stops being a cold call.

Ruth: But honestly, we've got a LIMS module that's meant to do some of this. I don't know that we need another system.

Alex: Good — I'd be surprised if you didn't have something. I'm not ringing to rip out your LIMS; it does the in-lab bit properly and we don't compete with that. Where teams tend to find the gap is the leg you just described, outside the lab's four walls. Is that a fair read?

→ The "we already have a supplier" objection, handled without a word against the incumbent. Attacking the LIMS would attack the trust's own past decision, which Ruth would defend. Instead Alex concedes the incumbent's strength precisely and narrows the conversation to the gap Ruth herself just named. Note "is that a fair read?" — control handed back.

Ruth: It's fair, yes.

Alex: Then here's what I'd suggest. Twenty minutes, not an hour. I'll show you how two other trusts handle the transport leg — one of them's a district general with three spokes, so it'll look familiar — and you tell me where your actual gaps are. If it's not relevant, we've both saved an afternoon. Thursday at two, or Friday morning?

→ The ask, at the moment of maximum interest and not one sentence later. Twenty minutes, not thirty. Named purpose. A comparable peer, described rather than name-dropped, because Alex has not cleared the name. An explicit permission to conclude it's irrelevant. Then two options — a choice, not a decision.

Ruth: Friday morning's better. Ten?

Alex: Ten it is. I'll send it now — can you confirm your email so I don't get it wrong?

Ruth: r.vance@... yes, that's right.

Alex: Perfect. One more thing — is there anyone on the digital or governance side who'd want to be in the room for the audit-trail part?

Ruth: Probably Sam Idris, our quality lead. I'll ask him.

Alex: Great. I'll put a short note in the invite so he knows what he's walking into. Thanks for the thirty seconds, Ruth.

→ Four closing moves in twenty seconds. Sending the invite live removes the biggest single cause of no-shows. Reading the address back creates a second micro-commitment. Asking who else should attend is the first multi-threading step and lifts the show rate, because two-person meetings are harder to drop. And the sign-off refers back to the thirty seconds she granted — a small, warm callback that says the permission was real, not a device.

Elapsed time: about four minutes. Alex asked six questions and made four statements. That ratio is the point.

7. Getting better on purpose

Dialling more does not make you better; it makes you tireder. Improvement requires a loop: record, review against a fixed standard, change one thing, measure.

Recording and self-review

Your employer's dialler almost certainly records calls under its own policy and privacy notice — ask where the recordings live and how to access your own. Don't freelance private recordings on a personal device without checking company policy; call recording involves personal data and sits under UK GDPR as well as your employer's rules.

The review method that actually gets done, because it takes six minutes:

1. Listen only to the first 60 seconds of three calls a day. That is where the outcome was decided.
2. Transcribe your own opener verbatim, weekly. Not what you meant to say — what you said. Almost everyone finds a filler phrase they didn't know they had.
3. Ask three questions of each call: Did I sound like a peer or a supplicant? Did they say more than five words? What was the actual reason they stayed on the line?

The scorecard

Mark yourself 0 (absent), 1 (attempted) or 2 (clean) on each; twenty points available. A practitioner rubric, not a validated instrument — but very close to what an interviewer scoring a mock call is holding.

0–8: rebuild the opener and the problem statement before dialling again. 9–14: you are callable; work items 6 and 7. 15+: you can coach someone else, which is the fastest way to get to 18.

The "one thing this week" method

Change one variable per week, hold everything else constant, and give it at least 200 dials before judging. Changing three things at once teaches you nothing, because you cannot attribute the result.

A sensible sequence: week 1 the opener, week 2 pause and pace, week 3 the problem statement, week 4 the ask — each with one metric (what share of target connects gave me thirty seconds?, then what share of conversations got an ask?, then what share of asks became a booking?). Write the number down on Friday and keep or discard on evidence, not on how the week felt. Fridays feel worse than they are: it is the weakest calling day in the published data.

Carrying the load

The maths is unavoidable: at roughly 89 dials per held meeting, about 88 of every 89 dials do not produce a meeting. No technique removes this. What changes is what you make it mean.

• You are sorting, not persuading. Your job on any dial is to find out whether this person has this problem now. A no is a completed task; the only bad outcome is not knowing. And they are rejecting an interruption, not you — they have no information about you to reject.
• Ritual beats willpower. Stand up; next number within ten seconds; after a brutal call, three more immediately — so the decision to quit never gets an opening. Call beside a colleague, too: isolation is what makes rejection heavy.
• Track inputs, not outcomes. You control dials and conversations; bookings are partly luck. Judging yourself daily on outcomes you don't control is how good reps talk themselves out of a career.
• Know the difference between hard and wrong. Discomfort is normal and permanent. Dreading it for a month, or being asked to say things you can't defend, is a signal about the job, not about you.

Voice from the field

"There is no easy button in sales. Prospecting is hard, emotionally draining work, and it is the price you have to pay to earn a high income."
— Jeb Blount, Fanatical Prospecting (2015)

Field note

Almost every sales floor measures dials, because dials are the only number available in real time — and what gets measured gets gamed. Reps hit a dial target with 40-second calls to switchboards they know will not connect, and the dashboard turns green while the pipeline stays empty. If you are managed to a dial count, meet it and then quietly track the numbers that actually predict your month: target connects, conversations, and conversation-to-meeting. Those three tell you whether your list, your opener and your ask are working, and they are the numbers a good manager will want to talk about in a one-to-one. Bringing them unprompted is one of the fastest ways to be taken seriously in a first sales job.

The 30-day programme

Every week without exception: one peer review of your recordings, one self-review of three calls, one number written down. Over 30 days that is roughly 800 dials — at the section 2 rates, about 12 booked and 9 held meetings, and enough repetition to make the first fifteen seconds automatic. That last part is the actual deliverable.