Communicating ETA Changes Without Annoying the Customer

Why this matters

A schedule slips almost every day. What actually damages the relationship is rarely the slip itself, it is finding out about it too late, too vaguely, or not at all. A customer who planned their morning around an eight-to-ten window and gets a call at 9:55 saying "running behind" has already burned an hour they cannot get back and now has no idea if it is fifteen minutes or three hours. Handled well, an ETA change barely registers. Handled badly, it becomes the entire review. The difference is timing, specificity, and tone, and all three are dispatcher skills, not luck.

The three things every ETA update needs

A useful update always has these three pieces, in this order:

• How late, in a real number. "Running behind" tells the customer nothing they can plan around. "About forty-five minutes behind the window" lets them make a decision.
• Why, briefly, if it reflects well or is neutral. "The prior job needed extra parts" is fine to share. You do not owe a customer a detailed excuse, but a one-line reason reads as honest rather than evasive.
• What happens next. A new expected time, or a promise to call again by a specific point if it is still uncertain. Never leave an update as just bad news with no resolution attached.

Call earlier than feels necessary

The instinct is to wait until you are certain of the new time before calling, because nobody wants to call twice. Resist it. The moment you have a reasonable read that the window will be missed, that is the moment to call, even if the estimate might shift again. A customer told at the first sign of trouble has time to adjust their day. The same customer told at the last possible minute has already lost that flexibility and experiences the same delay as a much bigger failure.

• Rule of thumb: if you would bet more than even odds the appointment slips by more than fifteen minutes, call now, not at the original window's edge.
• If the estimate changes again after that first call, a short follow-up ("just confirming, still on track for the new time") costs nothing and reinforces that you are tracking it, not that you are unreliable.

Match the channel to the customer and the news

Not every update needs a phone call, but every update needs to reach the customer in a way they will actually see in time.

• A text works well for small slips (under thirty minutes) and for customers who have shown they respond to texts quickly.
• A phone call is worth the extra time for larger slips, for customers who took off work, or for any update where tone matters, since a text cannot convey the same reassurance a calm voice can.
• Never rely on a single channel for anything urgent. If a call goes to voicemail and the slip is significant, follow with a text so the message lands even if the call was missed.

Give a range, not a false-precise number

"We'll be there at 2:47" sounds precise and lands badly the moment it is 2:52 and the customer starts watching the clock. A believable range holds up better than a fake-exact time.

• Give a window, not a point in time, especially for anything more than fifteen minutes out. "Between two and two-thirty" survives normal variation; "at 2:15 exactly" does not.
• Round toward the honest side, not the optimistic side. A dispatcher who consistently under-promises the delay and over-delivers the arrival earns trust. One who consistently promises a tighter time than reality can deliver trains the customer to expect to be let down.

What tone does that a number alone cannot

The words around the number matter as much as the number itself.

• Own it plainly. "We're running behind and I wanted to give you an updated time" reads better than a string of qualifiers and apologies that sound like the dispatcher is nervous about the news.
• Do not oversell the apology. One clear acknowledgment is enough. Repeating "I'm so sorry" five times in a short call reads as anxious rather than professional, and it does not actually shorten anyone's wait.
• Thank them for the flexibility, briefly, at the end. It costs nothing and closes the call on a note of respect rather than just delivering bad news and hanging up.

When the customer is upset anyway

Some customers will be frustrated no matter how well the update is delivered, especially if this is a repeat pattern with this account or the delay affects something time-sensitive on their end.

• Let them vent for a few seconds without interrupting. Talking over a frustrated customer to defend the delay usually makes it worse.
• Restate the concrete plan once they have said their piece: the new time, and what you will do if it slips again.
• If the delay is now large enough to matter, offer something concrete where appropriate, moving them earlier in tomorrow's queue, a priority slot next time, or simply the dispatcher's direct line for the rest of the day. A gesture that shows the inconvenience registered does more than another apology.

The pattern to build into daily habit

The best dispatchers treat ETA communication as a running task, not a one-time event triggered by a late job. Check the board's real-time status against the promised windows every hour or two, not just when a customer calls asking where their tech is. Catching a slip before the customer notices it is the entire goal; everything above is what to do once that window has already passed.

References

• See related: Route Density vs Strict Appointment Times: Decision Tree
• See related: The Scheduling Buffer: Why You Need Slack
• Trade-standard practice for field-service customer communication and dispatch