When Systems Fail, Human Judgment Still Matters

Executive takeaway

This case began as a study of a fragmented customer experience. A customer attempting to rent a vehicle encountered contradictory information across Enterprise's online experience, centralized reservation support, Enterprise Plus loyalty support, and a local rental office. A promised pickup did not occur as expected. An internal maintenance task was completed while the customer waited. The customer had to initiate repeated follow-up and ultimately incurred an additional cost because of the delay.

Viewed only through that sequence, the lesson would be straightforward: organizations create customer friction when channels and operating teams do not carry the same commitments.

But the case did not end there.

After the customer provided detailed written feedback, an Enterprise area manager responded personally. He acknowledged repeated breakdowns, said he had held extensive conversations with the team, identified communication as a significant issue that had been addressed, and offered to reimburse the customer's financial loss. [4]

The customer ultimately chose not to pursue reimbursement. The management response mattered more.

The unanswered organizational question is whether what a capable local leader learns can travel back to the centralized processes, systems, and decision-makers that contributed to the experience. That is where this becomes an Organizational Change Management case.

The service proposition

Enterprise publicly offers free pickup at non-airport locations during normal business hours and directs customers to coordinate pickup with the local rental office. Its published guidance also says that a guaranteed pickup time requires confirmation with the local office at least two hours in advance. [1]

Enterprise Plus allows members to redeem points for free rental days through the Enterprise website or app. The current program terms state that free rental days cannot be redeemed for reservations booked through branch locations or other booking channels. [2]

Those distinctions matter because the customer in this case was not trying to bypass Enterprise's processes. She was trying to follow them.

What happened

The customer began online but could not identify a way to indicate that pickup assistance was needed. She called Enterprise for help and was routed to a centralized representative.

The representative created a reservation, told the customer she could subsequently be transferred to Loyalty to apply Enterprise Plus points, and advised that pickup could be provided later that afternoon.

Once transferred, Loyalty told the customer the points could not be applied because the reservation had already been created. At approximately the same time, the local office contacted the customer and explained that its pickup service ended earlier than the centralized representative had indicated.

The immediate rental was therefore no longer workable. The customer cancelled the reservation, rebooked for the following morning using the appropriate loyalty process, and spoke directly with the local office about pickup. She explained her timing needs and was told to call when pickup service began so someone could be sent.

The next morning, the customer called as instructed. Her address was confirmed and she was told someone would be sent shortly. Thirty minutes later, no one had arrived. When she called again, she was told that the driver had been completing an oil change before coming to pick her up. The driver arrived after another follow-up call.

Because the customer had made another commitment based on the timing discussed with Enterprise the previous day, the delay caused her to miss the beginning of a scheduled service appointment and incur an additional out-of-pocket cost.

The published two-hour Enterprise pickup guarantee is not the basis of this case. The customer had been given specific operating instructions by the local office the previous afternoon. The more useful question is whether a customer should be able to rely on instructions provided directly by the people delivering the service.

The first failure: the promise did not travel

The customer received different answers depending on which part of Enterprise was speaking.

• The centralized representative's loyalty guidance did not survive the transfer to Loyalty.
• The centralized pickup information did not survive contact with the local office.
• The local office's next-morning pickup expectation did not survive the branch's competing operating priorities.

None of these failures requires assuming bad intent or even poor individual performance. The more significant issue is structural.

That is promise portability. When it fails, customers become the integration layer between functions. They repeat information, reconcile contradictions, make additional calls, absorb delays, and adjust their own plans around inconsistencies they did not create.

OCM often operates in precisely this space between lanes.

Then a person changed the experience

The most important development came after the transaction was over.

The customer sent detailed written feedback explaining not simply that the pickup had been late, but how the different failures had accumulated and why the absence of communication mattered.

An Enterprise area manager subsequently responded in writing. He said the feedback had been taken seriously and had resulted in extensive conversations with the team. He identified lack of communication as his biggest takeaway, indicated that it had been addressed, described walking the team through the experience from the customer's perspective, and offered to reimburse the customer's financial loss. [4]

The response did something the earlier interactions had not. It considered the experience as the customer experienced it, rather than as a collection of separate transactions.

Human recovery can be more valuable than transactional recovery

The customer ultimately decided not to pursue reimbursement. The amount mattered less than the response.

That does not make the original failure acceptable, and it does not erase the financial consequence. It demonstrates something more useful: appropriate human judgment can restore goodwill that a process has damaged.

Enterprise itself publicly describes customer input as a source of operational learning, says it works to remove friction from the customer journey, and emphasizes the continuing importance of human interaction alongside technology. [3] In this case, the area manager's response was much closer to that stated philosophy than the experience that preceded it.

