Parts Manager Hot Shot Coordination Script (Word-for-Word Template)

The most effective hot shot coordination script follows a three-step structure: confirm the part number and vehicle application, state the requested delivery time and cost responsibility, and lock in a pickup time with the receiving store's acknowledgment. Write it down, keep it consistent across your team, and you'll reduce miscommunications that waste time and money.

Why a standardized parts coordination script matters

Without a script, your parts team is improvising every call. One tech gives a verbal ETA, another doesn't confirm the receiving store has a bay ready, a third forgets to note who's paying the hot shot fee. Three days later you've got a $200 transmission cooler sitting in the wrong location and nobody remembers who authorized the cost split.

A written script doesn't mean robotic. It means your parts manager, your backup, and your BDC can all handle a hot shot request the same way. It's the difference between coordination and chaos.

Stores that get this right tend to see fewer wrong-parts shipments, clearer accountability on cost allocation, and faster resolution when a part arrives damaged or late. Your service advisors also stop getting surprised calls about parts they thought were already in stock.

The three-call structure for hot shot coordination

Break every hot shot into three distinct conversations: the request call, the confirmation call, and the handoff call.

Call 1: The Initial Request

This is when another store or your own service drive calls in needing a part fast. Your script for this moment should sound like:

"Hey [Store/Tech Name], I can help with that. Let me grab the details so we get this right. What's the part number and year-make-model of the vehicle?"

Then:

Repeat back the part number and vehicle application verbatim.
Ask: "When does the vehicle need to be ready?" (Not "when do you need it" — you want the service appointment time, not a vague deadline.)
Confirm: "So that's a [part name] for a [year make model], needed by [time] on [date]. Correct?"
Ask: "Is this a same-store job or do we need to hot shot it from another location?"
If inter-store: "Which store do you need it from, or should I check availability?"

Write down everything. Use your DMS or a parts coordination log — actually, scratch that, use a dedicated parts tracking tool if you have one. The point is: nothing stays in someone's head.

Call 2: The Confirmation Call (to the source store)

Once you know what you need and where it's going, call the parts department at the store that has inventory. Your script:

"Hi [Parts Manager Name], I need to coordinate a hot shot with you. We've got a [year make model] in the bay at [Store Name] that needs a [part name], part number [number], and they need it by [time] on [date]. Do you have that in stock, and can your driver make that window?"

Listen for three things:

Stock confirmation: "Yes, we have two in stock" is the answer you want. If they don't have it, pivot immediately , call the next location or check your distributor.
Delivery window: "Our driver can be there by 2 p.m." locks in the ETA. If they say "probably by 3," push back: "So 2:30 latest? I need to tell the service advisor a hard time."
Cost ownership: "We'll cover the hot shot" or "You cover it" , say it out loud. Don't assume.

Your closing line: "Perfect. So to confirm , you're sending [part name], part number [number], to [Store Name], pickup time [time], they need it by [time], and [Store A / Store B] covers the hot shot cost. I'm texting you the receiving store's address and the tech's phone number now."

Call 3: The Handoff Call (to the receiving store)

Once the source store confirms, call the receiving location back. This is quick.

"Hey [Service Advisor / Tech Name], the part's on the way. You're getting a [part name], part number [number], from [Store Name]. Their driver will be there around [time]. Your driver or someone needs to be ready for the handoff. I'm sending you the hot shot driver's cell number , give them a call if you're running late."

Then text or email a summary. One line is enough: "2019 Chevy Silverado timing belt , part #4892L , from Store 3, arriving 1:45 p.m., Bay 4 ready."

What to include in your written parts coordination script

Your script should live in your parts manager's desk or pinned in your team chat. It doesn't need to be fancy. A simple Google Doc or a note card works. Here's what must be in it:

Opening line: "Hey [Name], I can help with that. Let me grab the details so we get this right."
Key questions in order: Part number? Year-make-model? When does the vehicle need to be ready? Which store has it?
Confirmation statement: A "read-back" that repeats all details before any action.
Cost question: "Who's covering the hot shot fee?" (Make this explicit.)
Driver/ETA language: "What time can your driver be there?" not "Can you get it there soon?"
Contact exchange: "I'm sending you the driver's number now."
Handoff confirmation: A closing that locks in pickup/delivery times.

Here's an example you can adapt:

"Got it. So to confirm , you need a [part] for a [year/make/model], part number [#], at [Store] by [time] on [date]. [Store A] will send it from their inventory, and [Store B] covers the hot shot cost. Our driver leaves by [time] and will arrive around [arrival time]. I'm texting [receiving store] the driver's cell now so they can meet him in Bay [#]. Everyone good?"

Common mistakes that break your script (and how to avoid them)

Even with a script written down, your team can still mess up. Watch for these:

Mistake 1: Not repeating back the part number

You hear "timing belt for a Silverado" and assume you know what that means. But there are five different timing belt options across Silverado model years and engine sizes. Always repeat back the part number and the specific year-make-model before you hang up. A 15-second verification saves you a 45-minute wrong-part situation.

Mistake 2: Vague delivery windows

If you tell a service advisor "the part should be here this afternoon," you've set up failure. That advisor doesn't book a customer. The part arrives at 4:47 p.m. The service bay closes at 5. You just lost a day of throughput.

Instead: "The driver will be there at 2:15 p.m. If you're running behind, call him at [number]." Specific times reduce surprises.

Mistake 3: Forgetting to confirm who pays

