A scene from a sitcom, at a car rental counter. A customer walks in holding a reservation confirmation. The clerk says: yes, we received it. But unfortunately, all our cars are rented out. The customer asks back: isn’t a reservation exactly about keeping the car? That is the whole point of a reservation. The clerk has no answer. The audience laughs on the spot. The laugh has a reason: everyone has met the instant confirmation that evaporates at pickup. The dialogue is exaggerated; the structure is real. Comedy works by magnifying common sense, and the lecturer screened this clip in class as a specimen of customer service going wrong — not as a joke.
Taking a booking is not the skill
The essence of a reservation lies not in accepting but in keeping. Accepting a booking is the floor of capability: receive the information, send a confirmation, nod. Keeping the booking is the real craft: the car must actually be there on pickup day. Places that take bookings are everywhere; places that honor them are few. However fast the confirmation email arrives, if the car is not there, the paper is only paper.
The process runs, the work does not happen
The backstage is even sharper. The complaint gets escalated, and the clerk says: very sorry, my supervisor says nothing can be done. The camera cuts backstage, where the same clerk says: they think I’m talking to the customer, so I just pretend to talk — it looks like I’m speaking, but actually I’m saying nothing. That is not laziness; that is a process running while the work does not happen. The ticket goes around one full loop, and the car still is not there. What the customer sees is motion, not result.
The person standing at that counter, clutching a confirmation email, is wronged in a particular way: nothing was done wrong on his side, yet he pays for someone else’s broken process.
Overbooking is not the sin; passing the buck is
Someone will say: rental companies and airlines overbook all the time — using probability to squeeze out no-shows, efficiency first, nothing wrong with that. But the convention only stands when consequences are carried. Industries that genuinely overbook come with the full set of moves: compensation, rebooking, upgrades. That is managing probability. The counter in the sketch is different — it neither kept the car nor admitted fault, and with one line, my supervisor says nothing can be done, the entire risk shifted onto the person who made the reservation. Accepting the booking was the company’s business; failing to keep it became the customer’s business. That is not efficiency. That is dumping.
What a system magnifies depends on what the process lacks
Another objection: this was a human counter; a system would leave records. A system can just as well do only the accepting half — confirmation emails arrive in seconds while vehicle dispatch goes unattended. Technology magnifies the process, and where the process lacks keeping, the system magnifies the lack too. The thing to blame was never the tool. It is the mechanism that scores bookings taken and never scores bookings kept.
Losing the car is not the crime; the closing is
Running out of cars is not a sin. The sin is the closing: no admission of fault, no proactive remedy, just a compact car pushed across the counter as a substitute, plus a line about nothing that can be done. The same shortage, handled with an admission first and a choice second, and the customer remembers a different company. Keeping a reservation is hard, and the hard part is not the car. It is the step of admitting fault.
What is booked is paper; what is kept is the booking
Taking a booking is the floor of capability; keeping one is the substance of trust. A customer can rent from any counter, and trust goes only to the one that keeps the reservation. Service fails, more often than not, at keeping — not at accepting.
