His expression changed almost immediately.
The report contained copies of system records.
Complaint histories.
Modification logs.
Emails.
Approval records.
And a timeline showing how specific complaints had been rerouted.
Camille waited until everyone had read the first section.
Then she spoke.
"Trevor, do you recognize these entries?"
He looked down.
"Yes."
"Did you modify them?"
"Some."
"Why?"
"Because they were customer-service issues."
"All of them?"
"Not necessarily."
"Then which ones?"
Trevor looked toward Martin.
Martin did not move.
Trevor cleared his throat.
"The Strategic Accounts team had authority to manage certain customer complaints."
Rebecca spoke.
"That is not in dispute. The question is whether you had authority to reclassify safety and conduct complaints."
Trevor nodded.
"We had discretion."
"Where is that discretion documented?"
He hesitated.
"I would need to review the policy."
Camille looked at him.
"You have been using this system for years."
"Yes."
"Then you should know whether the authority was documented."
Trevor shifted.
"It was understood."
"By whom?"
"Commercial leadership."
"Which leaders?"
He looked toward Martin again.
Camille followed his eyes.
"Martin?"
Martin folded his arms.
"Trevor is describing an operational practice. I don't think we should turn every internal decision into a disciplinary matter."
Rebecca looked up.
"Some of these decisions involved complaints of threats and physical aggression."
Martin shrugged.
"Those incidents were handled."
"How?"
"Through customer recovery."
"Was the captain notified?"
"Not always."
"Was security notified?"
"Not always."
"Was the employee protected from retaliation?"
Martin looked irritated.
"Nobody was retaliated against."
David opened another document.
"An employee who reported a complaint involving a high-value customer was removed from a preferred route assignment."
Martin turned.
"That was an operational decision."
"Made three days after the complaint."
"So?"
David placed another page on the table.
"The manager approving the reassignment cited the employee's 'relationship-management difficulty.'"
Trevor looked down.
Martin said nothing.
Camille leaned forward.
"Let's discuss the phrase escalation discouraged."
Trevor sighed.
"It was meant to prevent unnecessary escalation."
"What is unnecessary?"
"Routine disagreements."
"An employee being insulted?"
"Depends on the severity."
"A passenger being threatened?"
"That should be reported."
"Then why were those reports closed?"
Trevor spread his hands.
"Because we were trying to maintain customer relationships."
Camille stared at him.
"At whose expense?"
Trevor looked confused.
"Excuse me?"
"At whose expense were you maintaining those relationships?"
He did not answer.
Camille continued.
"The flight attendant who was insulted. The gate agent who was humiliated. The employee who was threatened. The passenger who was intimidated."
She paused.
"You were protecting the relationship by transferring the consequences to people with less power."
Trevor's expression hardened.
"That's an unfair characterization."
"Then explain the records."
He glanced at the report.
"Corporate customers generate significant revenue. They expect a certain level of service."
"Service?"
Camille's voice became sharper.
"Is abuse a service preference?"
Trevor looked away.
Martin interrupted.
"We need to be realistic. Corporate customers are not ordinary passengers. They have negotiated agreements, dedicated support, and specialized expectations."
Camille turned toward him.
"Specialized service is not specialized immunity."
Martin shook his head.
"That's a slogan."
"No. It's a boundary."
She placed a printed email on the table.
"Read this."
Martin looked down.
The message was his.
Losing Voss would cost more than a dozen complaints.
He stared at it.
Then looked up.
"That was taken out of context."
Rebecca spoke.
"What context would justify the statement?"
Martin looked toward her.
"I was discussing the commercial impact of a major customer."
Camille nodded.
"And you concluded that losing the customer would be more expensive than addressing a dozen complaints."
"That's not what I meant."
"It's what you wrote."
Martin leaned forward.
"You cannot run a company by treating every complaint as an existential crisis."
Camille remained still.
"Nobody is asking you to."
"Then what are you asking?"
"Why you allowed a customer to become more important than the employees responsible for serving him."
Martin's jaw tightened.
"Because someone has to protect the revenue that pays those employees."
James spoke for the first time.
"Revenue does not give customers permission to abuse people."
Martin turned toward him.
"That's easy to say when you don't manage the accounts."
James shook his head.
"I manage operations. I know exactly what happens when employees believe leadership won't support them."
Camille looked toward Rebecca.
"Continue."
Rebecca opened a new section.
"There's another issue involving Trevor Lang."
Trevor straightened.
"What issue?"
"Potential undisclosed financial relationships."
The room became very quiet.
Trevor's expression changed.
"What are you talking about?"
Andrew opened his laptop.
"We found evidence that you hold an indirect financial interest in an aviation-software company backed by an investment fund associated with Graham Voss."
Trevor stared at him.
"That's private."
Rebecca answered.
"It is relevant to a potential conflict of interest involving a corporate account you managed."
Trevor looked toward Martin.
Martin had gone pale.
Camille watched both men.
"Was this relationship disclosed?"
Trevor hesitated.
"No."
"Why?"
"It wasn't relevant to my work."
Rebecca opened another document.
"Your investment vehicle received financial benefits from the company in question while you were overseeing the VossTech relationship."
Trevor shook his head.
"That's an exaggeration."
"Then explain the arrangement."