The test arrived on Monday morning.
Robert called me shortly after nine, and I could hear the strain in his voice before he finished saying hello.
"We have a serious complaint from a guest who checked out yesterday," he said. "It involves the front desk and the evening supervisor. The guest says she was charged for a room she never received."
"Has anyone reviewed the booking history?"
"Yes. The initial records suggest a reservation change was processed incorrectly. The guest also says the supervisor dismissed her concerns and told her she had misunderstood the confirmation."
I sat down at my desk.
"Has the complaint been entered into the new system?"
"Yes."
"Is the case marked resolved?"
"No. The team has placed it under review."
That was encouraging, but I wanted to know what had happened before the complaint reached management.
Robert explained that the guest, a woman traveling alone for a medical appointment, had arrived late on Saturday evening. She had a confirmed reservation for one night. When she reached the desk, the receptionist could not find the booking in the main system. The employee checked the secondary records and discovered that the reservation had been moved to another date after a change request was entered incorrectly.
The guest had shown the receptionist an email confirming the original date. The receptionist had called the evening supervisor, who told the employee that the system should be trusted unless there was clear evidence of an error.
The guest waited while the supervisor reviewed the records. Instead of checking the original transaction history, he told her that the booking partner had probably changed the reservation. When she insisted that she had not requested a change, he said that the hotel could not be responsible for mistakes made by outside companies.
The guest eventually received a room after the supervisor approved a manual adjustment. But when she checked out, she discovered that the original charge remained on her account, along with a second charge for the replacement booking.
She had asked for a written explanation and a refund. The supervisor had promised to investigate, then closed the conversation by telling her that billing would contact her.
No one had contacted her by the following afternoon.
"Who was the supervisor?" I asked.
Robert named him.
I recognized the name from Lupita's earlier feedback. It was the same supervisor who had continued to prioritize room-completion figures over unexpected guest requests. He had not been accused of deliberate misconduct before, but the pattern was becoming concerning.
"What have you done so far?" I asked.
"I've assigned the complaint to human resources and corporate operations. The supervisor has been removed from handling guest disputes while we review the records. The guest has received confirmation that the case is open."
"Have you contacted her personally?"
"Not yet. I wanted to establish the facts first."
"Contact her today. Explain that the investigation is underway, apologize for the delay, and give her a realistic time for the next update. Don't promise a refund until billing confirms the transactions, but don't leave her waiting without information."
"I'll do that."
I asked Robert to preserve the reservation logs, the transaction history, the employee notes, and any correspondence with the booking partner. I also asked him to obtain separate accounts from the receptionist and supervisor before they discussed the incident together.
The process was familiar by now. What mattered was whether the hotel would follow it when doing so became uncomfortable.
By midday, the preliminary review showed that the guest had been correct. The original reservation had been confirmed for Saturday. An employee had entered a date change while processing another booking, and the system had carried the altered date into the guest's record. The booking partner had not requested the change.
The supervisor had then relied on the altered record instead of examining the transaction history.
The double charge was also confirmed. The hotel had collected payment for the original booking and processed a second charge when the replacement room was assigned. The billing team had issued a refund, but the guest still needed a clear explanation and confirmation that no additional payment was outstanding.
Robert called me again.
"The facts are straightforward," he said. "The supervisor should have checked the transaction history. He didn't, and he dismissed the guest's evidence."
"What does he say?"
"He says the lobby was busy and he believed the booking partner was responsible. He also says he was trying to prevent an argument at the desk."
"Did he document the conversation?"
"Yes, but his notes say the guest accepted the explanation."
"Did she?"
"No. Her complaint says she asked for a written explanation and was told billing would contact her."
I looked at the report.
"Then the notes are inaccurate."
"They appear to be."
"Did he knowingly misrepresent the conversation?"
"We haven't established that yet. I want to interview him before making that determination."
"Good. Don't turn an inaccurate note into a finding of dishonesty without evidence. But make sure the discrepancy is documented."
Robert agreed.
That afternoon, the supervisor attended a formal interview with human resources. He acknowledged that he had not checked the original transaction history and that he had assumed the booking partner was responsible. He said he believed the guest was becoming unreasonable and wanted to move the queue along.
When asked why he had recorded that she accepted the explanation, he said he had understood her decision to leave the desk as acceptance.
The explanation was weak, but the investigator did not immediately conclude that he had deliberately falsified the record. The supervisor had made a serious judgment error, failed to verify information, and recorded an outcome that the guest disputed. Whether he had knowingly misrepresented the conversation required further evidence.
The company placed him on temporary reassignment while the review continued.
I agreed with that decision.
A fair system had to work for employees as well as guests. If we demanded accurate records from staff, we could not abandon fairness the moment a supervisor's actions became difficult to defend. The facts needed to be established, and the consequences needed to reflect what the evidence showed.
But fairness did not mean postponing every difficult decision until the people involved were comfortable.
The guest received a written apology that afternoon, along with confirmation of the refund and an explanation of the reservation error. Robert offered to speak with her directly. She accepted the written response but declined a phone call, saying she had already spent too much time trying to correct a problem that should never have occurred.
Her reply stayed with me.
We often measured service recovery by whether a guest accepted the hotel's offer. But a person could accept a refund and still leave with a justified loss of confidence. The hotel could correct the financial mistake without pretending that the experience had been repaired completely.
I asked the team to record the case as financially corrected but with the service complaint still under review until the investigation and corrective actions were complete.
That distinction became important during the next management meeting.
One department head argued that keeping the case open would make the hotel's performance look worse even though the guest had been refunded. Another said the new system was creating unnecessary administrative work.
Robert listened to both arguments before responding.
"The case isn't complete because the money has been returned," he said. "We still need to understand why the reservation was changed, why the supervisor failed to check it, and why the guest wasn't contacted when promised."
The room fell quiet.
He continued.
"We used to treat a complaint as finished when we had something to offer the guest. That isn't enough. If we don't correct the process, the next person may experience the same problem."
I was not in the room, but David relayed the discussion to me afterward. He said Robert had resisted pressure to close the case prematurely, even though doing so would have improved the monthly figures.
That was the first concrete sign that the general manager's behavior was changing under pressure rather than merely in front of me.
Lupita also contributed to the response. She helped develop a short training scenario based on the reservation error, with the guest's identity and personal details removed. The exercise asked employees to identify what information should be checked, when a supervisor should become involved, and how staff should communicate uncertainty without blaming the guest.
She insisted that the training include the supervisor's mistake as well as the receptionist's. A procedure could not work if employees learned only to follow instructions without understanding when those instructions required verification.
"People need to know what to do when the system is wrong," she told Robert. "Otherwise they'll treat the screen like it's more trustworthy than the person standing in front of them."
Robert agreed to include the scenario in the next training session.
The investigation concluded later that week. The supervisor had failed to verify the booking history, dismissed the guest's evidence, and recorded the outcome inaccurately. The review found insufficient evidence to establish that he had deliberately falsified the record, but it determined that his conduct fell below the hotel's standards and that his handling of the complaint reflected previous coaching concerns.
He was removed from the supervisory role and placed under a formal performance process for a position without responsibility for resolving guest disputes. Human resources would review his progress before deciding whether he could return to supervisory duties.
The decision was difficult for the hotel. The supervisor had been experienced, efficient, and popular with several managers. Removing him created a staffing gap during a busy period.
But keeping him in a role he had shown he could not perform reliably would have undermined the entire review.
Robert informed the department heads of the decision and explained the evidence behind it. He did not disclose unnecessary personal details or invite gossip. He made it clear that the standard applied to everyone, regardless of seniority or performance in other areas.
I called him that evening.
"You made a difficult decision," I said.
"I should have made it sooner."
"Perhaps. But what matters now is whether you continue applying the same standard when the next case involves someone you like."
He was quiet for a moment.
"I understand."
I hoped he did.
The next day, the guest sent a brief email thanking the hotel for correcting the charges and explaining the error. She did not offer a glowing review or say that everything was forgiven. She simply acknowledged that the hotel had finally provided a clear answer.
I was grateful for that response, precisely because it was limited. It did not turn a failure into a success story. It showed that the hotel had done what it should have done from the beginning.
That evening, I called Lily before bed. She was sitting at the kitchen table with a new drawing, this one showing our house, a vase of roses, and three figures holding hands.
"Who's this?" I asked, pointing to the smallest figure.
"Me."
"And this?"
"You."
I pointed to the third figure.
"Daddy."
She nodded.
"He's in the picture because he belongs with us."
I felt my throat tighten.
"Yes, sweetheart. He does."
She told me that her class had discussed what people should do when they make mistakes. Some children thought they should apologize. Others said they should fix what they had broken. Lily said both things mattered, because an apology did not put something back together by itself.
I looked at the drawing.
"That's a good answer."
She shrugged.
"It was easy."
After we said goodnight, I remained at the table for several minutes. The Grand Regent's latest complaint had tested the new process in a way that no training session could have predicted. The hotel had been under pressure, the person responsible had been experienced, and closing the case quickly would have improved the numbers.
This time, the manager had allowed the investigation to continue.
The system had worked, at least once.
Now we needed to make sure it continued working when the attention faded, when the records became less dramatic, and when the people involved were not as easy to identify.
Click here to continue reading: PART 12: One Year Later, the Roses Returned to the Grand Regent and Reminded Me What It Really Meant to Own a Hotel
A Sleeping Child, a Crushed Bouquet, and the Receptionist Who Decided We Were Too Poor to Stay
Part 11 of 12
