A Word-for-Word Script Service Advisors Can Use for Keeping a Tight Promise Time

A tight promise time starts with this three-step script: (1) repeat the time back to the customer with the date and day, (2) explain one specific reason why you chose that time, and (3) ask for their cell number and confirm you'll text if anything changes. Use this exact language: "So we're looking at Tuesday at 2 p.m., and that's because we've got your part arriving Monday night, so we can knock this out first thing. Can I grab your cell so I can reach you if we need to move you?" This moves you from a vague promise to a locked commitment with a fallback plan.

Why Service Advisors Lose Control of Promise Times

Promise time creep is a dealership disease. The advisor says "Tuesday," the technician finds a hidden rust seize on the bolt, parts don't show up on time, and suddenly you're calling the customer at 5 p.m. on Tuesday asking for a miracle. The customer's already rescheduled their day. CSI tanks. Trust erodes.

Here's the pattern we see: advisors quote a time they hope to hit, not a time they've actually built. They don't involve the parts team before committing. They don't text the customer when a dependency shifts. They assume the customer will just be flexible because, well, cars are complicated.

Customers don't care that cars are complicated. A customer who was told "Tuesday at 2 p.m." has already told their boss they can pick up their car at 2:30 p.m. They've arranged a ride. They've moved a meeting. Slipping that time by even 30 minutes registers as a broken promise, and one broken promise erodes five good experiences.

