The psychology of waiting: why a transparent 30-minute wait beats a surprise 20-minute one

Maister's first law of waiting

In 1985, David Maister — a Harvard Business School professor — published a paper called The Psychology of Waiting Lines. It is one of those rare academic pieces that practitioners actually read because the conclusions are immediate and useful. His first law is one sentence:

"Satisfaction equals perception minus expectation."

If a customer expects a 20-minute wait and gets a 25-minute wait, they are unhappy by 5 minutes. If a customer expects a 45-minute wait and gets a 30-minute wait, they are happy by 15 minutes. The clock is the same; the experience is opposite.

The implication for service drives is direct. Most stores under-quote waits to "be nice" — "we'll have you out in 30 minutes" when honestly it's a 50-minute job — and then deliver 50. The customer who heard 30 leaves angry. If the same store had said "honestly, you're looking at 45-50 minutes today, want to wait or come back?", the customer who chose to stay would leave neutral or happy. Identical work. Different conversation. Different CSI score.

The eight principles, applied to the service drive

Maister's paper lays out eight propositions about how customers experience waiting. Here are all eight, with the service-drive translation.

1. Occupied time feels shorter than unoccupied time

Customer staring at a phone with no signal: 20 minutes feels like 40. Customer watching a live camera feed of their own car on a lift, plus a magazine and decent coffee: 20 minutes feels like 12. The waiting room is not overhead. It is part of the service.

2. Pre-process waits feel longer than in-process waits

The bench wait before an advisor takes the keys feels far longer than the wait after the car is on the lift. Move the customer into the "in-process" mental category as fast as possible: greet them, take the keys, send them to the lounge. Even if no work has actually started, the perception is "they have my car now."

3. Anxiety makes waits feel longer

"Did anyone see me?" "Did they forget me?" "Is my car going to be done in time for school pickup?" Anxiety inflates perceived wait by 30-50%. The fix is acknowledgement: a name on a screen, an SMS confirmation, a wait estimate. Anything that says "you exist; we know you're here; here's the plan."

4. Uncertain waits feel longer than known waits

This is the headline of this article. A wait of "we'll get to you when we can" is excruciating. A wait of "you're third in line, about 35 minutes" is fine, even if 35 minutes is longer than the customer wanted.

5. Unexplained waits feel longer than explained waits

"You're waiting because the previous customer's RO took longer than expected — we're adding a tech now" is a different wait than "uh, just hang tight." Explanations restore agency.

6. Unfair waits feel longer than equitable waits

If a customer who arrived after them is called first, the original customer's wait perception jumps. This is why FIFO queues — and visible queues — matter. If you're going to break FIFO (e.g., for an appointment vs walk-in), explain it: "Mr. Reyes is here for his 10:30 appointment, you're our next walk-in."

7. The more valuable the service, the longer the wait people will tolerate

Customers will wait an hour for a transmission diagnostic without complaint. They will lose their minds at a 20-minute wait for an oil change. Match the experience to the perceived value. Express bays should have aggressive wait targets. Main shop can be more relaxed.

8. Solo waits feel longer than group waits

The waiting room with two people in it feels worse than the waiting room with twelve. Sounds counter-intuitive, but multiple people waiting normalizes the wait. This is why empty waiting rooms feel like ghost towns and why "we're a little backed up today, it's happening to everyone" is a more reassuring message than you'd think.

Why a 30-minute estimate beats a 20-minute surprise

This is worth a section by itself because it's the most common service-drive mistake. The advisor hedges down to be "nice," and the result is consistently worse CSI than if they had hedged up.

Scenario	Quoted	Actual	Customer perceives	CSI delta
Hedge down (typical)	20 min	35 min	"They lied to me"	−0.4
Honest	35 min	35 min	"They were straight with me"	0
Hedge up (best practice)	45 min	35 min	"Faster than promised"	+0.3
Way overshoot	90 min	35 min	"They have no idea what they're doing"	−0.2

The sweet spot is hedging up by ~25-30%, not 200%. You want the customer to feel that you respected their time enough to give them an honest number, with a bit of cushion in case something goes sideways. The customer who consistently gets out faster than quoted becomes a regular.

The hard part is producing the estimate. If your advisor is guessing based on vibes, the variance is huge. If your queue tool is computing it from current bay utilization, average service times for the customer's specific job, and the position in line — the estimate becomes credible enough to lean on.

