the ninth day, the response arrived, from a customer relations representative named Ellis Chen, and I read it standing in my kitchen, barefoot again, because some news can only be received barefoot, in the place where the first email had arrived. I liked that his name was in the signature — a person's name, not a department's — because a name means someone can be written back to, and being able to write back is the difference between a response and a wall. The response was careful, and partial, and real: it acknowledged the duplicate, it apologized without qualifying the apology into nothing, and it promised a review. A promise of a review is not a resolution. It is a door, left ajar. And doors, left ajar, are an improvement on doors closed — provided someone walks through them, and keeps walking, and writes down, as they go, what they find on the other side.
The last sentence bothered me. I read it three times, at the kitchen counter, with my coffee going cold. If protocol meant asking the upgrade passenger to move while the crew investigated — if protocol meant that the person with the newer assignment absorbed the uncertainty — then the protocol needed review, not praise. The crew had been kind. The process had still put the burden in the wrong place.
I replied the same evening. I thanked him for the explanation. I asked whether the airline had considered how to avoid placing the burden of uncertainty on the person with the newer assignment — whether there was a way to verify first and move second, rather than the other way around. I also said the crew had been respectful, and that my concern was with the process, not with the attendants. I wanted that distinction to be unmistakable. It is easy for feedback to be filed under “complaint about staff,” and I did not want Celia and Denise to pay for a system they had handled as well as anyone could.
A week later, Mr. Chen called. I was at my desk, between meetings, with a stack of route maps on one side and a cold cup of tea on the other. He introduced himself, apologized for calling during work hours — “I know you’re busy, I’ll be brief,” the way people say when they will not be brief but mean well — and said the airline’s customer experience team would review the procedure for duplicate seat assignments. He asked whether I would be willing to speak with them — not as a complainant, but as someone who had been through the process and could describe what it felt like from the seat.
He introduced himself the way people introduce themselves when they know they are calling about something uncomfortable: with his full name, his role, and a pause, as if giving me time to decide whether to be guarded. I decided, in that pause, not to be — not from naivety, but from strategy, because guarded people get guarded answers, and I wanted an unguarded one. He asked about the morning — not the airline's version of it, but mine: the aisle, the phones, the peppermint, Denise's tablet, the mediator from the second row, the feeling of being certain and contradicted at the same time. I told him, in the order the events had happened, not the order they had felt, because feelings, honored in their own column, do not need to become the story. He listened without interrupting, and then he asked a question I had not expected, and one that changed the shape of everything that followed: "What would have helped, in the aisle, that did not happen?" I thought about it, with the route maps on one side and the cold tea on the other, and I said: a script. Not a script for me — a script for the crew. A set of words, agreed in advance, for the moment when two passengers hold the same seat: words that name the problem as a duplicate, that separate the people from the paper, that promise a check of the manifest before anyone is asked to move. He wrote it down — I could hear the pen, which is a sound you do not forget when you are waiting to be heard — and he said he would take it to the training team, which is the sentence people say when they mean "I will try," and also the sentence people say when they mean "goodbye." I did not know, on that call, which one he meant. I knew only that I had been asked a question no one had asked me in the aisle — not "who is right," but "what would have helped" — and that the difference between those two questions is the difference between a dispute and a design. Disputes end when someone wins. Designs begin when someone asks what would have helped, and then builds it, so the next aisle does not need a winner at all.