Freight / 3PL · Renewal Call
Freight / 3PL Renewal Call Script: How to Save a Visibility Account Six Weeks Before It Walks
The contract ends in six weeks. You sold them automated track-and-trace across eight branches and 140 seats, and twelve months later the only desk that truly runs on it is the reefer desk in Fresno. Tracking compliance sits at 61% company-wide and 58% on the 1–5 truck carriers who cover their worst lanes — which means the loads that go dark are still exactly the loads their biggest shipper calls about. Their coordinators are still making six check calls a load and still copy-pasting ETAs into three shipper portals. And in June, during produce season, ticket 41-882 sat nine days without a first response while their EDI 214 status messages stopped flowing to their largest account.
The Director of Brokerage Operations taking this call has already half-decided to leave. A competitor rep has been in their inbox since October with a number 28% lower. They're taking the meeting partly to say out loud what went wrong — and partly to see whether you know. If you open with "so, what would it take to get this renewed," you confirm every suspicion they have: that you only show up when money is due, and that you never looked at their account between QBRs.
This playbook is the opposite move. You go first, by ticket number and date. You let it be worse than you thought. You apologise once, specifically, and then you show them their own data — not a company-wide support stat — and a 90-day plan with names and dates on both sides of the table. The order form is the last five minutes of a thirty-minute call. Run it in that order and the same person who was drafting a cancellation email starts negotiating with you instead of against you.
The renewal call script
Say it in your own words. The structure is the part that matters.
- 1
Before the call: the renewal autopsy
Do not dial until you can say these numbers from memory. • Every ticket from the last 12 months by ID, open date, first response time, resolution time. Know the three worst by number. Ours: 41-882 (opened June 3, nine days to first touch, EDI 214 feed down to their top shipper), 42-107, 42-311. Median first response April 14 – June 20 was 61 hours against a 24-hour SLA. We missed it eleven times. • Adoption by desk and branch, month over month. Not "adoption is 40%". Fresno reefer desk: 94% weekly active, 3.2 check calls per load, 31 loads covered per coordinator per day. Dallas dry van and the three East branches: peaked at 34% in March, flat since. 140 seats billed, 61 weekly active. • Tracking compliance by carrier tier. Overall 61% against the 85% on the original business case. Top 50 carriers: 79%. Everything under five trucks: 58%. • CSM/AE turnover on our side. Two CSM changes in fourteen months. That's ours. Name it before they do. • Every QBR commitment we didn't deliver: the carrier onboarding sprint promised in the Q1 QBR, rescheduled twice, never run. The flatbed macro set. Write them down. • Their org changes. Did the Director of Brokerage Operations who signed still own the budget? Did a new COO come in? Is there a new CIO / Director of Logistics Technology now sitting between us and the buy? • Escalations: did anything reach their VP of Operations or COO? Pull the email where someone wrote "this is unacceptable." Then get written internal alignment before you dial: what Support leadership will actually commit to (named engineer, tier, SLA), and what carrier onboarding resource CS will actually fund. Decide your floor on price, term and seat count now. A second broken promise ends this account permanently.
- 2
Opening: name it before they have to
"Before anything else — I know the contract's up on the 31st. I'm not here to talk about renewal yet. I want to talk about this year, because from where I'm sitting it wasn't the year we sold you. Here's what I can see. Ticket 41-882 went nine days without a first response, and that was June third — the middle of produce season, with your 214s down to your biggest account. Between April and June our median first response on your tickets was 61 hours against the 24-hour SLA you're paying for. We missed it eleven times. You've had two CSMs in fourteen months, and the second one you basically had to re-onboard yourself. We sold you 85% tracking compliance. You're at 61%, and 58% on the small carriers — which is the tier that covers your hard lanes, so the loads that go dark are the ones your shipper calls about. And you're billed for 140 seats with 61 people weekly active. Fresno runs on this. Dallas and the East branches never got past a third. That's my side of it. What am I missing, and what did it actually cost you?" Then stop talking. Do not fill the silence. The meeting is won in the next ten seconds.
- 3
The listening phase: let it be worse than you thought
Budget fifteen of your thirty minutes here. No "but." No "to be fair." Do not defend a single ticket — not even the one where their coordinator never enabled the driver app. Use these: • "Tell me about those two weeks in June. What were the coordinators actually doing?" • "When the 214s stopped, who found out first — you or the shipper?" • "Did this show up in a QBR with them? What did your on-time delivery number look like in that deck?" • "Who did you have to explain this to internally — did it get to the COO?" • "You championed this. What did that cost you politically?" Follow the emotional word. If they say "we were running blind on 400 loads," say "tell me about those 400 loads." Write it down visibly and read it back: "So: the June response times and the 214 outage during produce season, the carrier onboarding sprint we promised in the Q1 QBR and never ran, Dallas never getting trained, and you finding out about the January maintenance window from your own coordinators instead of from us. What else?" Ask "anything else?" twice.
- 4
The apology: once, specific, unhedged
"The Q2 response times were our failure. We reorganised support in March, your queue got routed behind enterprise escalations, and nobody caught it until you escalated. That's an explanation, not an excuse — you paid for a 24-hour SLA and we missed it eleven times, in your busiest eight weeks of the year. And the carrier onboarding sprint we committed to in the Q1 QBR never happened. I own that one personally; I rescheduled it twice." One apology. Then move. Do not apologise again later in the call — repeated apology reads as a negotiating posture.
- 5
Proof of change: their data, not our press release
Only three things carry weight here. Use their numbers. 1. Structural change with a date: "We split the support queue by segment on August 12 and added a brokerage-only tier. Since September 1 your median first response is 3.4 hours across 14 tickets. Here's the list, with IDs and timestamps — check it against your own inbox." 2. Something already done, unasked: "Last week I had the carrier team run your top 50 by load count through onboarding — 38 of them are now on ELD integration rather than the app, which is why your compliance on that tier moved from 71% to 79% in six weeks. You didn't ask for that and I didn't want to bring it up as a promise." 3. Evidence from a brokerage their size: "There's a brokerage in the Southeast, about 1,100 loads a week, that had the same Q2 experience we gave you. Their Director of Carrier Sales will take a call from you and tell you exactly what we were like to work with while we fixed it. I'd rather you heard it from him than from me." If nothing structural has changed, say so and change what you control: your own coverage cadence, a named escalation path, an executive sponsor. Do not manufacture progress. They will check.
- 6
Rebuild on what actually works
"You said Fresno wouldn't give this up. Tell me why — who built that workflow?" Then quantify it in their language, out loud: "Fresno is at 3.2 check calls per load. The East branches are still at 6.4. That desk is covering 31 loads per coordinator per day against 22 everywhere else. That's not a feature preference, that's nine loads a day per head. If we went away Monday, whose morning breaks first — and is that person on this call?" Get the name. That's your remaining champion and they almost certainly weren't invited. Ask to bring them into the plan review. Then say the switching cost plainly, once: "The thing you'd be rebuilding isn't the license. It's whatever your reefer desk built on top of it, plus twelve months of arrival and departure timestamps you'd currently use to fight a detention claim."
- 7
Surface the competitor before they do
"I'd assume you've had [Competitor] in your inbox since the fall. I'd be surprised if you hadn't. What did you like about it?" Listen, genuinely, and then find out how far it's gone: • "Have they quoted in writing, or is it still a number in an email?" • "Has your CIO or your logistics tech lead run it through security review yet?" • "Have they scoped the carrier migration — who re-onboards your 340 active carriers, and how long do you run at 40% compliance while that happens?" • "Did they commit to a compliance rate for owner-operators, or did they quote you a fleet number?" Never disparage them. Reframe from price to total switching cost: re-onboarding carriers, retraining the one desk that did adopt, migrating twelve months of timestamped arrivals, the quarter where your on-time delivery percentage in the shipper QBR is defended with coordinator notes again — and the honest one: "the risk that you inherit their version of the Q2 we just put you through, with none of the goodwill and no history with anyone over there." Do not touch price here.
- 8
The 90-day plan, built live
"Can I build something with you right now, on the call, rather than send you a deck? Four fields on every line: what, who by name on both sides, by when, and what done looks like." Draft it out loud: • Carrier onboarding: our team works your top 100 by load count, ELD integration first, driver app second. Owner: [named CS lead]. Start the week of the 14th. Done = tracking compliance on that tier at 85%+ by day 60, measured in your own dashboard. • Dallas and the three East branches: two live sessions per branch, run against real loads on their board, not a sandbox. Owner: [named CSM] plus your Branch Manager in Dallas. Done = 45 of the 61 untrained users weekly active by day 60, and check calls per load under 4.5 on those desks. • Support: named escalation contact with a direct mobile, 4-hour first response on P1, effective at signature, written into the contract with a service credit attached. • Governance: 30/60/90 reviews, written usage report each time, first one dated on the calendar before we hang up. • The thing I can't do: auto-generating EDI 214s from driver-app pings for non-integrated carriers is not shipping before Q3. I'm not going to pretend otherwise, and I'd rather you plan around it. Then hand it back: "What am I missing? And what does your side need to own? Last year adoption stalled partly because nobody in Dallas was accountable for it. If your VP of Operations doesn't mandate it the way you mandated the TMS, we'll be having this call again."
- 9
Only now: the commercial conversation
"If we can agree that plan is real, can I walk you through what the renewal would look like?" Structure before number: • "You're paying for 140 seats and 61 people are using it. I'd rather right-size to 90 and grow it back as the branches come on than discount 140 seats you don't use. That kills the shelfware conversation permanently." • "On term: I can do twelve months with a break clause at month six tied to the compliance and adoption numbers in that plan. If we miss them, you walk without penalty. That's worth more to you than a discount, and it's how I'd rather be held to it." • Service credits, not a price cut, for the bad months: "For April through June I'll credit the months where we missed SLA. That's specific and it's finite. What I'm not going to do is drop the rate as an apology — a discount would tell you this was always a pricing conversation, and it wasn't." • Any discount is traded: multi-year, a reference call with another Director of Brokerage Operations, a case study on check calls per load, or signature before the 31st.
- 10
Multi-thread and close
"Walk me through what happens between now and the 31st. Who signs — you, or does this go to your COO? Does procurement have [Competitor]'s quote already? Does your CIO need to re-approve anything on the integration side?" Then: • "I want your Fresno lead and your VP of Operations on the plan review. I'll bring our VP of Customer Success — she should hear about June from you directly, not from me." • Book it on the call. A date and a time, not "I'll follow up." • Temperature check, honestly: "On a scale where one is you've already decided to leave — where are we right now, and what specifically moves it?" Take the honest answer over the polite one, and if they say three, ask what a seven looks like. Within 24 hours, send four things: the written 90-day plan with names and dates, the ticket data you quoted, the intro to the reference brokerage, and a one-page summary of what went wrong this year in their words. That last document does more work than any proposal you'll ever send.
How the call actually sounds
Prospect on the left, the rep on the right.
Rep
Before we get anywhere near the renewal — I want to go through this year first, because it wasn't the year we sold you. Ticket 41-882 sat nine days without a first response, June third, right in the middle of produce season, with your 214s down to your largest shipper. Our median first response on your account April through June was 61 hours against a 24-hour SLA. Two CSM changes in fourteen months. And we sold you 85% tracking compliance — you're at 61%, 58% on anything under five trucks. That's what I can see. What am I missing?
Buyer
What you're missing is what 58% means on my board. The 1-to-5 truck guys are the ones covering my Laredo and Fresno lanes — the lanes nobody else wants. Those are exactly the loads that go dark, and those are exactly the loads my shipper calls me about at 4pm. So functionally I bought a system that tracks the loads I was never worried about.
Rep
That's fair and I don't have a rebuttal for it. Tell me about the calls at 4pm. Who was fielding those?
Buyer
My coordinators. Same as before we bought you. They're still making six, seven check calls a load on those desks, still typing arrival times into the load record by hand, still guessing. And then in June, when we couldn't even send the 214s, my shipper's transportation manager found out about two missed appointments from his own plant before he heard from us. I had to sit in that QBR and defend a 91.4% on-time delivery number with coordinator notes. Not GPS. Notes.
Rep
Did that get above you? Did your COO see it?
Buyer
He saw it. He asked me what we were paying you. That's the part I actually want to talk about, because [Competitor] came in 28% under, and they're telling me they'll onboard my carriers themselves.
Rep
I'd assume they had. I want to come back to them properly in a minute — but first, is there anything else from this year I haven't named? Anything else?
Buyer
Yes. The onboarding sprint you promised in the January QBR. Rescheduled twice, never happened. Dallas never got trained, and my Branch Manager down there now tells new coordinators not to bother with it because 'it's a second screen.' We spent eighteen months getting people onto McLeod. I'm not fighting that war twice for a tool that adds clicks.
Rep
The sprint is mine. I rescheduled it twice and then it fell off. That's not a support failure, that's me. And on the second screen — if it isn't writing back into the load record where the coordinator already lives, then Dallas is right and I'm not going to argue with them. Here's what I can show you rather than promise: since we split the support queue by segment on August 12, your median first response is 3.4 hours across 14 tickets, and I'll send you the IDs so you can check them against your own inbox. And last week, before this call, we ran your top 50 carriers by load count through ELD integration instead of the driver app. That tier moved from 71% to 79% compliance in six weeks. I didn't tell you because I didn't want it to be another promise.
Buyer
Seventy-nine is better. It's not what we bought. And [Competitor] is quoting me 92%.
Rep
Ask them one question when you next speak: is that 92% across all carriers, or across ELD-integrated fleets? Because on your carrier mix — and you know it better than I do — the number that matters is compliance on owner-operators, and nobody in this market is at 92% there. What percentage of your weekly volume runs on your top 100 carriers?
Buyer
Most of it. Seventy-something percent.
Rep
Then that's the first line of the plan, and I want to build it with you now rather than send you a deck. My team works your top 100 by load count, ELD first, app second — named owner on my side, start the week of the 14th, done means 85% compliance on that tier by day 60, measured in your dashboard, not mine. Second line is Dallas and the East branches: two live sessions per branch, run against loads actually on their board, and the target is check calls per load under 4.5 on those desks. Fresno's at 3.2 today and covering 31 loads per coordinator per day against 22 in Dallas — I'd like your Branch Manager to hear that number from your own reefer lead, not from me.
Buyer
And if it goes the way this year went? I'm not signing twelve months on the strength of a plan you'll reschedule twice.
Rep
Then put a break clause at month six tied to those two numbers — the 85% on the top 100 and the adoption count in Dallas. If we miss, you walk, no penalty. And I'll credit April through June where we missed SLA, because those months you paid for something you didn't get. What I'm not going to do is drop the rate as an apology — that would tell you this whole year was a pricing argument, and it wasn't.
Buyer
Alright. I still want to see what a right-sized number looks like. We're billed for 140 seats and I've got about 60 people in it.
Rep
Sixty-one weekly active. So I'd rather take you to 90 seats and grow back as the branches come on than discount 140 you're not using. Before we get to paper: walk me through what happens between now and the 31st — do you sign, or does this go to your COO, and does procurement already have their quote? And I want your Fresno lead and our VP of Customer Success in the plan review. She should hear about June from you, not from me. Can we do Thursday the 9th at 8am your time?
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. You promised it too, and I'm at 61%."” | Don't defend the number, own it and get specific about which number you'll move. "You're right, and I'm not going to re-pitch you. So let's stop talking about visibility and talk about two numbers: tracking compliance on your top 100 carriers, and check calls per load on the desks that never got trained. Compliance on that tier is 79% today, up from 71% in six weeks. Check calls in Fresno are 3.2; Dallas is 6.4. Those are the only two numbers in the plan, and the break clause is tied to them. If they don't move by day 60, you leave." |
| “"My carriers won't take it. The small guys decline the ping or turn it off after pickup, and I'm not losing capacity over a tracking mandate."” | Never let it become capacity versus visibility — you lose that argument every time, and at renewal it's fatal. "I'd never ask you to turn away a truck over a ping. That's why the plan starts with ELD integration on the top 100 rather than the app — no driver behaviour change at all. Roughly 70% of your volume runs on those carriers. For the 1-to-5 truck operations on Laredo and Fresno, I'll quote you a realistic number for that mix, not 98%, and we'll agree what happens on the rest — which is a structured check-call cadence, not silence. Where I failed you this year was pushing the app at everybody instead of segmenting the carrier base." |
| “"We fought for eighteen months to get people onto the TMS. Dallas tells new hires not to bother with your tool because it's a second screen."” | Agree out loud, then get technical fast. "If it's a second screen, Dallas is right and I'm not going to argue with your Branch Manager. So let's be precise: which McLeod version, API or flat file, and does the arrival timestamp land in the load record where the coordinator already works or in our portal? If it's landing in our portal, that's the first thing I fix in the 90 days, and it goes in the plan with a date and a name against it — mine." |
| “"[Competitor] came in 28% under, and they'll onboard my carriers themselves."” | Never disparage, and never match on price in this call. "Good — I'd have been surprised if they hadn't. What did you like about it? … Two questions I'd want answered before you sign: is their 92% compliance across all carriers or across ELD-integrated fleets, and who re-onboards your 340 active carriers, on what timeline? Because the real cost isn't the license delta, it's the quarter where you're back at 40% compliance during the migration, plus retraining the one desk that did adopt, plus twelve months of timestamped arrivals you currently use to fight detention. And the honest version: there's nothing stopping you inheriting their version of the Q2 we just gave you, with none of the history." |
| “"Just tell me what it costs per load. Net revenue per load is down and I'm being measured on headcount per 100 loads."” | Price it in their operating metric, not in dollars saved. "Then let's price it in heads, not dollars. Fresno covers 31 loads per coordinator per day at 3.2 check calls a load. Dallas covers 22 at 6.4. That gap is what the plan is trying to close across three branches. Separately — what was the last account you lost on service? A shipper doing 40 loads a week at $200 margin is a $400K conversation, and that's the one your COO will remember, not the per-load fee." |
| “"Honestly, my shippers never noticed the difference. They're fine with the emails we send."” | Move it from service upgrade to bid eligibility. "They're not asking you — they're asking whoever's bidding against you. What did the last three RFPs you responded to require for EDI 214 status messaging and automated location? Most of the enterprise shippers now score it in the bid, and your VP of Sales on the shipper side will feel that before your coordinators do. If the answer is 'none of them,' then I'll build the plan around check calls per load and coordinator throughput instead, and we'll drop the shipper-facing piece from what you're paying for." |
| “"We're heads-down on peak. Send me the paperwork and I'll look at it in January."” | Don't fight the calendar, use it — but protect the six weeks. "Peak is exactly when I want you to see this, because January numbers will flatter both of us. What I'd rather do is twenty minutes with you, your Fresno lead and our VP of Customer Success on the 9th — and I'll come with your live check-call and compliance numbers from peak week, not a deck. If the plan doesn't hold up against your worst week, you shouldn't sign it." |
Questions reps ask about this call
- What should the first sixty seconds of a freight / 3PL renewal call sound like when the account is at risk?
You go first, with specifics. Name the ticket numbers and dates, the SLA misses, the CSM turnover, the adoption gap by branch, and the gap between the tracking compliance rate you sold and the one they actually have. Then hand them the floor and stop talking. Opening with "how has everything been going?" when you can see a nine-day first-response time on your screen reads as either unprepared or evasive, and the buyer will spend the rest of the call working out which.
- How much of the call should be spent listening before I bring up renewal terms?
Forty to fifty percent. On a thirty-minute call, if you're not fifteen minutes in before you mention anything commercial, you rushed it. In freight specifically, ask what the failure cost them in the shipper QBR — the on-time delivery percentage they had to defend with coordinator notes instead of GPS pings is usually the wound, not the tickets themselves. Ask who they had to explain it to. The Director of Brokerage Operations who championed you has usually taken heat from a COO or VP of Operations, and that's what actually has to be repaired.
- Should I discount to save a freight brokerage renewal when a competitor is 25–30% cheaper?
Not as an apology, and not before you've rebuilt value. A price cut reframes the entire bad year as a pricing dispute and permanently resets your floor. Two honest instruments work better: service credits for the specific months where you missed SLA, which are finite and specific, and right-sizing seats to actual weekly active users — going from 140 billed seats to 90 real ones kills the shelfware objection for good and shows you'd rather be accurate than big. If you do concede on rate, trade it for a multi-year, a reference call with another Director of Carrier Sales, or a signature date.
- What goes in a 90-day success plan for a 3PL that never got past first-team adoption?
Four fields on every line: what, who by name on both sides, by when, and what "done" looks like in their metrics. For a brokerage that means carrier onboarding by tier (top 100 by load count, ELD integration before driver app) with a target tracking compliance rate, branch-by-branch training run against live loads on the coordinators' own boards with a target for check calls per load, a named escalation contact with a written SLA, and dated 30/60/90 reviews. Include the thing you can't deliver — say plainly that the roadmap item isn't shipping before Q3. And make sure the customer owns lines too: if their VP of Operations doesn't mandate it the way they mandated the TMS, adoption stalls again.
- The buyer says their carriers won't accept tracking, so the product was never going to work. How do I answer that at renewal?
Never frame it as capacity versus visibility — no brokerage will turn away a truck on a hard lane to satisfy a tracking mandate. Segment instead: ELD integration for the fleets that already have it, driver app for the ones that'll take it, and an agreed check-call cadence for the rest. Ask what percentage of their weekly volume runs on their top 50 or top 100 carriers; it's usually most of it, and those are the ones you onboard first. Quote a realistic compliance figure for their carrier mix rather than a headline number, and put it in the plan as a measurable target with a break clause attached.
- How do I avoid the renewal dying in procurement in the last two weeks?
Ask directly, on this call, who signs and what the path is: does it go to the COO, has procurement already received the competitor's quote, does the CIO or Director of Logistics Technology need to re-approve the integration or run a security review. Then multi-thread deliberately — get your power user (usually the desk lead whose workflow would break) and the economic buyer into the same plan review, with your own exec sponsor present so the apology happens leader-to-leader. Book that meeting before you hang up. Most stalled renewals die in procurement, not in the business.