The Car Service Appointment.
When the Brand Makes a Promise the Dealer Doesn't Keep.

What Happened

I needed my car serviced. Nothing unusual. Routine maintenance plus a recall item that needed attention.

I called the manufacturer's customer service line. The experience was smooth. The agent pulled up my VIN, confirmed the recall, checked what service was due, and booked the appointment at my local dealership. Before I hung up, I asked about a loaner vehicle—I had meetings that day and couldn't sit in the waiting room for three hours. No problem, the agent said. Loaner reserved. Confirmed. Done.

I showed up at the dealership on the appointed day, at the appointed time, expecting to drop off my car and drive away in a loaner.

The service advisor found my appointment in the system immediately. All the service details were there—the recall, the maintenance, the notes. But the loaner? No record of it. Nothing in their system. No vehicle set aside. No reservation.

What followed was an hour of the service advisor working the phones, checking availability, calling around to see if a loaner could be freed up. This person wasn't the problem. They were doing everything they could to recover from a situation that shouldn't have existed. They were being heroic—which, if you've read anything else I've written, you know is exactly the symptom I look for.

When an employee has to be heroic to deliver a basic experience, the system is broken. The heroism is the tell.

Eventually, they found a loaner. I got on my way—an hour late, with a day already rearranged around a problem that never should have happened. Not because anyone did their job poorly, but because the space between two organizations was completely undesigned.

Mapping the Operation

Let me map this as a Service Operation Map, because the structure of the failure matters more than the story.

In Deliberate Work, every customer journey moves through seven stages. We call the framework AAAERRR: Awareness, Acquisition, Activation, Engagement, Retention, Revenue, and Referral. These stages are organized into three zones—the Funnel (pre-customer), the Flywheel (active customer), and the Off-Ramp (designed exit). Within each stage, the actual work is structured as Workflows, which contain Stages, which contain Steps.

That hierarchy—Stage > Workflow > Stage > Step—is how we make the invisible architecture of a business visible. Let me show you what I mean by mapping exactly what happened to me.

Look at that map. The Funnel was clean—Awareness, Acquisition, and Activation all worked as designed. The Flywheel delivery was fine too. The entire failure lives in a single place: the zone boundary between Activation and Engagement, where the brand's commitment crossed from one organization to another.

This is the distinction that matters: making a commitment and transmitting a commitment are two different design problems. Most businesses only design the first one. They invest in the customer-facing experience—the call center, the booking flow, the confirmation email—and assume the internal handoff just... happens.

It doesn't. Not reliably. Not without design.

The Missing Piece: A Handoff Contract

In Deliberate Work, we call the boundary between commitment and delivery a zone boundary. It's the highest-risk transition in any operation map. It's where work is most likely to stall, context is most likely to be lost, and customer experience is most likely to fracture.

Every zone boundary needs a handoff contract—a designed specification of exactly what must travel from one side to the other before the receiving team begins work.

In my car service experience, the handoff contract between the brand and the dealer was incomplete. The appointment information crossed the boundary. The loaner reservation did not. And nobody on either side had a mechanism to detect the gap.

Think about what a complete handoff contract would look like here. The brand's system, upon completing the booking, would need to transmit:

This isn't complicated. It's a specification. But someone has to design it. Someone has to decide that the boundary between these two organizations is important enough to govern with the same rigor they apply to the booking experience itself.

Right now, the brand invests in making the commitment feel effortless. The dealer invests in making the service feel professional. But neither invests in the transition between them. That transition is where I lost an hour of my day. And it's where the next customer will lose an hour of theirs.

The Cost Nobody Measures

Here's what makes handoff failures especially insidious: the cost is real, but it's invisible to everyone except the customer.

The brand's call center probably has metrics for call duration, booking completion rate, customer satisfaction on the call. My call scored well on all of those. The agent was great. The experience was smooth. If they survey me about the booking, I'd rate it highly.

The dealership has metrics for service completion time, customer satisfaction at pickup, and probably some measure of service advisor performance. The advisor who helped me was excellent—they spent an hour solving a problem they didn't create and got me into a loaner.

But the hour I lost? The frustration of showing up prepared for a seamless handoff and getting improvisation instead? The rearranged meetings? That cost doesn't show up in anyone's dashboard. It lives in the space between two organizations' metrics—in the boundary that neither one measures because neither one owns it.

When nobody owns the boundary, the customer becomes the integration layer.

I was the one who had to stand at the counter and explain that the brand had promised me a loaner. I was the one carrying the context that the dealer's system didn't have. I was the one bridging the gap between two organizations that should have bridged it themselves.

This is the pattern. Whenever a customer has to repeat themselves, re-explain a commitment, or manually carry information from one part of your business to another, they're doing work that your system should be doing. They've become the handoff contract you never designed.

This Isn't Just About Cars

I'm telling this story because it happened to me and it's specific. But the structure of this failure is everywhere. If you run a business with more than one team, you have this problem. The only question is whether you've found it yet.

Sales → Delivery. Your sales team closes a deal. They've promised a timeline, a scope, maybe some custom provisions. The deal moves to the delivery team. How much of that context makes it across? Does the delivery lead get the full picture, or do they start the kickoff meeting by asking the client to explain what they bought? Every time a client has to re-explain what was already agreed, you're replaying my car service experience. The commitment was made. It wasn't transmitted.

Marketing → Sales. Marketing qualifies a lead. They've captured context—what the prospect is interested in, what content they engaged with, what problem they described. The lead routes to sales. Does the salesperson see that context, or do they open with "So, what brings you to us?" That question—which feels normal—is the sound of a missing handoff. The prospect already told your business what they need. Your business didn't pass it along.

HQ → Field. Corporate sets a policy, a promotion, or a commitment. The field team is supposed to execute it. But the communication is a memo, an email, a Slack message that's buried by noon. The customer shows up expecting the thing corporate promised. The field team has never heard of it. Sound familiar?

Every one of these is the same structural failure. Two teams share a customer journey. The boundary between them has no designed handoff contract. The customer absorbs the cost.

How to Find Yours

The diagnostic is straightforward. Map every point in your customer's journey where responsibility shifts from one team, system, or organization to another. Those are your zone boundaries.

For each boundary, ask three questions:

If the answer to question three is "the customer," you've found your car service appointment. You've found the place where a commitment is being made but not transmitted, where the customer is doing the integration work your system should be doing, and where an employee is being forced into heroics to cover for a handoff that was never designed.

The fix isn't a new tool. It isn't better communication. It isn't a Slack channel or a weekly sync. The fix is a designed handoff contract: a specification of exactly what must cross the boundary, a mechanism to transmit it, and a check that rejects incomplete handoffs before they reach the customer.

It's a 30-minute design problem. The cost of not designing it is an hour of every customer's time, compounded across every appointment, every deal, every handoff—forever.

The Deliberate Version

Now let me show you the same operation, redesigned. Same stages. Same organizations. But with a designed handoff contract at the zone boundary.

Same people. Same organizations. Same car. The only thing that changed is the boundary between Activation and Engagement. A designed handoff contract—specifying what must cross, validating that it arrived complete, and flagging gaps at the moment of booking instead of the moment of arrival.

That's the difference between accidental work and Deliberate Work. Not better people. Not more effort. Better design at the points where things are most likely to break.

Go Deeper