The customer-service booths had six plastic chairs arranged like a small classroom. Juma chose the last seat, not because he wanted to lead, but because each person could call from their own account without hearing anyone else’s data beyond what that person chose to share.
“We’re testing whether the case is individual,” he said. “We are not trying to trap an agent.”
Naima folded her arms. “Say that one more time and I’m putting a checklist sticker on your forehead.”
Brian laughed. Achieng did not. She was still angry about her bag and wanted somebody to admit the airline had wronged them.
Juma called first. The IVR requested his booking reference, surname and destination. After three minutes, an agent named Selly came on the line.
“I can see an irregular disruption group,” she said. “Case number IRR-7714.”
“I would like a case for my own booking.”
“That case serves the group.”
“I did not travel as a group.”
“I understand, but the record is linked.”
Juma asked for SMS confirmation. Selly sent it. He wrote down the time and case number, then ended the call without asking about anyone else.
Naima called from her phone. A different agent, Tom, gave her the same number.
“IRR-7714?” she said loudly.
“Yes.”
“My booking is different from his.”
Tom read a script: “Passengers associated with group disruptive conduct are being handled under a consolidated irregular-operations case.”
Naima started to ask whether that meant the airline knew it had made a mistake. Juma shook his head from his chair.
She glared at him, then changed the question. “Who is listed as group organizer on my booking?”
“I can’t disclose a third party’s identity.”
“Is the organizer a passenger?”
Tom paused. “The record says bulk disruption reconciliation.”
Brian wrote the phrase in his notebook. One by one they made their own calls. Four returned exactly IRR-7714. Two carried suffixes—`IRR-7714-B` and `IRR-7714-F`—but the base case remained the same.
“We’ve proved they tied us together,” Achieng said after her call.
“We’ve proved the case architecture,” Juma replied. “Not the reason.”
“Sometimes you are extremely annoying.”
“I’ve been told.”
Juma called again with one request. “I want a separation request for my booking. I don’t want a shared voucher if that is the price.”
Selly put him on hold. The cheerful waiting music felt insulting. Four minutes later she returned.
“I can open the request, but station approval is required.”
“Open it.”
“If you separate, shared accommodation support may be removed.”
“I understand.”
“Do you accept that?”
“For my booking only, yes.”
Selly read back the confirmation. Juma did not speak for anyone else. When he hung up, he explained the procedure: each person could request separation if they wanted. Nobody had to.
Achieng refused. “I have a child at home. I can’t pay for a hotel just to prove a principle.”
“Then don’t lose the voucher,” Juma said. “Choose what is right for you.”
Naima studied him. “So you’re fine with somebody staying inside the group if she needs a room?”
“I’m fine with somebody choosing her own cost. The problem is if the record says that choice means she committed someone else’s conduct.”
Brian received his SMS first: `Request received—pending station review.`
“So separation exists,” he said.
“Yes. But somebody at the station has to approve it.”
Tom refused to name the station manager when Brian called again, but he did explain that bulk disruption groups could be split by operational authority once identity and booking were verified. There was no rule saying twenty-one people had to remain one object forever.
That mattered more than an apology. Juma understood why: Ruth’s claim that “the system won’t allow it” could be true on the gate interface and still not be true of the entire system.
“That’s where the manager comes in,” Naima said.
Juma opened his new SMS.
`Separation from G-17 requested. Pending station approval.`
Below it sat a smaller field: `Approval queue: EM-04`.
“EM?” Brian asked.
“Ezekiel Mrema?” Achieng said.
Juma refused to turn initials into a person without verification, but he added the code to his index.
After the six calls, he drew a small table on paper: booking channel, case number, SMS status, separation requested or not requested. There was no passport-number column. Brian noticed that the two suffix cases had different destinations, yet both still sat under IRR-7714. That supported the idea that the case was an operational container, not one person’s complaint.
Achieng again declined separation after Selly confirmed her hotel voucher could disappear. “I don’t have money to play hero.”
“You don’t have to,” Juma said. “If you stay in the support package, that should not become a confession of conduct.”
Naima stared at the table. “That’s the real issue, isn’t it? They put the service and the story into one checkbox.”
Juma nodded. The system had not merely treated them as one travel object. It had tied accommodation, rebooking and an incident narrative together.
Tom later confirmed on Brian’s call that station approval could remove the disruption association without changing original ticket ownership. Juma asked Selly to repeat the same point for his own booking. She made no promise, but confirmed that “individual separation is a supported station action.” He noted the exact phrase and time and requested an SMS status rather than pretending his handwritten note was a recording.
As the confirmations arrived, each person saved their own message. Nobody forwarded screenshots into a group chat. The procedure could now be repeated without creating a new central owner of everyone’s data.
Before they left the booths, each caller repeated their case number back to the agent to avoid another transcription error. Juma filed his SMS with his own booking because the approval concerned his record alone.
The approval queue read `EM-04`.
Those initials matched station manager Ezekiel Mrema.