He did not need a perfect system in order to acknowledge what had happened. He did not need to debate whether each individual employee had technically followed a procedure. He looked at the cumulative experience, considered the customer's perspective, acted within his sphere of influence, and responded accordingly.

The harder question: can learning travel back upstream?

The area manager addressed the part of the problem he clearly could influence: his team.

The written response does not establish whether the other issues were routed beyond the local operation. The customer had also encountered problems involving centralized reservation guidance, loyalty redemption, and inconsistent pickup information across channels. Those issues may sit outside an area manager's direct authority.

There is no evidence in the available correspondence showing whether he escalated those issues, whether Enterprise has another mechanism that captured them, or whether centralized teams subsequently acted on them. The case therefore should not conclude that Enterprise failed to escalate them.

It should ask a more useful question: what happens when a capable local leader discovers that part of the customer failure sits outside the part of the organization he controls?

Organizations can inadvertently limit their strongest people when employees have responsibility for recovering customer relationships but lack a clear mechanism for converting what they learn into change elsewhere in the system.

• A local leader can coach a team.
• A local leader can apologize and recover a relationship.
• A local leader can often resolve a customer-specific financial consequence.
• A local leader may not be able to redesign a booking flow, change loyalty-system rules, correct centralized reference information, or align multiple operating groups.

If organizational learning depends primarily on the initiative and reach of the individual manager who happened to receive the complaint, the recovery may remain local even when the cause is not.

The second requirement: learning has to travel back

The first half of this case is about promise portability: can what the organization tells the customer travel reliably from one part of the experience to the next?

The second half is about the return path: can customer learning move back across those boundaries until it reaches the people with the authority to address each contributing condition?

When either direction breaks, customer experience becomes dependent on individual heroics.

Where OCM belongs

This is not primarily a training problem. It is also not solved simply by telling employees to communicate better.

The area manager demonstrated that empathy and effective service recovery can be strengthened locally. The broader OCM opportunity is to make that behavior part of an operating system that also captures what employees and customers are discovering.

Stronger change capability would create conditions in which:

• customer-facing commitments remain consistent as work moves across digital channels, centralized teams, loyalty functions, and local operations;
• employees know when a statement to a customer has become a commitment and what must happen if it cannot be fulfilled;
• frontline and local leaders have enough authority to recover the relationship without unnecessary escalation;
• recurring contradictions and exceptions can be surfaced beyond the local team rather than repeatedly solved one customer at a time;
• customer feedback is routed to the owners of the systems and processes capable of correcting the underlying condition; and
• the originating team can see what happened to the signal, so employees learn that raising an issue can actually produce change.

This is not about removing human judgment from the experience. It is about creating an organization in which good human judgment has somewhere to go.

What the alternative customer journey could have looked like

The ideal experience would not require every underlying system to be perfect.

The customer could have begun online, discovered that pickup required local coordination, and been directed clearly to the appropriate office. A representative helping with an Enterprise Plus rental could have recognized that redemption required the customer to complete the reservation through the eligible digital route rather than creating a conflicting reservation first.

If same-day pickup was no longer operationally feasible, that could have been communicated accurately before the customer planned around it. The following morning, the office could either have honored the pickup expectation or contacted the customer when another operational need threatened it.

And if a breakdown still occurred, someone could have acknowledged its effect immediately rather than leaving the customer to initiate each recovery attempt.

No single step requires extraordinary customer service. The value comes from making the experience coherent.

The commercial lesson

Organizations often think of service recovery as compensation: a discount, a credit, or a refund.

This case suggests that the more valuable recovery mechanism may sometimes be credible evidence that someone understood what happened and cared enough to act on it. The customer was offered reimbursement and chose not to pursue it. The management response had greater value.

That should not become an excuse to substitute empathy for reliable operations. Human recovery is powerful precisely because failures are inevitable. It should be the safety net, not the operating model.

And when a capable employee or manager repeatedly has to compensate for the same structural problem, the organization should treat that effort as evidence, not merely excellent customer service.

Conclusion

The most useful version of this Enterprise case is not a story about a rental-car pickup that went wrong. It is a story about two organizational movements.

Enterprise's systems and channels did not produce a coherent experience in this instance. A human response later did something the systems had not: it recognized the whole experience.

That response mattered enough that the customer valued it more than reimbursement.

The remaining question is larger than this branch or this customer. Organizations often say they want empowered people, customer feedback, and continuous improvement. Those ideas become meaningful only when the operating environment connects them.

A strong local leader should be able to recover a customer. A strong organization should also make sure that leader does not have to recover the same failure again.

This case study was developed with AI assistance and substantively reviewed, revised, and approved by Change Collaboration. The final content, source use, professional judgment, and conclusions remain Change Collaboration’s responsibility.