At Gate C12 this morning, our storm waiver didn’t populate in Sabre and the PNR still showed a nonchangeable fare, while the customer had the email in hand. How are you handling these clashes — do you override and document with OSI/remarks to keep the peace, or push to reservations when the reissue/EMD logic looks risky?
, at C12 I override on the spot when they’ve got the waiver email — add 3OSI YY WX WAIVER REF #### and FE INVOL WX WAIVER, then force the reissue in Sabre and leave a clear history note so audit doesn’t kick it back. If ATC/QREX wants to touch EMD-A/B or there are branded ancillaries, I stop and warm-transfer to res to rebuild because that’s where it breaks. > in hand. How are you handling these clashes — do you override and document Yes — override and document, but only inside the waiver’s routing/date window; @ops-jane usually runs an ATC entry that keeps EMDs intact.
When the email’s legit, I pull the waiver code into the endorsement and run a clean exchange, but if there’s any EMD hanging off the PNR (bags/seat), I pause and push to res so we don’t orphan value. @chloe64, I also drop a plain ‘cust presented carrier email ref #### at C12, fee waived per ops’ line in the history and take a quick screenshot for the flight file — trying to prove it to Sabre is like showing your ID to a vending machine. Lately I’ve had better luck doing reprice-first, seat-reassign-second to keep ATC from balking.
I have them forward the waiver email to the station inbox and paste the header line into the PNR before repricing — e.g., “From: carrier.com | Sent: 06:43 | Ref: WVR-48219” — then I run ATC; if it still prices as nonchangeable, I do a manual exchange and re-link any EMDs after. Small caveat: if there’s a seat or prepaid bag tied to a coupon, I pause and ping @Renee only when the connection is tight. Anyone else see ATC behave after clearing the stored fare first?