Freight / 3PL · Warm Call
A Warm Call Script for Freight / 3PL Reps Who Get Ninety Seconds of Borrowed Goodwill
It's 7:40am and the Director of Brokerage Operations you're calling has already looked at the morning board: eleven loads uncovered out of Laredo, a reefer sitting at a receiver in Fontana going into hour four of detention with no timestamped arrival proof, and a coordinator out sick whose 25 loads just got split across three people who were already at capacity. Somebody they respect told them to take your call. That's the only reason the phone got answered, and it is worth about ninety seconds.
Warmth is a loan, not a grant. The referral buys you the pickup, a short window where they won't hang up at second twelve, and permission to ask a direct question without earning it first. It does not buy you interest, a problem, or a pitch slot. The fastest way to burn it in this industry is to say the words "end-to-end visibility" — because whoever referred you is the fifth person this year to walk a visibility story into that office, and your prospect can recite the deck from memory. Two generic sentences and you've converted a warm call into a cold call the prospect now feels mildly embarrassed to be on.
This script does three things in under five minutes: names the referrer immediately and says exactly what they said, bridges from the referrer's operation to this brokerage's numbers — check calls per load, tracking compliance rate, loads covered per coordinator per day — and closes on a diarised second meeting with an ops lead's name attached. It also tells you when to stop, because a clean "not the problem" protects the person who referred you and saves you a quarter chasing a ghost.
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. Not "Marcus thought you'd be interested." That's nothing. "Marcus Deel at Ridgeline pulled down our check-call benchmark last month, and he said you'd taken over brokerage ops at Calder in January when they folded the two branches together." Small, checkable, about them. Then pre-decide three more things: 1. **What you're allowed to say Marcus said.** If he said "you should call Tasha," you say exactly that. Never inflate it to "Marcus said you'd really want to see this." Carrier sales directors in the same market talk to each other constantly. Getting caught embellishing costs you two relationships in one call. 2. **Your relevance hypothesis** — one line about *their* shop. Built off a trigger: new in role, a branch consolidation, an acquisition, a job ad for four track-and-trace coordinators, a shipper award they announced on LinkedIn. 3. **The 15-second re-brief.** Assume the intro email was skimmed on a phone in the yard and archived. Plan for them not remembering.
- 2
The open — name, referrer, provenance, permission (25 seconds)
"Tasha — Sam Whitfield, from Harlow. Marcus Deel at Ridgeline suggested I call you. He picked up something we put out on check calls per load and mentioned you'd inherited brokerage ops at Calder when the Memphis and Dallas desks got merged. He may have oversold my usefulness. Have you got four minutes for me to find out whether this is even relevant, or is now a bad time?" Four beats, that order, no deviation. Name. Referrer in sentence two. The specific reason they thought of you. A permission question with a time box. If they say **"Yeah, Marcus said you'd be calling"** — that's the entire warmth budget being handed over. Do not spend it asking how they know Marcus. Five words and move: "Good, he said he'd flag it. Then I'll be quick."
- 3
If they don't remember the referrer
Happens more often than not. Do not argue them into remembering. "No reason you would — it was a two-line intro on a Friday afternoon. Short version: we cut the number of check calls a coordinator has to make per load, and the update lands in the load record in your TMS rather than in another portal. That's the whole thing. Worth four minutes or not really?" No company overview. No founding story. If they still don't bite, take the no and protect the referrer: "Fair enough — I'll tell Marcus I caught you in the middle of peak."
- 4
The relevance bridge — the move the call lives or dies on
This is where warm calls die, because reps transplant the referrer's pain wholesale. Different carrier mix, different TMS, different mandate. Structure it: **the referrer's world → why yours might be different → a question that hands them control.** "What Marcus was dealing with at Ridgeline was small-fleet heavy — a lot of one to five truck carriers on the Laredo lanes, tracking compliance sitting well under where his shippers wanted it, and coordinators making six or seven check calls a load to fill the gaps. That's his shop. You're running more contract volume and I think a bigger asset-lite carrier base, so honestly I don't know if this lands the same way. When one of your coordinators is covering their 25 or 30 loads a day, how many times are they actually picking up the phone on a single load?" Naming a reason you might be irrelevant is the fastest credibility move available on a warm call. It reads as honest, and it drops the "here comes the pitch" brace.
- 5
Discovery — three questions, four at the outside
This is not a booked discovery call. You have four to twelve minutes and no agenda they agreed to. Eleven questions reads as an abuse of the referral and gets shut down with "just send me a deck." **1. Mechanical current state:** "Walk me through it — when a load tenders at 6am, who touches it between tender and delivered? Is that a dedicated track-and-trace desk or is the coordinator who covered it also chasing the driver?" **2. Cost or friction, in their numbers:** "What's your tracking compliance rate looking like right now — percentage of loads where you've got an automated location rather than a coordinator's typed note? And when a load goes dark, who finds out first, you or the shipper?" **3. Priority test — the one that saves you a wasted follow-up:** "Is that a this-quarter problem, or is it a live-with-it problem until after peak?" **Optional fourth:** "Besides you, who'd care about this — is that your VP of Ops, or does your CIO own anything that touches the TMS?" Listen for the correction. When they say *"it's not really the check calls, it's that I can't defend my on-time delivery number in a QBR because the data behind it is a note somebody typed"* — that's the call working. Write the phrasing down verbatim. It goes in the follow-up email and the second meeting agenda.
- 6
Reading the cool-off
Warmth withdraws politely in freight. The tells: answers get shorter and more agreeable. They start narrating logistics — "can you send something over." They ask what it costs per load before you've established a problem. Or they invoke the referrer as an exit: "Well, if Marcus rates you." Stop talking and name it: "I'm getting the sense this isn't the pressing thing this week — which is fine, Marcus was guessing on my behalf. Is it not the problem, or not the moment?" A clean "not the problem" is a good outcome. It protects the referral and it stops you spending Q4 on a ghost. A "not the moment" gives you a date.
- 7
The close — a meeting with a date, a length, and a name on it
The number one failure on a warm call is a pleasant conversation that ends in "send me some info." Friendly is not progressed. Close on their words, not yours. "Then here's what I'd suggest. You said the problem isn't the check calls, it's that you can't defend the on-time percentage in a QBR because the timestamp is a typed note. Give me thirty minutes and I'll show you exactly how that data lands back in the load record in McLeod, and what the tracking compliance number looked like at a brokerage running your carrier mix — small fleets included, not a 98% fantasy. I'd want whoever runs your track-and-trace desk on it too. Thursday at 7:30 before the board fills up, or Monday afternoon?" Must be present: a date, a length, a reason built from their language, and who else should attend. If they genuinely can't commit mid-peak: "I'll send two paragraphs and one screenshot of the load record view. Pull your check calls per load for one week and tell me on Thursday whether it's worth thirty minutes." Put Thursday in *your* diary, not theirs.
- 8
Close the loop with the referrer the same day
Non-negotiable, routinely skipped. Two lines: "Marcus — spoke to Tasha, thanks for that. Her issue's a bit different to yours; it's less about check-call volume and more that she can't defend on-time delivery in a QBR. Meeting her and her track-and-trace lead Thursday. Appreciate the intro." This thanks them, tells you whether you can use their name again in that market, and it's the only reliable way one referral turns into a second. Sources that never hear back stop referring.
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Tasha — Sam Whitfield, Harlow. Marcus Deel at Ridgeline suggested I call. He picked up something we put out on check calls per load and said you'd taken over brokerage ops at Calder when the Memphis and Dallas desks merged. He may have oversold my usefulness. Four minutes to find out if this is relevant, or bad timing?
Buyer
Marcus. Yeah. Look, I've got eleven loads uncovered out of Laredo for tomorrow and a coordinator out, so four minutes is generous. And I'll save you some of it — I've sat through this exact pitch four times this year. Everybody's got visibility.
Rep
Fair, and most of them are selling you a map. So let me not do that. Two numbers I'd ask about instead: what your tracking compliance rate actually is, and how many loads went dark last month on lanes a shipper cared about. Do you know either of those off the top of your head?
Buyer
Compliance is somewhere in the low sixties. It's been in the low sixties for two years. And it's not a technology problem, it's a carrier problem. My small guys — the one and two truck operations that are the only ones who'll take a hot load out of the Valley — they decline the ping or they kill location sharing the second they're loaded. I'm not losing capacity over an app.
Rep
Agreed, and I'd never make you pick between coverage and visibility — you'd pick coverage and you'd be right. What did Marcus's mix look like versus yours? His was small-fleet heavy on the border lanes. Is yours the same shape, or do you have a core group carrying most of it?
Buyer
Most of my volume runs on maybe fifty to sixty carriers. The dark ones are the one-offs I'm booking off the load board at four in the afternoon.
Rep
That's a different problem from the one Marcus has, then. Your top fifty are an onboarding exercise — ELD integration for the fleets that have it, driver app for the rest, done once through the carrier packet. The 4pm board booking is never going to be 98%, and anyone who tells you otherwise is lying to you. So when one of those goes dark on a load your shipper's watching, who finds out first — you or them?
Buyer
Them, usually. Their plant calls my rep before my coordinator's called them. That's the part that actually costs me. I lost an account in the spring — three late deliveries, and the third one they heard about from their own receiving dock. Nobody churns over a late load. They churn over the phone call they didn't get.
Rep
How many loads a week was that account?
Buyer
Around forty. And before you do the math out loud at me — yes, I know what that was worth in net revenue per load. Here's my actual problem. We spent eighteen months and real money getting this team onto McLeod and half my coordinators still run their day out of a spreadsheet and Outlook. If your thing is a second screen they have to go look at, they will quietly not use it and I'll have paid for it anyway.
Rep
Then say no to it, because you'd be right. The only version worth your time is fewer screens, not more. Which McLeod are you on — LoadMaster, and is your integration API or are you still passing flat files? Because that determines whether the location update writes into the load record where the coordinator already works, or whether it sits somewhere else and you've bought yourself a fifth portal.
Buyer
LoadMaster, API. Our IT director handles it. But I'll tell you now, we're mid-cycle with a provider until June, so even if I liked this I couldn't move.
Rep
Then I won't pretend otherwise. What's the thing your current provider doesn't do? Usually it's one of three: carrier onboarding is a slog, the data doesn't flow back into the TMS cleanly, or the shipper-facing portal is bad enough that you're still emailing PDFs.
Buyer
Onboarding. It's on us to chase every carrier and my carrier sales team won't do it because it slows down booking. That's why compliance is stuck in the sixties.
Rep
That's the useful answer, and it's a fixable one — it's a carrier packet workflow problem more than a product problem. So here's what I'd do rather than waste your June. Thirty minutes, before the board fills up, and I'll walk you through exactly how onboarding runs at a brokerage with your carrier mix — including what their compliance number actually landed at, small fleets included. I'd want your track-and-trace lead on it, and if your IT director wants to sanity check the LoadMaster write-back, bring them. Thursday at 7:30, or Monday after the 3pm push?
Buyer
Thursday, 7:30. Thirty minutes and if it turns into a demo of a map I'm hanging up.
Rep
No map. Two things: the onboarding flow and one screenshot of the load record. If you can have somebody pull your check calls per load for one week beforehand, we'll talk about your numbers instead of mine. Invite's coming in the next ten minutes — go cover Laredo.
Objections you will hear
What they say, and what you say back.
| Objection | How to answer it |
|---|---|
| “Every freight tech company that walks in here promises visibility. I've heard this exact pitch four times this year.” | "Fair — and most of them are selling you a map." Don't defend the category, change the unit of measure. Ask the two numbers nobody else asks: how many check calls per load their coordinators are making today, and how many loads went dark last month on lanes a shipper cared about. Then be specific about which of those two you move and what the before and after looked like at a brokerage their size and carrier mix. Vague visibility loses to a number every time. |
| “We fought for eighteen months to get people onto the TMS and half of them still aren't fully on it. Another tool isn't going to stick.” | Agree out loud first — this is the one where arguing kills you. Then reframe: it shouldn't be another tool, it should be fewer screens. Get concrete immediately. Which TMS, which version, API or flat file, and does the update land in the load record where the coordinator already works? If your answer is that it creates a second place to look, say so and lose the deal honestly. Coordinators who have to add a click will quietly refuse, and the Director of Brokerage Operations knows it better than you do. |
| “My carriers won't accept tracking. The small guys decline the ping and I'm not losing capacity over it.” | Never make it capacity versus visibility — you lose that argument and you deserve to. Talk multi-source: ELD integration for the fleets that have it, driver app for the ones that'll take it, and be honest about what happens on the rest. Quote a realistic tracking compliance rate for their carrier mix, not 98%. Then ask what percentage of loads run on their top fifty carriers. It's usually most of them, and those are the ones you onboard first through the carrier packet. |
| “What's this going to cost me per load? My margins are already thin — contract rates were bid at last year's numbers.” | If they ask price before you've established a problem, it's usually a polite disqualification. Put it against ops cost they already carry: if a coordinator handles 25 loads a day and loses three hours to check calls, price the recovered time in loads covered per coordinator per day, not in dollars saved. Then go to the account they lost: "How many loads a week was it?" Forty loads a week at $200 net revenue per load reframes a per-load fee in about four seconds. |
| “Our shippers aren't asking for this. They're happy with the status emails we send.” | "They're not asking you — they're asking the broker bidding against you." Then get factual: what did the last three RFPs require for visibility and EDI 214 status messaging, and was it scored? Most enterprise shippers score it in the bid now. Position it as bid eligibility for the VP of Sales on the shipper side, not as a service upgrade for ops. |
| “Send me something and I'll look at it. We're heads-down on peak.” | Don't fight the calendar, use it. "Peak is exactly when your coordinators are drowning — that's the week I'd want you looking at check calls per load, not January when everything's calm and the number lies to you." Offer twenty minutes with them plus one ops lead, and ask them to pull one week of load volume beforehand so it's their data on the table. If they still won't commit, take the smaller yes and diarise the follow-up on your side. |
| “We're mid-cycle with a provider until June. Come back at renewal.” | Get the renewal date, then find the gap: "What's the thing they don't do?" It's almost always one of three — carrier onboarding is a slog, the data doesn't write back into the TMS, or the shipper-facing portal is bad enough that they're still emailing PDFs. Build the follow-up around that specific gap, and book it sixty days before renewal, not after. By renewal the incumbent has already re-signed them. |
| “If Marcus rates you, send me the deck and I'll take a look.” | This is the cool-off dressed as a compliment. Name it: "I think this might not be the pressing thing for you right now — which is fine, Marcus was guessing on my behalf. Is it not the problem, or not the moment?" A clean 'not the problem' protects the referral and frees your quarter. If it's 'not the moment,' you get a date, which is more than a deck would have got you. |
Questions reps ask about this call
- How is a warm call script for Freight / 3PL different from a cold call script?
A cold call has to earn the right to ask a question in the first twenty seconds. A warm call already has it — the referral buys you the pickup, roughly ninety seconds of suspended disbelief, and permission to be direct. What it does not buy is interest, budget, or a problem. The practical difference is that you skip the hook entirely and go straight to a relevance bridge: what the referrer's brokerage was dealing with, why this prospect's carrier mix or TMS might make it irrelevant, then one question about their operation. Reps who treat 'warm' as 'qualified' show up with a solution and no diagnosis.
- What if the Director of Brokerage Operations doesn't remember the person who referred me?
Assume they don't. The intro email was skimmed on a phone between covering loads and archived. Don't argue them into remembering it — give them cover and re-brief in fifteen seconds: 'No reason you would, it was two lines on a Friday. Short version: we cut check calls per load and the update lands in the load record in your TMS, not in another portal. Worth four minutes?' No company overview, no founding story. If it's still a no, take it cleanly so the referrer doesn't hear you were pushy.
- Which metrics should actually appear in the script?
Two or three, no more, and only ones the buyer is personally measured on. For a VP of Operations or Director of Brokerage Operations, the live ones are check calls per load, tracking compliance rate, loads covered per coordinator per day, and on-time pickup and delivery percentage. For a COO or Branch Manager, net revenue per load and net revenue per head are what leadership reviews weekly. Ask for their number rather than quoting one at them — 'what's your tracking compliance sitting at?' outperforms any benchmark you could recite.
- How do I handle the tracking compliance objection without losing the call?
Never frame it as capacity versus visibility, because every Director of Carrier Sales will choose capacity and end the conversation. Concede the point about the one-to-five truck operations immediately — they're right, those carriers decline pings. Then split the base: ask what percentage of volume runs on their top fifty carriers. It's usually most of it, and those are a one-time onboarding exercise through the carrier packet. Be honest that the 4pm load board booking will never be fully compliant. Quoting 98% to a freight operator destroys your credibility instantly.
- What counts as a successful warm call outcome in freight?
A booked meeting with four components: a date, a length, a reason built from their own words, and the name of one more person — usually whoever runs the track-and-trace desk, or the CIO / Director of Logistics Technology if TMS write-back came up. 'Send me some info' is not a successful outcome, it's a pleasant one. A clean 'this isn't the problem' is also a success: it protects the referral relationship and stops you spending peak season chasing a deal that was never there.
- Do I really need to tell the referrer what happened?
Yes, same day, two lines. Freight is a small world and carrier sales directors in the same market compare notes constantly. Closing the loop thanks the person, tells you whether you can use their name again in that lane, and is the single most reliable way one intro turns into a second. Sources who never hear back stop referring — and in this industry that closes off a whole market segment quietly.
- How do I practise this without burning a real referral?
Run it out loud before you dial. The specific failure points are the first twenty-five seconds and the relevance bridge, and both are muscle memory problems, not knowledge problems. Roleplay a Director of Brokerage Operations mid-peak who opens with 'I've heard this pitch four times this year' and pushes back on carrier compliance and TMS fatigue, and keep going until you can say 'that's his shop, not yours, so I don't know if this lands' without it sounding rehearsed. Referrals are finite. The reps who waste them are the ones improvising the open.