By early afternoon, Robert Haines had assembled the first batch of complaint records. They arrived in a neat digital folder, accompanied by a brief summary from the operations office. At first glance, the numbers seemed ordinary. Most complaints involved delays, billing questions, room preferences, or service requests that had taken longer than expected.
But as I read through the entries, a pattern began to emerge.
Several reports described employees being dismissed when they raised concerns. Others mentioned guests who had been treated impatiently after asking for clarification. A few referred to reservation problems that had been resolved only after a supervisor intervened.
The reports were short. Some contained little more than a date, a department, and a sentence indicating that the issue had been handled.
I asked Robert to explain the process used to close a complaint.
“The department manager investigates, records the outcome, and marks it resolved once the guest has received a response.”
“Does anyone verify that the guest agrees the issue was resolved?”
“Not in every case.”
“Does anyone review whether the same employee or department appears repeatedly?”
“The operations team reviews the monthly totals.”
“Totals don't tell you whether the same behavior is recurring.”
He nodded, though his expression suggested that he was beginning to see how much information the process had failed to capture.
I selected several entries and asked for the supporting correspondence. Two contained email exchanges. Another included a note from a shift supervisor stating that a guest had been offered a complimentary breakfast after a prolonged wait.
The compensation was reasonable. What concerned me was the absence of any record explaining why the delay had occurred or whether the underlying problem had been corrected.
“Who decides when a complaint is closed?” I asked.
“The department manager.”
“And who reviews the manager's decisions?”
“Usually me, if the matter is escalated.”
“Usually?”
Robert rubbed his forehead.
“Some complaints are considered minor.”
“Minor to whom?”
He did not answer.
I left the folder open and asked him to retrieve the original reservation logs from the previous evening. The system showed that my booking had been entered correctly through the corporate office. The executive block was available to authorized front-desk employees, and the reservation had not been canceled, altered, or duplicated.
The problem had been a failure to search the correct field.
That was a small operational mistake. The decision to send me elsewhere had been a separate choice.
Robert leaned over the screen. “Patrick may have been trying to move the queue along. The gala created a lot of pressure.”
“Then we should examine the staffing plan.”
“I've already reviewed it. We had the expected number of employees.”
“Were they trained to handle corporate reservations?”
“Yes.”
“Do the records confirm that?”
He opened the training folder. One employee's completion record was present. Another had attended the session but had not completed the final assessment. Patrick's file showed a completed module, but the date had been entered manually.
Robert stared at the screen.
“Someone will need to verify that.”
“Yes.”
I was not interested in turning a missing signature into evidence of misconduct. Records could be incomplete for ordinary reasons. But if the company wanted reliable service, it needed to know whether its training systems were functioning as intended.
We moved to the staffing reports. The front desk had been busy, but not unusually so for a gala night. There had been no documented emergency, no system outage, and no shortage of rooms caused by an unexpected overbooking.
The facts did not support the excuse that the staff had been overwhelmed.
“Please arrange separate interviews with Patrick and Karl,” I said. “I want their accounts before they have an opportunity to coordinate their explanations.”
Robert agreed.
“And I want a confidential meeting with Lupita.”
He looked uncomfortable again.
“She's a housekeeper. I'm not sure she would know much about the reception department.”
“She knew which reservation screen Patrick should have checked.”
“That may have been a coincidence.”
“Then the interview will establish what she knows.”
He closed the folder.
“I'll arrange it.”
I could tell he was struggling with the shift in our conversation. He had expected to manage a booking complaint, perhaps offer an apology, and return to preparing for the gala. Instead, the incident was leading us into questions about supervision, training, staff treatment, and the reliability of the hotel's reporting procedures.
I understood why he was uneasy. A manager could spend years believing that an operation was healthy because its public-facing results looked good. It was difficult to accept that a polished surface might conceal problems that employees had learned not to mention.
But discomfort was not a reason to stop asking questions.
Later that afternoon, I met Lupita in a small conference room away from the busy service corridors. She arrived carrying a notebook and sat near the edge of the chair. Her hands were folded tightly in her lap.
“I don't want you to feel that you need to defend yourself,” I told her. “You helped me last night, and I appreciated it. I'm asking to understand how the hotel works from your perspective.”
She nodded.
I asked her to describe what she had witnessed at reception.
She explained that the executive reservation system occasionally required a second search, particularly when bookings were made through the corporate office. She had seen similar issues before and knew where the secondary tab was located. She had not intended to challenge Patrick's authority; she had simply wanted the guest to receive an answer.
“Have you raised concerns about this procedure before?” I asked.
“Once or twice.”
“What happened?”
“The first time, I was told that reception staff knew their work better than housekeeping. The second time, my supervisor said I should focus on my own responsibilities.”
“Was the booking procedure changed?”
“Not that I know of.”
I wrote down her answer.
“Have you had other concerns about how employees are treated?”
She hesitated for a long time.
“I don't want to cause trouble.”
“You're not causing trouble by answering a question. I cannot promise that every concern will lead to a particular outcome, but I can promise that we will examine what you tell me fairly.”
She looked at me, trying to decide whether the promise was worth trusting.
“Some people can speak up,” she said eventually. “Others can't.”
“Why do you think that is?”
“Because some people are believed before they finish speaking.”
Her words were quiet, but they carried the weight of experience.
She explained that employees who had worked at the hotel for years sometimes felt that their observations mattered less than those of supervisors who had arrived recently. When someone raised a concern, the response depended heavily on who was involved. A complaint about a junior employee might lead to a formal meeting. A complaint about a manager might be treated as a misunderstanding and closed without a follow-up.
“Do you have examples?” I asked.
“I can give you dates. I don't have copies of everything.”
“That would help.”
She opened her notebook and began listing incidents she remembered. She had kept track of some dates because they related to staffing changes, training sessions, or conversations about work assignments. She was careful not to accuse anyone of deliberate wrongdoing when she could not support the claim.
That caution impressed me.
“May I ask about the supervisory position you applied for?” I said.
Her hands tightened around the notebook.
“I thought you might ask.”
“Robert mentioned it. I would like to understand what happened.”
“I applied three years ago. I had trained new housekeepers, helped with room inspections, and covered some scheduling duties when our supervisor was away. I believed I was ready for the position.”
“Were you interviewed?”
“Yes.”
“Who made the decision?”
“The operations manager at the time. He told me they wanted someone with a more professional presentation.”
“What did he mean by that?”
“He didn't explain.”
“Did you receive written feedback?”
“No.”
“Was another candidate selected?”
“Yes. Someone who had been working here for less than a year.”
“Was that person qualified?”
Lupita considered the question carefully.
“I don't know everything about his experience. He may have had skills I didn't. But I was never told what I needed to improve, and no one explained why I wasn't considered ready.”
That distinction mattered. A rejected applicant was not automatically a victim of unfair treatment. But a company that offered no meaningful explanation, no development plan, and no transparent selection criteria created an environment in which employees had little reason to believe that effort would be rewarded fairly.
“Did you appeal the decision?”
“No.”
“Why not?”
She gave a small, humorless smile.
“I needed the job.”
The answer was simple enough to make further questions unnecessary.
I thanked her and asked whether she would be willing to provide a written account of the incidents she had described. I made it clear that she could take time to prepare it and that she should include only what she remembered accurately.
She agreed.
Before she left, I asked whether she had ever considered leaving the hotel.
“Several times.”
“What kept you here?”
“My family depends on my income. And I still like taking care of guests.”
She looked toward the door.
“Sometimes a guest comes back and remembers your name. They tell you that you made their stay easier. That matters to me.”
“It should matter to the company, too.”
She gave me a cautious smile, then returned to her shift.
After the meeting, I reviewed the promotion records. Robert had retrieved the original application, interview notes, and decision summary. The file contained no clear scoring rubric. The notes referred vaguely to presentation and leadership presence, but offered no specific examples of deficiencies.
There was also no record of a development plan or a recommendation that Lupita pursue further training.
I did not know whether the decision had been unfair. I knew only that the documentation was inadequate to explain it.
That afternoon, David called to ask how the review was progressing.
“The reservation issue is straightforward,” I told him. “The wider concerns will take more work. I have evidence of inconsistent procedures and incomplete reporting. I've also heard concerns about how staff are treated and how promotions are decided.”
“Do you think the general manager knew?”
“I don't know yet.”
“Should we bring in human resources?”
“Yes. I want an independent review of the staffing decisions and complaint records. We should also make sure employees have a confidential way to raise concerns without going through the managers they may be complaining about.”
David agreed to arrange the appropriate support.
I ended the call and returned to the complaint folder. Near the bottom was an entry from three years earlier, dated shortly before Lupita's promotion application had been rejected. It referred to a disagreement between housekeeping and reception over a reservation problem. The complaint had been closed by the same operations manager who had overseen the promotion decision.
The description was brief, and the supporting documents were missing.
I read the entry twice.
It might have been unrelated. It might have been nothing more than an ordinary workplace disagreement.
But the dates were close enough that I wanted to know more.
I asked Robert to locate the original records, including any emails or internal notes that had not been transferred into the central system.
He promised to look.
As evening approached, I returned to Suite 904. Lily was sitting on the carpet, drawing a picture of the hotel. She had made the windows enormous and colored the lobby ceiling with bright yellow stars.
“That's a lot of stars,” I said.
“They're for Daddy.”
I sat beside her.
“It's beautiful.”
She pointed to a small figure near the entrance. “That's you. And that's me.”
“Where am I going?”
“Upstairs. To our room.”
“And where are the flowers?”
She added a red shape near the window.
“Here.”
I looked at the drawing for a long moment. She had included the hotel, the elevator, our room, and the vase. In her version, everything had a place. Nothing was missing, and nobody was being sent away.
I folded the picture carefully and placed it beside the vase.
Then my phone vibrated.
Robert had sent a message. He had found an archived email connected to the old reservation complaint. It appeared to contradict part of the summary in the central system.
He had not yet reviewed the attachment.
I opened the message and read the first lines.
The original complaint had not been closed because the problem was resolved.
It had been closed because a manager had decided that further discussion would be unnecessary.
I stared at the screen, feeling the shape of the investigation change once again.
The question was no longer simply why two receptionists had treated a tired mother with contempt.
It was whether the hotel had been teaching its employees, quietly and over time, that some people could be dismissed without anyone asking why.
And the records I had requested were beginning to suggest that the answer might be yes.
Click here to continue reading: PART 5: The Archived Email Revealed Who Had Decided That Some Complaints Were Better Left Unanswered
A Sleeping Child, a Crushed Bouquet, and the Receptionist Who Decided We Were Too Poor to Stay
Part 4 of 12