The fix isn't managing the customer's expectations better (that's code for lowering them). The fix is building a promise time that's actually achievable, then locking it in with a script that forces clarity on both sides.

The Three-Part Script Every Advisor Should Memorize

This script works because it does three jobs at once: it confirms the customer heard the time correctly, it explains why you chose that specific time (which makes it feel real, not arbitrary), and it establishes a communication backup if something goes sideways.

Step 1: Repeat the Time Back, Specific and Dated

Don't say "a couple of days." Don't say "Wednesday-ish." Say the full date and time.

Script: "So we're looking at Tuesday, the 18th, at 2 p.m."

This does two things. First, it gives the customer one last chance to correct you if they heard wrong. Second, it burns the commitment into both of your brains. There's no wiggle room in "the 18th at 2 p.m." There's plenty of wiggle room in "early next week."

Step 2: Explain the One Reason You Chose That Time

Name the dependency that makes this time real. Don't make it up. It has to be true. Here are real reasons:

Parts availability: "That's because your transmission seal kit arrives Monday night, so we can pull the pan first thing Tuesday morning."
Technician schedule: "That's because our transmission guy is booked solid Wednesday and Thursday, but he's got a hole Tuesday morning before the fleet jobs."
Diagnostic hold: "That's because we want to run a full diagnostic on the suspension first, and that takes about 90 minutes. We can get that done Monday, and then we'll have a clear parts list Tuesday."
Parts lead time: "That's because the water pump we need is on backorder, but the supplier promised delivery by Monday 5 p.m., so Tuesday afternoon gives us a buffer."

Notice: each one is specific. It ties the promise time to a real constraint or workflow step. The customer hears this and thinks, "Okay, they actually have a plan, not just a guess."

Step 3: Get Their Cell and Commit to Notification

This is the safety net. You're essentially saying: "I'm confident in this Tuesday 2 p.m. time, but if the plan changes, you're the first person to know."

Script: "Can I grab your cell so I can reach you if we need to move you? If we run ahead or if something pops up, I'll text you as soon as I know."

That text-first language matters. A phone call feels like bad news. A text feels like a heads-up from someone who respects your time. And the promise to text "as soon as I know" sets the tone that you're not going to hide bad news until 4 p.m. on Tuesday.

How to Build a Promise Time You Can Actually Keep

Before you even open your mouth to the customer, you need to know: Can we actually hit this time?

A typical $3,400 timing belt job on a 2017 Pilot at 105,000 miles with a water pump replacement takes about 4.5 hours of labor, plus 30 minutes for the inspection and pre-work. The parts are in stock at most dealers. If the customer drops the car off Monday morning, and the job runs Tuesday morning, you're looking at a 3 p.m. pickup Tuesday. That's solid. But if the serpentine belt is also shot and you didn't catch it in your initial estimate, suddenly you're at 5.5 hours, and now you're slipping to 5 p.m. That's a promise break.

Here's what top advisors do: they build in a buffer and they verify dependencies before they quote.

The checklist before you quote a time:

Is the part in stock? (Check your system, call parts if you're unsure.)
Does this job land on a day when the right technician is available? (Look at the schedule, don't assume.)
Is there a hidden risk that might expand the job? (Ask the tech if they've seen this issue before on this model.)
What's your buffer? (Add 20–30 minutes to your labor estimate as a safety margin.)
Will you text them if the job finishes early? (Yes. Early is better than late, and it builds trust.)

Once you've verified these, you can quote with confidence. Your script isn't lip service; it's a summary of actual work you've already scheduled.

What to Do When the Plan Changes

The car comes in for a brake pad replacement, and the tech discovers rusted rotors that need replacing too. The part you ordered for Wednesday just shipped from the supplier, but it's not arriving until Friday. The technician who usually does transmission work called in sick.

This happens. The script handles it.

The moment you know the promise time is shifting, text the customer. Don't wait for them to call you. Don't wait until they arrive at the dealership. Text them the moment you have new information.

Script: "Hi [Name], wanted to give you a heads-up on your 2017 Pilot. We found rusted rotors when we got under there this morning—that's actually better for you because we can replace them while we're in there, but it'll take another 30 minutes. I'm moving your pickup to Tuesday at 2:30 p.m. instead of 2 p.m. Does that work, or do you need me to squeeze you in earlier?"

Notice: you're not apologizing for the surprise; you're explaining why it's there, giving them the new time, and asking if they can accommodate it. You're treating them like a collaborator, not a problem to manage. That tone matters more than the 30 minutes.

And if they can't accommodate Tuesday at 2:30, you have a negotiation on your hands. But that conversation is happening while you still have time to adjust, not at 5 p.m. when they're already frustrated.

Building This Into Your Team's Standard

One advisor using this script is good. All advisors using this script is how you stop losing CSI points to promise-time failures.

This means your service manager needs to audit it. Pull five ROs from last month and listen to the advisor-customer calls (or read the text threads if you've got recording software). Are they doing the three-part script? Are they repeating back the date and time? Are they explaining the reason? Are they getting a cell number?

Honest opinion: most advisors will resist this at first. It feels prescriptive, like you don't trust them. But after they use it twice and they see the customer nod and say "Okay, that works," they'll get it. The script isn't limiting their judgment; it's protecting their credibility.

The other thing your team needs is a real conversation with parts about lead times. Your service advisor can't promise Tuesday at 2 p.m. if parts is telling you "yeah, we usually get that by Wednesday, but maybe Thursday." That's a workflow problem, not an advisor problem. If your dealership is built to handle it, this is the kind of workflow Dealer1 Solutions was built to support—tracking parts ETAs per-part, so advisors see a real, specific arrival time in the system and can quote against it with confidence.

The One Thing That Changes Everything

Advisors who use the three-part script consistently report that customers stop trying to negotiate the time.

When you're vague ("maybe Wednesday"), customers push back. They want options. They want to compare your Wednesday against their schedule. When you're specific and justified ("Tuesday at 2 p.m., because your part lands Monday night"), they accept it. Specificity feels like competence. Competence builds trust. Trust makes the promise stick.

That's not magic. That's just the script working the way it's supposed to.

Frequently asked questions

What if the customer asks for a time that doesn't work with your schedule?

Be honest about it. Say: "Tuesday at 9 a.m. is tough because our tech is booked with fleet maintenance that morning, but I can get you in at 1 p.m. or Wednesday at 10 a.m. Which works better for you?" You're offering real options, not excuses. The customer picks one, and you both move forward without resentment.

Should I text the customer or call them if the promise time changes?

Text first, every time. Calls feel like bad news; texts feel like a heads-up. If the change is significant (more than 2 hours), follow the text with a call so they know you're serious about staying in sync. But the text gets to them immediately, and that's what matters.

What if I'm not sure about a part's arrival time?

Don't guess. Call your parts person or check the system. If the arrival is uncertain, tell the customer: "Your part is in transit, but I'm seeing Friday afternoon as the latest it should land. I'll confirm Thursday morning and text you with an exact pickup time Friday." That's better than promising Tuesday and failing.

Does this script work for warranty work and recalls?

Yes, with one change. Warranty and recall work is often manufacturer-constrained, not advisor-constrained. Your script becomes: "The recall takes about 90 minutes, and we've got you scheduled for Tuesday at 10 a.m. That's because we're waiting for the software update from the manufacturer to arrive Monday,once it does, you're first on the list Tuesday morning." The specificity is the same; the constraint is just different.

What if the technician finishes early?

Call or text the customer immediately. Don't hold the car to hit your promised time. Early is a gift, and customers remember gifts. Say: "Good news,we finished about an hour ahead of schedule. You can pick up anytime after 12 p.m. today instead of waiting until 2. Works out better?" Most customers will rearrange to come early.

How do I handle a customer who doesn't believe the promise time is realistic?

Lean into your reason. If they say, "Really? Tuesday?", respond with: "I know it feels fast, but here's why: your part is already on the truck, we've got a two-hour block open Tuesday morning, and this job is pretty straightforward for us. If anything changes, you're the first call. Does Tuesday work for you?" You're not overselling; you're restating the facts that justify the promise.