Staffing / Recruiting · Cold Call
The Staffing / Recruiting Cold Call Script for Reaching VPs of Recruiting and Branch Managers
You are dialling someone who spent eleven years on a desk before they ran one. A Managing Director or VP of Recruiting has heard every opener in existence, usually from a rep who calls their reqs "job orders" and their recruiters "talent acquisition professionals." They will clock you as an outsider in about four seconds. The counter to that is not enthusiasm — it's saying something so specific about their week that they stop trying to place your name and start listening.
The specific thing, for most firms, is one of two problems. Either the shortlist goes into the void — three qualified profiles out Tuesday, "great, reviewing this week," and six weeks later the req closes in the ATS because it got filled internally and nobody chased past the second email. Or contractors walk at end of assignment — nine months on billing, zero conversations since onboarding, and they're on a competitor's payroll by Wednesday with redeployment sitting in the low 20s. Both problems show up on the numbers the person you're calling actually gets asked about: submittal-to-interview ratio, placements per recruiter per month, fall-off inside 30 days, bench days.
This script is built for a cold dial with no email, no referral, no download. The goal is not to explain your product. It's to name their desk math accurately enough that they give you twenty minutes with whoever runs delivery. Everything below is meant to be said out loud, at your normal speaking pace, slower than feels comfortable.
The cold call script
Say it in your own words. The structure is the part that matters.
- 1
90-second prep (do not dial without this)
Say each of these out loud before the phone rings: 1. WHO: "Priya Raman, VP of Recruiting, three years in seat, owns delivery across IT and light industrial, roughly 35 recruiters." 2. TRIGGER: new office opening, a fresh MSP win on their site, 40+ open reqs posted in the last two weeks, a Practice Lead hire in a new vertical, or an acquisition. No trigger? The segment is the trigger: "every IT staffing firm we talk to that's running 30+ recruiters against VMS-capped rates." 3. ONE PROBLEM I'LL LEAD WITH: shortlist ghosting OR contractor redeployment. Not both. Write it down. 4. THE ASK: "Twenty minutes, Thursday 8:15 or Friday 11." Have the follow-up email drafted in a window before you dial, and the calendar invite half-built.
- 2
Opener — honest cold call frame
"Hi Priya, it's Marcus at Cordell. We haven't spoken — this is a cold call. Can I have thirty seconds to tell you why I rang, and then you can tell me to get lost?" [PAUSE. Two full seconds. Do not fill it.] Downward inflection on "get lost." If they answer clipped and flat, come in one notch below bright — this buyer talks to recruiters all day and can smell performance.
- 3
Opener — pattern interrupt (for the Managing Director who screens hard)
"Priya — Marcus, Cordell. You don't know me. Bad time?" Most say "depends what it's about." That is permission. Go straight to the problem, not to your company.
- 4
Opener — trigger-led
"Priya, Marcus from Cordell. I saw you've posted eleven .NET and data engineering reqs out of the Dallas office in the last two weeks — that's actually why I called. Got a minute?" Or: "I noticed you brought on a Practice Lead for healthcare IT last month. That's why I rang. Sixty seconds?"
- 5
The reason — Problem A: shortlists go into the void
"We work with about a dozen staffing firms running between twenty and sixty recruiters. The thing that keeps coming up with VPs of Recruiting is the shortlist that goes into the void — recruiter sends three qualified profiles Tuesday, hiring manager says 'great, reviewing this week,' and then nothing. Nobody's got a defined cadence past the second email, so the req sits in the ATS as 'submitted' while the candidates take other offers, and six weeks later you find out it was filled internally. Submittal-to-interview rots and the forecasted spread never books. Is that anywhere near your world, or have you got that nailed down?" Notice: no product name. The out at the end — "or have you got that nailed down" — is what makes an honest answer safe.
- 6
The reason — Problem B: contractors walk at end of assignment
"We work with staffing firms in the twenty-to-sixty recruiter range. The number that comes up in almost every conversation with Directors of Delivery is redeployment. A contractor finishes a nine-month assignment on a Friday, nobody's spoken to them since onboarding, and they're on a competitor's payroll by Wednesday. Most firms we look at are somewhere in the twenties on redeployment when the same firm's target is north of fifty — so every ending assignment is a re-source of someone you already recruited, already background-checked, already know performs. Where does yours sit, roughly — or is that already handled?"
- 7
Two questions maximum, then close
Narrow and factual only. Pick two: - "How's the follow-up handled today after the shortlist goes out — is that a person or a sequence?" - "Roughly how many contractors do you have on billing at any given time?" - "What's your submittal-to-interview running at across the desk — one in three, one in five?" - "Is that on someone's plan this year, or is it just living with it?" Listen for the admission: "yeah, it's a mess," "we've been meaning to," "honestly I couldn't tell you, the ATS data's not clean." When you hear it, stop asking and close.
- 8
The ask
"Here's what I'd suggest. Twenty minutes — not a demo, no deck. I'll walk through what redeployment and submittal-to-interview look like at firms your size in IT and light industrial, you tell me whether your numbers already beat them. If they do, we're done and you've got a data point for your next ops meeting. I've got Thursday at 8:15, before the day gets going, or Friday at 11. Which is less bad?" Then: "Sending the invite now — can you tell me it landed?" Do not hang up before it lands.
- 9
Gatekeeper / "what is this regarding"
"It's about their contractor redeployment numbers — Marcus at Cordell, she won't know me. Happy to be told to email instead." Short, calm, specific. Never imply a prior relationship, never say "it's personal," never say "she's expecting my call."
- 10
Voicemail — under 20 seconds, no ask
"Priya, Marcus at Cordell — you don't know me. Calling about redeployment rates on contractors rolling off assignment; it's the thing we see most at firms your size. I'll try you again Thursday morning. 555-0148." The voicemail's job is name recognition for attempt two, not a callback.
- 11
The soft no and the recycle
"No problem. Last thing and I'll let you go — is this a timing thing or a not-a-priority thing?" [Listen.] "Got it. When does the delivery team set targets for next year — October?" "Perfect. I'll come back to you the first week of October. I'll send one email now so you've got my name on file." A dated callback plus one named priority is a successful call. "Send me an email" with nothing attached is not.
- 12
Immediately after
- Send the follow-up inside five minutes. Subject: "Our call just now — redeployment on rolls-off." - Log their exact words. If she said "we're bleeding people at end of assignment," that phrase goes in the email and opens the discovery call. - Log an honest disposition: "booked Thu 8:15, Director of Delivery joining" or "callback first week Oct, target-setting." Never "interested."
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Hi Dave, it's Marcus at Cordell. We haven't spoken — this is a cold call. Can I have thirty seconds to tell you why I rang, and then you can tell me to get lost?
Buyer
Marcus, I ran a desk for eleven years and I've been a Managing Director for six. I know exactly what the next thirty seconds sound like. You've got them, but I'll stop you the second it turns into a pitch.
Rep
Fair deal. We work with staffing firms running twenty to sixty recruiters, mostly IT and light industrial. The thing that keeps coming up with Managing Directors is contractors walking at end of assignment — nine-month contract ends Friday, nobody's talked to the person since onboarding, they're on a competitor's payroll Wednesday. Most firms we look at sit in the low twenties on redeployment. Is that near your world or have you got that solved?
Buyer
We're at 31%. And before you tell me that's low, I'll tell you it's low. But we're a Bullhorn shop with automation already licensed. Whatever you're selling, we bought a version of it eighteen months ago.
Rep
Most firms your size have. Let me ask it the way I'd want it asked of me — of the contractors who rolled off last quarter, what percentage had a logged conversation in the thirty days before their end date? Not an automated email. A conversation.
Buyer
Honestly? I don't trust the number the system would give me. Half my recruiters log activity at six o'clock from memory. 'Last contacted' in that system is fiction and everybody here knows it.
Rep
That's the answer I hear most. So you've got two things stacked — the redeployment number itself, and the fact that when it slips you can't tell your owner whether it's a sourcing problem, a client problem or a recruiter problem. Which of those two is the bigger headache in your pipeline reviews?
Buyer
The second one, obviously. Every Monday review turns into a debate instead of a decision. But look — margins. We're 70% VMS work, the programs have capped us at 13, and ownership's answer to everything is 'do more with the same headcount.' Anything that adds cost per placement is dead before I bring it up.
Rep
Then let's not talk about spend, let's talk about the thirty-one. Every point you move redeployment is a placement you don't pay to source — same bill rate, no job board spend, no forty recruiter hours. If you moved 31 to 45 across the contractor base you've got on billing, that's the whole conversation. Roughly how many contractors do you have out right now?
Buyer
Around 240. And I'll tell you the other thing you're going to run into — my recruiters are already in four systems. LinkedIn Recruiter, Bullhorn, the VMS portals, the dialler. A fifth login and they'll nod in training and never open it again. We tried something two years ago and it was dead by month two.
Rep
What broke — the tool or the process around it? Nine times out of ten nobody owned the cadence and it quietly died. Was there anyone reporting on touches weekly, or was it left to the recruiters?
Buyer
Left to them. My delivery director rolled it out and then Q1 hit, we were drowning in reqs, and it fell off the map. That's fair, that's on us.
Rep
Then that's a fixable problem and I'd rather solve it than sell against a ghost. Here's what I'd suggest — twenty minutes with you and your delivery director. Not a demo, no deck. I'll bring redeployment and submittal-to-interview benchmarks from IT staffing firms in your headcount range, and if your 31 and your ratios already beat them, we're done and you've got a slide for your ops meeting. Thursday at 8:15 before the day starts, or Friday at 11?
Buyer
Send me something first and I'll see if it's worth pulling Elena in.
Rep
I'll send it either way. But a PDF won't tell you whether it fits your desk math, and you'll bin it — I would. Give me the Thursday slot with Elena on it; if the first five minutes aren't relevant, say so and I'll drop off and you've got your morning back.
Buyer
Fine. Thursday 8:15, twenty minutes, and I mean twenty. Elena's on it or it doesn't happen.
Rep
Done. Sending the invite now with Elena copied — subject line says 'redeployment benchmarks, 20 min.' Can you tell me it's landed before I let you go?
Buyer
Just came through. Talk Thursday.
Objections you will hear
What they say, and what you say back.
| Objection | How to answer it |
|---|---|
| “Our ATS already claims to do that.” | Most do — the module exists and it's probably licensed. Pull it up right now and tell me what percentage of your submittals had three or more logged touches after the shortlist went out. If your team's like most, the feature's paid for and unused because it depends on a recruiter remembering to set the sequence at 6pm. I'm not asking you to replace Bullhorn. I'm asking whether the follow-up actually happens when nobody remembers. |
| “Margins are thin this year — new spend is frozen.” | Understood, which is exactly why I'd rather talk redeployment than spend. What's your rate on contractors rolling off? If it's in the twenties, every point you move it is a placement you don't pay to source — same bill rate, no job board spend, no recruiter hours. Show me the number and if the math doesn't clear the cost, I'll leave it alone until budgets open. |
| “My recruiters won't use another tool. They're already in four systems.” | Fair — if it's a fifth login it fails, full stop. Where does your team actually live, ATS and phone mostly? If the follow-ups fire from the record they're already in and the recruiter only sees the ones that need a human, it stops being a training problem. But you'd know better than me — what happened last time you rolled something out? |
| “Automated follow-up is going to feel like spam to my clients. These are relationships.” | Agreed — a hiring manager who gets a generic drip is a hiring manager who blocks the whole domain. What I'm describing is structure, not blast: the recruiter's own voice, a defined cadence, an actual reason to reach out each time. The alternative isn't high-touch relationship, it's your recruiter chasing twice and quietly giving up. Which is what's already happening on the reqs that go dark. |
| “We tried something like this two years ago and it didn't stick.” | What broke — the tool or the process around it? Nine times out of ten nobody owned the cadence and it died in month two. I'd want to know who owned it, what the first thirty days looked like, and whether anyone reported on touches weekly. If that's the story, that's fixable, and I'd rather solve it than sell against a ghost. |
| “We're a relationship shop, not a volume shop. This feels like a high-volume play.” | Then the ghosting costs you more, not less. A volume desk absorbs a dead shortlist; you've got fewer, bigger accounts and each one that goes quiet is real spread. How many of your top ten clients went silent on a submittal last quarter — and did anyone find out why, or did the req just close in the system? |
| “Send me some information and I'll circulate it internally.” | Happy to, but a PDF won't tell you whether this fits your desk math. Twenty minutes with you and whoever runs delivery — I'll bring redeployment and submittal-to-interview benchmarks from firms your size in your verticals, and if your numbers already beat them we're done and you've got a data point for your ops meeting. Thursday at 8:15 or Friday at 11? |
| “I'm not interested.” | Totally fair, you don't know what I do yet. If I'm wrong I'll hang up — is the low-twenties redeployment number a thing at your firm, or have you genuinely got that one closed out? |
Questions reps ask about this call
- What should the first line of a staffing / recruiting cold call script be?
Name, company, and an honest admission that it's a cold call, followed by a permission ask with downward inflection: "Hi Priya, it's Marcus at Cordell. We haven't spoken — this is a cold call. Can I have thirty seconds and then you can tell me to get lost?" Then pause two full seconds. Staffing leaders came up on the phone themselves; the fastest way to lose a VP of Recruiting or Managing Director is a rehearsed "how are you today." Naming the cold call collapses the suspicion loop so they stop trying to place you and start listening.
- Which problem should I lead with when cold calling a staffing firm?
Pick one, not three, and match it to the title. For a Director of Delivery or Director of Contractor Care, lead with redeployment — contractors rolling off a nine-month assignment with no conversation since onboarding, and a redeployment rate sitting in the twenties against a target north of fifty. For a VP of Recruiting, Practice Lead or CRO, lead with the shortlist that goes into the void: three profiles out Tuesday, "reviewing this week," then silence, and a submittal-to-interview ratio that rots while the req shows 'submitted' in the ATS. Write your single lead problem down before you dial.
- How do I handle "our ATS already does that" on a cold call?
Don't argue with the feature — ask about the behaviour. "Most do, the module's licensed. Pull it up and tell me what percentage of your submittals had three or more logged touches after the shortlist went out." Nearly every firm has the sequencing capability and nearly none have it running, because it depends on a recruiter remembering to set it at 6pm from memory. Frame yourself as additive to Bullhorn or JobDiva, never as a rip-and-replace — that's an instant no from a Managing Director with margin pressure.
- What metrics should I actually name in the script?
Use the numbers the buyer gets asked about in Monday pipeline reviews: redeployment rate on contractors rolling off, submittal-to-interview and interview-to-placement ratios, placements per recruiter per month, fall-off inside 30 to 90 days, and bench days. Reference them as things you'll benchmark together, not as market claims you're asserting. "Where does your redeployment sit, roughly?" earns more than any statistic you quote at them.
- How do I get past the margin objection when the firm is mostly MSP/VMS work?
Stop talking about spend and start talking about placements they don't have to pay to source. If bill rates are capped at 12-15% and ownership's answer is "do more with the same headcount," the only lever left is recruiter productivity — so anchor on redeployment and fall-off. Every point of redeployment is a placement with no job board spend and no re-sourcing hours against a person already background-checked. Then offer the exit: "show me the number, and if the math doesn't clear the cost I'll leave it alone until budgets open."
- What counts as a successful staffing cold call if they won't book?
A dated reason to call back plus one piece of intelligence. Ask: "Is this a timing thing or a not-a-priority thing?" then "When does delivery set targets for next year?" A logged disposition of "callback first week of October, target-setting, redeployment at 31%" is pipeline. "Send me an email" with nothing traded for it is a polite hang-up and an unopened message. When you do book, send the invite while they're still on the line and ask them to confirm it landed — verbally-agreed meetings calendared later no-show at a much higher rate.