Story code: ST-000998
Part 2: She Let Him Keep Defining It
Rick should have backed off when Marisol asked him which field showed this so-called ladder lock execution window, but he did the opposite. He sat forward, put two fingers on Nina’s table without touching her phone, and started expanding the term like he was teaching a seminar instead of talking about her account on a recorded call. The keyboards behind me kept clicking, the speakerphone light stayed steady, and Marisol let him build the trap himself.
“It’s not always a single field,” Rick said. “You infer it from the sequencing. The route, the timing, the way the lock condition interacts with the price ladder.”
Marisol said, “What route are you looking at on the customer confirmation?”
Rick answered right away, but he answered sideways.
“You’re being too literal,” he said. “These retail confirmations simplify things. That’s my point. Nina sees a basic fill and thinks that’s the whole story.”
Nina kept her eyes on the phone. “I’m looking at the confirmation right now,” she said. “It shows the order type, the quantity, the price, and the time. I’m asking why he keeps saying there was some extra condition.”
Rick gave another little laugh, this one shorter. “Because there was. You just don’t know what you’re reading.”
He said it in that patient, public way people use when they want the humiliation to sound helpful.
Marisol did not react to the tone. “Ms. Alvarez,” she said, “please read the order type exactly as displayed.”
Nina read it out. Plain language. One line. No special condition in it.
Rick cut in before she finished the next line. “That’s not dispositive. You’re ignoring the execution environment.”
Marisol asked, “Is ‘ladder lock execution window’ a term used in our order disclosures or confirmation language?”
Rick answered immediately. “Not in customer-facing wording, no. It’s trader language.”
Marisol said, “Understood. Then I need to separate platform terms from your interpretation.”
That changed the air in the room. Not dramatically. Just enough that even the normal office sounds around us seemed sharper. Nina looked up toward the ceiling speaker for the first time since the call started. Rick kept talking before the pause could settle.
“You’re making this more complicated than it is,” he said. “She placed a sell, the market moved, and the ladder lock protected the execution pattern. That’s why the confirmation looks ordinary after the fact.”
Nina finally turned her phone a few inches outward, enough that I could see Marisol’s mirrored desktop view on the second monitor beside the call console. Same transaction. Same plain fields. No hidden language blooming out of it no matter how often Rick said the phrase.
Marisol asked Nina for the timestamp. Nina read it. Marisol repeated it back and then asked for the share amount. Nina read that too. Rick started talking over the numbers halfway through, then stopped when Marisol spoke across him for the first time.
“Please let her finish reading the confirmation.”
Rick went quiet. Not for long, but long enough to be noticeable.
When Nina finished, Marisol said, “Thank you. I also want to confirm whether the dispute is about execution quality, order type selection, or account authorization. Ms. Alvarez, in your own words.”
Nina answered carefully. “I’m saying what he keeps describing is not what I saw when I entered the trade, and he keeps telling me I can’t object because I don’t know his terms.”
Rick came in hard on that.
“Nobody said she can’t object. I said she can’t object intelligently if she doesn’t understand active trading mechanics.”
Marisol let a beat pass. “Noted.”
That one word landed differently than anything else on the call because she said it like she was placing it somewhere permanent.
Then she asked Nina to navigate one screen back and confirm what the app labeled the order before submission. Nina did it slowly so the taps were audible. Rick started explaining again, faster now, saying pre-submission labels were simplified, saying serious traders used context, saying the app would never spell out internal execution windows for end users.
Marisol kept him talking just enough to narrow him down.
“So your position,” she said, “is that the customer-facing record can appear inconsistent with the actual order behavior, and your explanation for that inconsistency is this ladder lock execution window.”
Rick answered at once. “Exactly. Thank you. Yes.”
Marisol repeated the phrase exactly as he had said it, every word clean and flat, and asked me to pull the standard order-description reference on the side terminal. I did. She did not ask for my opinion. She only asked me to verify that the customer confirmation fields on her screen matched what Nina was reading from the phone.
“They match,” I said.
Rick exhaled through his nose like the whole process was beneath him. “Of course they match. That’s not the issue.”
Marisol said, “All right. I’m going to do one more step so we can test that.”
Rick stopped moving his hand over the table. Nina held the phone still. The room got very quiet except for one headset agent two stations over finishing a password reset.
Marisol’s voice stayed even.
“I want to bring up the live order detail view against the confirmation and have Ms. Alvarez confirm each field in real time. Then I want you to tell me exactly where your term maps to the record.”
Rick did not answer right away this time.
When he finally spoke, he said, “That’s not really how experienced traders would frame it.”