Here is a schedule that looks fine on paper. Four appointments at 8am. Four bays. Nothing wrong with that.
Except three of those four customers are waiting in the lobby, and the fourth dropped their car off at 7:15. You have one lift that can start on the drop-off whenever it likes, and three cars that need to be in and out while their owners sit twenty feet away watching the clock.
That is not four appointments. That is a bad morning.
Two appointments that share a name and nothing else
A waiter and a drop-off consume your shop completely differently, and the difference is not the work — it is the flexibility.
A waiter owns a bay for a specific window. The job has to start close to the appointment time and finish close to the estimate, because a person is sitting in your lobby measuring both. You cannot pull the car out to make room for something urgent. You cannot let it sit while you wait on a part. The promise is the time, not just the work.
A drop-off owns a day. It can start at 8am or 11am. It can go back on the lift after lunch. If a part is late, the customer finds out at pickup rather than from a chair in your waiting room. It absorbs disruption, which is exactly what a busy shop needs some of its work to do.
Book both from one pool of "appointments per hour" and you will regularly commit to more simultaneous, inflexible work than the building can do.
The failure is asymmetric
What makes this worth fixing is that the two mistakes cost very different amounts.
Overbook drop-offs and you have a long day. Cars sit slightly longer, one or two get finished tomorrow, and most customers never notice because they weren't waiting anyway.
Overbook waiters and you have three people in your lobby watching an estimate slide past. That is the scenario that produces the one-star review about "sat there for two hours for an oil change." The work was fine. The scheduling wasn't.
So the two need separate limits, and the limit on waiters should be the stricter one.
What this means for your booking page
The practical consequence is that "how many appointments can I take at 8am" is the wrong question. There are two answers, and they are different numbers.
A booking page that only understands one kind of appointment has to pick one of those numbers. If it picks the generous one, you get the lobby full of waiting customers. If it picks the cautious one, you turn away drop-offs you could easily have taken — which is worse, because drop-offs are the work that makes the rest of the day survivable.
The shops that get this right treat the two as separate capacity with separate limits, so the page can be genuinely full for waiters and still open for drop-offs on the same morning. That is a question worth putting to any scheduling vendor directly: can your system be full for one appointment type and open for another on the same day? A surprising number cannot, and it does not come up in a demo unless you ask.
Drop-off is the offer most shops are hiding
Worth saying plainly, because it comes up in nearly every scheduling conversation we have: a lot of shops accept drop-offs happily on the phone and never mention them online.
The booking page offers times. Times imply waiting. A customer who cannot spare ninety minutes on a Tuesday morning sees no option that fits, and doesn't book — even though "leave it with us Tuesday, pick it up after work" would have suited them perfectly and suited you better.
Making drop-off a visible, bookable choice does two things at once. It captures customers who were never going to wait, and it moves work into the flexible pool that keeps your day recoverable when something goes wrong.
It also tends to be the easier sell. "Drop it off in the morning, we'll have it back to you by five" asks less of a customer than any specific appointment time does.
The test
If you want to know whether your current setup has this problem, look at last month's schedule and ask one question: on the days that went badly, how many people were waiting?
If the bad days correlate with waiter count rather than with total car count, your pools are wrong. The fix is not working faster. It is refusing the fourth waiter at 8am while still cheerfully taking the drop-off.
PISTn's Appointment Scheduling system treats waiting and drop-off as separate capacity, with independent limits, so the booking page can be full for one and open for the other. Book a demo and we will set it up against your bay count and your lobby.
