Why “We’ll Call You” Costs Your Service Department Money

Monday morning, 8:10. The drive is already full. One advisor is juggling a line of write-ups, a waiting customer wants to know how much longer, a technician is asking for authorization on added work, and the phone is ringing with the same question service hears all day long: “Just checking on my car.”

The advisor says what most good people say when they are trying to keep things moving: “We’ll call you.” It sounds harmless. Helpful, even. The customer hears a promise. The advisor means, “As soon as I know something.” The problem is nobody decides what “something” means, who owns the next contact, or when that call is actually supposed to happen.

That one sentence is expensive. It creates inbound calls, stalls approvals, clogs the drive, irritates customers, and leaves everyone feeling busy without being productive. In a small service department, where one missed call can throw off the whole day, “we’ll call you” is not customer service. It is unfinished work.

Vague promises create repeat traffic

When a customer drops off a vehicle, they are handing you two things: the car and their uncertainty. They do not know whether the concern is minor or major, cheap or painful, same-day or all-week. If your only communication plan is “we’ll call you,” the customer is left to manage that uncertainty on their own.

So they do what anybody would do. They call back.

Now your team handles the same repair order two, three, sometimes four times before the work is approved or completed. That extra traffic does not produce another labor sale. It just burns advisor time, ties up the phone, interrupts dispatch, and distracts technicians waiting on decisions.

Most service departments think the problem is phone volume. Usually it is promise volume. If the promise is loose, the follow-up gets messy.

The cost is bigger than the phone call

The obvious cost is labor time at the counter. But the bigger cost shows up in the cracks.

A technician finishes diagnosis and waits because the advisor is tied up with customers asking for updates. An estimate sits too long before it is presented. Parts are ordered later than they should be. A loaner or shuttle customer gets frustrated because nobody told them the timeline changed. At 4:45, the department is still chasing customers it could have updated at 10:30.

Then there is the trust problem. Customers are surprisingly patient when they know what is happening. They get aggravated when they feel forgotten. “Nobody called me” lands harder than most managers want to admit, because to the customer it means, “My time did not matter enough for a simple update.”

In a small department, you do not have spare people to absorb that kind of rework. Every avoidable touch costs you capacity.

Replace “we’ll call you” with a communication commitment

The fix is not to make more promises. It is to make clearer ones.

Instead of saying, “We’ll call you,” your advisor should give the customer a specific next contact point. That can be tied to time or event:

• “I’ll update you by 10:30, even if we’re still in diagnosis.”
• “Once my technician inspects it, I’ll call with findings before any added work is done.”
• “If parts availability changes, you’ll hear from me by noon.”
• “If you don’t hear from me by 3:00, call me directly at this number.”

That does three important things. It sets expectation, assigns ownership, and creates a clock. The customer now knows when to expect contact. The advisor knows what was promised. Management has something concrete to coach.

Notice one more thing: a good update does not require a final answer. “We are still waiting on inspection, and I’ll call again at 11:30” is a perfectly good update. Silence is what hurts you.

Process → Procedure → Reference for service updates

This is where a small department needs discipline, not complexity.

Process: Decide how customer communication should work from write-up to delivery.

Your process should answer a few plain questions:

• When is the first update promised?
• Who owns the contact—the advisor, cashier, dispatcher, or BDC?
• What events require immediate customer contact?
• How are waiting, drop-off, warranty, and special-order jobs handled differently?
• What happens if the advisor is tied up or absent?

The goal is simple: every open repair order has a known next communication step.

Procedure: Write down the steps your team follows every time.

A basic procedure might look like this:

1. At write-up, advisor records the customer’s preferred contact method.
2. Advisor gives a specific update time or event-based promise.
3. That promise is noted on the repair order or daily control log.
4. After dispatch or initial inspection, advisor reviews open ROs by promised contact time.
5. Advisor contacts customer by the promised time, even if the update is only status.
6. Added work is presented with estimate, priority, and expected completion impact.
7. If advisor cannot make the contact, backup coverage is assigned.
8. Final communication is documented before delivery.

That is not fancy. It is just repeatable.

Reference: Keep the records and forms that prove the process happened.

For this topic, your references may include:

• Repair order notes with promised update time
• Advisor daily follow-up log
• Text or email communication record
• Added-work authorization notes
• Missed-contact exception log for coaching

If it is not written down somewhere your team can see and act on, it is relying on memory. Memory is not a system.

Start with one promise and one log

Do not overbuild this. You do not need new software, a consultant, or a three-inch policy manual to clean this up. Start with one standard: no advisor says “we’ll call you” without giving a time or trigger for the next update.

Then give them one place to record that promise. It can be in the DMS notes, on the hard copy repair order, or on a simple open-RO follow-up sheet. What matters is that the promise is visible and reviewable.

Have your service manager spot-check a few repair orders a day. Ask two questions: What was promised? Did we do it? That alone will tell you a lot about where the department is leaking time.

Small service departments do not usually lose money because people do not care. They lose money because good people are working without a clear communication process. “We’ll call you” sounds courteous, but in practice it is often a delay, an interruption, and a comeback waiting to happen.

Tighten the promise. Write down the procedure. Keep the reference. That is how you turn customer updates from a constant interruption into part of the work itself.

Process → Procedure → Reference — Centennial Business Systems | Centennial Dealership Operating System