The "almost ready" notification effect

Here's a small thing that has an outsized effect. Send the customer an SMS when the work is roughly 5-10 minutes from done. Not "your car is ready" — that one is mandatory — but a heads-up:

Three things happen. First, the customer mentally exits "waiting" mode and enters "almost done" mode, which is psychologically very different. Second, if they had stepped out to a Starbucks, they have time to get back without your advisor having to call them three times. Third, when the actual "your car is ready" SMS lands a few minutes later, they're already prepared to leave — saving 4-7 minutes in pickup overhead.

It is one extra SMS, fully automatable from any modern queue platform, and it's worth roughly 0.1-0.2 CSI points all by itself.

Practical tactics on the service drive

Greet within 90 seconds, every time

Maister's third principle (anxiety) collapses if the customer is acknowledged quickly. Even "hi, I see you, I'll be right with you" within 90 seconds resets the anxiety clock. If your advisors can't hit this consistently because they're at the desk doing data entry, that's a process problem you can solve with a kiosk or a podium tablet.

Visible queue position

"You are #4 in line. Estimated wait: 38 minutes." That's it. Print it on the kiosk receipt, show it on the lounge TV, send it via SMS. Visibility is the antidote to uncertainty (principle 4) and unfairness (principle 6).

Live status updates at meaningful moments

The minimum cadence:

• Check-in confirmed (queue position + estimate)
• Tech started on your vehicle
• Concern: anything that adds time (estimate update + reason)
• Almost ready (5-10 min out)
• Ready

Five SMS messages over an hour. Customers do not find this excessive — they find it reassuring, as long as each message has actual content.

Show the work

If you can stream a camera feed of the bay, do it. Not because customers actually watch the whole time — they don't — but because the option to glance at it converts anxiety into satisfaction. Maister's first principle (occupied time) and third principle (anxiety) both move.

Make the lounge actually good

Decent coffee. Wi-Fi that works. Outlets within reach of seats. A clean restroom. A kid-friendly corner if your customer base needs one. None of this requires more than $2,000 of one-time investment, and it has a measurable CSI impact.

Apologize concretely when you slip

"Sorry for the wait" is empty. "Sorry — we hit a snag with a part on the previous job and it pushed everyone back about 12 minutes. Coffee on us, and your wait is now down to 14 minutes" is recovery. The first one annoys the customer; the second one earns trust.

What NOT to say

Most of these are habits, not policies. They get into advisor vocabulary because they sound polite. They scan as polite to the advisor. They scan as evasive to the customer. The fix is awareness plus a one-page service drive vocabulary sheet that managers actually enforce.

SMS templates and A/B test ideas

Here are templates that work, with notes on what to test. Keep all of them under 160 characters where possible — long SMS can get split or rejected.

Check-in confirmation

Test: Including the estimated time vs not. Including position vs not. We've seen position-only outperform time-only because time creates a contract; position creates a feeling of progress.

Work started

Test: Naming the tech vs not. Naming the tech consistently lifts CSI 0.05-0.15 points because it creates accountability and humanity.

Concern / scope change

Test: "Either is fine" framing vs straight-line ask. The non-pressured version converts at roughly the same rate and produces dramatically higher CSI on the upsell question.

Almost ready

Test: Sending this vs skipping it. Stores that send "almost ready" texts see pickup time drop 4-7 minutes and "kept me informed" CSI questions move up.

Ready

Test: "Thanks for choosing us" vs nothing. Polite closers are weirdly polarizing — some customers love them, some find them sycophantic. A/B by demographic if you can.

Post-visit (sent 2 hours later)

Test: Time delay (2hr vs 24hr vs 48hr). 2-hour windows capture problems while the experience is fresh; 24-hour windows give the customer time to drive the car. We've seen 2-hour outperform on issue capture, 24-hour outperform on positive feedback. You can do both.

The summary in one paragraph

Customers will accept long waits if they understand the wait, can see their place in it, get acknowledged for their time, and feel respected by honest estimates. They will not accept short waits delivered with vagueness, broken promises, and silence. The differentiator between a 4.4 CSI store and a 4.7 CSI store is rarely the wrench-time. It is the words and signals that surround the wrench-time. Most of those words and signals can be automated, and the few that can't can be trained.

Related reading: 5 metrics every service manager should review every Monday morning · What 30 days of paper sign-in data really costs your service department