Hot shot costs add up. If Store A thinks Store B is paying and Store B thinks Store A is paying, you've got a $150 dispute on your hands. Say it out loud: "Store 3 is covering the hot shot, correct?" Make your parts manager write it in the log with initials.

Mistake 4: No written record

Three weeks later, a service director asks, "Why did we spend $800 on hot shots last month?" If your parts manager can't pull up a log showing which parts went where and who authorized it, you look disorganized. Keep a simple log in your DMS, a spreadsheet, or a team chat thread. Just keep it.

Adapting your script for different scenarios

Not every hot shot is the same. Your script needs flexibility for common variations.

Scenario A: Emergency hot shot from a distributor

Sometimes no dealership has the part. You're calling a supplier. Your script shifts slightly:

"Hi [Supplier], I need an emergency delivery today. I'm looking for [part name], part number [#], for a [year make model]. Can you confirm you have it in stock and what's your delivery window to [address]? What's the cost?"

Then confirm cost with your service director before you commit. An emergency transmission part might run $400 plus $80 for a hot shot. That's a conversation before you authorize it.

Scenario B: Multi-part coordination (rare, but it happens)

A customer has a big job , say, a $3,400 timing belt job on a 2017 Pilot at 105,000 miles. You need a belt, pulleys, a water pump, and a tensioner. Some parts are in stock, one is at another store.

Don't make three separate hot shot calls. Consolidate: "I've got one hot shot coming in , it's actually four parts for a 2017 Pilot timing belt service. I'm sending you the list. Can you confirm you have all of these and what time your driver can get here?" Fewer trips, same coordination discipline.

Scenario C: Same-store parts already in inventory

This is your easiest call, but use the same script anyway. It trains consistency. "I'm pulling a [part] from Bay 3 inventory for the 2016 Accord in Bay 7. I'm confirming that part number [#] is correct, and you'll have it in 10 minutes." Write it down anyway. It's a one-line log entry, and it keeps your inventory accurate.

Training your team on the script

Writing the script is half the battle. Getting your parts team to actually use it is the other half.

Spend 15 minutes in your next team meeting walking through a hypothetical hot shot call. Have your backup parts manager role-play the request, and have your primary parts manager use the script. Do it three times. Then switch roles. People remember what they practice.

Post the script in your parts department and in your team chat. When a new parts tech or BDC rep joins, walk them through it before they take their first hot shot call. Consistency compounds.

This is the kind of workflow Dealer1 Solutions was built to handle , parts coordination, approvals, and handoff tracking all in one place so nothing falls through gaps.

Measuring whether your script is working

After two weeks of using a standardized script, pull your metrics. You should see:

Fewer wrong-part shipments: Because you're repeating back part numbers, not guessing.
Fewer missed ETAs: Because you're locking in specific times, not vague "sometime today" estimates.
Clearer cost allocation: Because you're asking who pays out loud and logging it.
Faster service completion: Because parts are arriving when promised, not 45 minutes late.

If you're still seeing surprises after two weeks, audit your team. Is someone skipping the confirmation call? Are they forgetting to log the cost? Coaching at that point is specific: "I need you to repeat back the part number before you hang up. That one change will fix the mismatches we've been seeing."

Red flags that your script needs refinement

Watch for patterns that suggest your script is incomplete.

Repeated questions about "when will it actually be here?": Your ETA language isn't specific enough. Tighten it.
Cost disputes between stores: Your script isn't asking clearly about who pays. Make that question mandatory and logged.
Parts arriving at the wrong bay or wrong store: You're not confirming the receiving location clearly. Add a read-back: "So Bay 3 at the downtown location, correct?"
Drivers showing up with the wrong part: Your source store isn't verifying what they're picking. Consider requiring a photo or a second set of eyes before the part leaves.

Frequently asked questions

What if the source store doesn't have the part in stock after I confirm with them?

Call them back immediately and tell the receiving store you need to pivot. Don't let them wait. Have a backup plan , either a second dealership location or a distributor number to call. Your script should include a fallback: "If we can't get it from [Store A], we'll source it from [Distributor] and still hit the window. Let me confirm that's okay cost-wise."

Should the parts manager make all hot shot calls, or can the BDC handle them?

Your parts manager should own the inter-dealership coordination and the cost authorization. Your BDC can take the initial request and log it, but a parts person should make the confirmation calls to source stores. That way, parts knowledge stays in the conversation, and cost decisions are made by someone with P&L accountability.

How do you handle hot shots when the driver is delayed or breaks down?

Your script should include a protocol: the driver calls the receiving store directly the moment they know they're behind. Not 20 minutes before they arrive , the moment they know. Your script line: "Our driver will call you if anything changes. If you don't hear from him by [time], call me and I'll find out where he is."

Can you use this script for parts transfers that aren't emergencies?

Absolutely. A planned parts transfer to rebalance inventory uses the same discipline. You're still confirming part numbers, confirming times, and logging costs. The only difference is you've got more time to coordinate, so there's less urgency in the conversation. Same script, lower pressure.

What if a service advisor keeps asking for hot shots instead of planning ahead?

That's a separate conversation with that advisor's manager. Your parts script doesn't solve a planning problem. But your script does make it visible , you'll see in your log that one advisor is requesting emergency parts three times a week. That's data for a coaching conversation about scheduling and parts ordering discipline.

Should you charge internal hot shots differently than external ones?

That's a dealer decision, but your script should make the cost transparent either way. If Store A sends a part to Store B at no charge, log it. If there's a cost, log it and get approval before the driver leaves. Your script is neutral on policy , it just enforces clarity.

---