Staffing / Recruiting · Warm Call
Warm Call Script for Staffing / Recruiting: Cashing a Referral Before It Cools
Somebody's Managing Director downloaded your redeployment benchmark and told you to call his old colleague at a competing shop. Or a Practice Lead you met at Staffing World fired off a three-line intro on a Friday that your prospect skimmed in an Uber and archived. Either way you're about to dial a VP of Recruiting or a Director of Delivery who will pick up, will remember the referrer's name, and will not have the faintest idea what you sell.
That's the whole gift: the pickup, about ninety seconds of suspended disbelief, and permission to be direct without the usual three-minute warm-up. It does not buy you a problem. The referrer's shop might be running 400 contractors through an MSP with redeployment in the twenties; your prospect might be a boutique direct-hire desk in life sciences where the word "redeployment" means nothing. Transplant the referrer's pain onto them and they'll hear, correctly, that you researched the wrong person.
This playbook gives you the provenance line, the relevance bridge, three questions that fit inside four minutes, and a close that produces a diary slot with the Director of Contractor Care on it rather than a PDF nobody opens. Warmth decays at the speed of generic — every sentence you could have said to any staffing firm in the country burns ten seconds you don't have.
The warm call script
Say it in your own words. The structure is the part that matters.
- 1
Pre-call: write the provenance line before you dial
One sentence, out loud, before the phone rings. Small and checkable. "[Referrer] mentioned you because [specific reason]." Good: "Marisol Vega pulled down our redeployment benchmark last month and said you'd just taken the IT practice at Halversen after they folded the two branches together." Dead: "Marisol thought you'd be interested in what we do." Also decide, before you dial: - **Exactly what you're allowed to say the referrer said.** If Marisol said "you should call Trent," you say "Marisol said I should call you." Not "Marisol said you'd be really interested." Staffing is a small industry and these people sit on the same ASA panels. - **Your relevance hypothesis about THEIR desk.** New in role, a branch merge, an MSP win, a Job posting for six contract recruiters, a vertical they just stood up. - **Assume the intro email was never read.** Have a 15-second re-brief in staffing language, no product name. - **Which two metrics you'll name.** Pick from redeployment rate, submittal-to-interview ratio, fall-off inside 30-90 days, placements per recruiter per month. Two. Not six.
- 2
The open — name, provenance, permission (25 seconds)
"Trent — Sam Whitfield, from Harlow. Marisol Vega said I should call you. She picked up a piece we did on redeployment rates and mentioned you'd taken over the IT practice at Halversen when the two branches merged in January. She may have been overselling my usefulness. Have you got four minutes for me to find out whether that's true, or should I come back?" If they say **"Right, Marisol said you'd call"** — that's the entire warmth budget landing in your hand. Five words of acknowledgement, then move: "Good, she said she'd flag it. Then I'll be quick." Do not ask how they know Marisol. It costs three minutes and returns nothing.
- 3
If they can't place the referrer
Happens on half these calls. Don't argue them into remembering it. "No reason you would — it was a two-line intro on a Friday. Short version: I work with staffing firms on what happens to a submittal after it's been sent, and to a contractor after the assignment ends. Redeployment, mostly. That's the whole thing. Worth four minutes, or not really?"
- 4
The relevance bridge — where the call lives or dies
Their credibility becomes your relevance, inside the first minute. Three beats: what the referrer's world looked like → why yours is different → a question that hands them control. "What Marisol was dealing with was 380 contractors on billing through two VMS programs, and nobody talking to any of them between onboarding and the last Friday of the assignment. Her redeployment rate was sitting around 24%. That's her shop, not yours. You're mostly direct hire and contract-to-hire from what I can see, and you've got a Contractor Care function she doesn't have. So I genuinely don't know if this lands. When a contract ends at Halversen — who owns the conversation with that person, and when does it start?" Naming the reason you might be irrelevant is the fastest credibility move on a warm call. It kills the "here comes the pitch" brace.
- 5
Discovery — three questions, four at the outside
You have four to twelve minutes and no agenda they agreed to. Eleven questions reads as an abuse of the referral. **1. Mechanical current state.** "Walk me through it — recruiter sends three profiles Tuesday, hiring manager says 'reviewing this week.' What actually happens on day four? Who touches it?" **2. Cost in their numbers.** "Where's your submittal-to-interview ratio sitting this quarter versus last? And on the contract side, what percentage of people rolling off end up back on billing with you inside 30 days?" **3. Priority test — the one that saves you a wasted meeting.** "Is that a this-quarter problem, or a live-with-it problem? Because if the owner's only asking about gross profit per placement right now, I'd rather know." **Optional fourth:** "Who else would care about this — does your Director of Contractor Care own redeployment, or does it sit with the account managers?" Listen for the correction. When they say *"honestly it's less the follow-up, it's that I can't tell from Bullhorn whether the follow-up happened"* — write that sentence down verbatim. It goes in your email and on the second meeting agenda.
- 6
Reading the cool-off
Warmth withdraws politely. The tells: - Answers shorten. "Yeah. Yeah, makes sense." - They narrate logistics: "Can you send something over?" - They ask about pricing before you've established a problem. - They invoke the referrer as an exit: "Well, if Marisol rates you..." Stop and name it: "I'm getting the sense this isn't the pressing thing on your desk right now — which is fine, Marisol was guessing. Is it not the problem, or not the moment?" A clean "not the problem" is a good outcome. It protects the referral source and it stops you forecasting a ghost.
- 7
The close — a date, a length, a name, a reason in their words
"Then here's what I'd do. You said the issue isn't the follow-up, it's that you can't tell from the ATS whether it happened — and that redeployment's sitting under 30%. Give me thirty minutes and I'll show you how a firm your size in IT staffing got that number above 50 without adding headcount. I'd want whoever owns contractor care on the call, because they'll poke holes in it faster than either of us. Thursday morning, or Monday after your pipeline review?" If they truly can't commit, take a smaller real thing — and diarise it on your side, not theirs: "Fine. I'll send two paragraphs and one screenshot of the redeployment report. I'll call you Thursday at 8:40, before your team huddle, and you tell me then whether it's worth thirty minutes."
- 8
Close the loop with the referrer — same day, non-negotiable
Two lines, no more: "Marisol — spoke to Trent, thanks for that. His issue is different to yours, it's less redeployment and more that he can't see submittal follow-up in the ATS at all. Meeting him and his contractor care lead Thursday. Appreciate you." This thanks them, tells you whether you can use their name again, and is the only reliable way one referral produces a second. Sources who never hear back stop referring.
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Trent — Sam Whitfield, from Harlow. Marisol Vega said I should call you. She pulled down our redeployment benchmark last month and mentioned you'd taken the IT practice at Halversen after the branch merge in January. She may have been overselling my usefulness. Four minutes to find out whether she was?
Buyer
Marisol, yeah. She sent something, I think. Look, I'll be straight with you — I'm in the middle of a QBR prep for a client who's about to cap us at 14%, so unless this is about bill rates I'm not sure it's my week.
Rep
It's not about bill rates, and I'm not going to pretend it is. Marisol's problem was 380 contractors across two VMS programs with nobody speaking to them between onboarding and the last Friday — redeployment sitting around 24%. That's her shop, not yours. You're heavier on contract-to-hire and you've got a real Contractor Care function. So I don't know if this lands. When an assignment ends at Halversen, who owns that call and when does it start?
Buyer
The account manager's supposed to start at 30 days out. Whether they do is another question. But honestly — we're on Bullhorn with Herefish sitting on top of it. Automation isn't the gap. We bought the gap two years ago.
Rep
Then let me ask the awkward version of that. Pull up a req you submitted on three weeks ago that went quiet. How many logged touches after the shortlist went out — is it three or more, or is it two and then silence?
Buyer
...it's two and then silence. Because the sequence only fires if the recruiter tags the record properly, and my recruiters log activity at six o'clock from memory. That's not a tool problem, that's a discipline problem, and I've been beating on it for a year.
Rep
Fair. So what's your submittal-to-interview ratio doing while that plays out?
Buyer
Down. Roughly one in five last year, closer to one in eight now. Submittals are up though — the team's working. That's the part I can't explain to ownership. Volume's up, placements per recruiter are flat, and the answer from upstairs is do more with the same heads.
Rep
And on the contract side — of the people rolling off in the last quarter, roughly what percentage were back on billing with you inside 30 days?
Buyer
I'd have to check. It's not good. High twenties maybe. We had a guy finish a nine-month at a payer client on the Friday and he was on a competitor's payroll by Wednesday. Background-checked, performance-reviewed, we'd already paid to find him once. That one I actually think about.
Rep
That's the number I'd want to talk about, not the 14% cap. Every point on redeployment is a placement you don't pay to source — same spread, no job board spend, no recruiter hours. But I'll ask the honest question: is that a this-quarter problem for you, or a live-with-it problem?
Buyer
It's this quarter, but I've heard this pitch. We rolled something out in 2022, it died by month two because nobody owned it and the recruiters went back to doing it their way. I'm not doing that again.
Rep
Then that's the conversation, not the demo. What broke was ownership, not software — nine times out of ten it is. Who owned it, what did the first thirty days look like, and was anyone reporting on touches weekly? If nobody was, that's fixable and I'd rather solve it than sell against a ghost.
Buyer
Nobody was. It sat with a recruiting manager who left in the spring. Alright — what are you actually proposing?
Rep
Thirty minutes. You said the two things: two touches and silence on submittals, and redeployment in the high twenties on people you already recruited. I'll bring how a similar IT shop moved that number past 50 without adding headcount, and I'd want your Director of Contractor Care on it — she'll poke holes faster than you or I will. Thursday morning, or Monday after your pipeline review?
Buyer
Thursday, 8:30, and keep it to thirty. Send an invite with an agenda on it — if it says 'discovery call' I'll decline it.
Rep
It'll say 'redeployment rate and submittal follow-up — Halversen IT practice.' I'll get it over in ten minutes. And I'll tell Marisol you took the call.
Objections you will hear
What they say, and what you say back.
| Objection | How to answer it |
|---|---|
| “Bullhorn already does that — we've got the automation module.” | Most ATSs do, the module exists. 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, it's licensed and unused because it depends on a recruiter remembering to tag the record. I'm not asking you to replace the ATS. I'm asking whether the follow-up actually happens without someone remembering. |
| “Margins are thin this year — the MSP has us capped and new spend is frozen.” | Understood, which is exactly why I'd rather talk about redeployment than spend. What's your redeployment 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 touch a fifth system. They're already in the ATS, LinkedIn Recruiter, the VMS portal and Teams.” | Fair, and if it's a fifth login it fails — I've watched that happen. Where does your team actually live, ATS and phone mostly? If the follow-ups fire off the record they're already in and the recruiter only sees the ones that need a human voice, adoption stops being a training problem. But you'd know better than me — what happened last time you rolled something out? |
| “Automated follow-up will feel like spam to my hiring managers. These are relationships built over years.” | Agreed — a hiring manager who gets a generic drip blocks you and tells his peers. 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 following up twice and quietly giving up. Which is what's 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 it'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 can absorb a dead shortlist; you've got fewer, bigger accounts and each one that goes quiet is real spread off the forecast. How many of your top ten clients went dark on a submittal last quarter — and did anyone find out why, or did the req just close in the system? |
| “Just send me some information and I'll circulate it to the delivery team.” | 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 numbers from firms your size in IT and light industrial, and if yours already beat them we're done and you've got a data point for your next ops meeting. |
Questions reps ask about this call
- How is a warm call script for staffing different from a cold call script?
A cold call spends its first fifteen seconds earning the right to keep talking. A warm call skips that and spends its first sixty seconds proving the referrer wasn't wasting the prospect's time. The structural difference is the relevance bridge: you have to move off the referrer's world — say, a 400-contractor VMS shop with redeployment at 24% — and onto the prospect's, which might be a direct-hire boutique where none of that applies. Cold calls die from being ignored. Warm calls die from being generic.
- What do I say if the VP of Recruiting doesn't remember who referred me?
Don't argue them into remembering. Say: "No reason you would — it was a two-line intro on a Friday." Then give a fifteen-second re-brief in staffing language with no product name: "I work with staffing firms on what happens to a submittal after it's sent, and to a contractor after the assignment ends." Then ask for four minutes. Trying to reconstruct the intro chain in front of them makes the whole thing feel thinner than it is.
- Which metrics should I put in the script itself?
Two, not six. Pick the pair that fits the buyer's seat. For a Director of Contractor Care or a Managing Director running a contract book, use redeployment rate on people rolling off and fall-off inside 30-90 days. For a VP of Recruiting or Head of Talent Delivery on a perm-heavy desk, use submittal-to-interview ratio and placements per recruiter per month. Ask for their number rather than quoting one at them — "what percentage are back on billing inside thirty days?" starts a diagnosis, whereas a benchmark you assert starts an argument.
- How long should a warm call to a staffing leader actually run?
Ask for four minutes and mean it. If it's working you'll get eight to twelve — most Practice Leads and Branch Managers will keep talking once they've said their submittal-to-interview ratio out loud. Three questions maximum: mechanical current state, cost in their numbers, priority test. Running full discovery because they were friendly is the fastest way to get "can you just send me a deck."
- What counts as a successful outcome if they don't book?
A clean "not the problem" is a good outcome — it protects the referral source and stops you forecasting a ghost for a quarter. Second best is a smaller commitment you own: two paragraphs plus one screenshot of a redeployment report, and a specific callback time in your diary, not theirs. What isn't a good outcome is a pleasant call that ends in "send info" with no date, which is how most warm calls in staffing quietly end.
- Do I really need to close the loop with the referrer?
Yes, same day, two lines. Tell them you spoke, tell them what turned out to be different about the prospect's situation, tell them what happens next. It's the only reliable mechanism by which a Managing Director who gave you one intro gives you a second, and it tells you whether you're clear to use their name in that vertical again. Staffing is a small industry — referral sources who never hear back stop referring, and they mention it to each other.