Originally Posted by
seawolf
Old ticket wouldn't be cancelled if new ticket was not issued. Old ticket flight coupon will remain OPEN status until new ticket issued at which point, the old ticket status goes to EXCHANGED status.
Because CX resolved it on their end without AS intervention, what likely happened was AS did issued new ticket but failed to associate flight segments with the new flight coupons. Because the flight segments are still associated with the old ticket coupon which have a status of EXCHANGED, system would not allow a check-in. CX supervisor most likely looked at the record, saw the new ticket number and tied the flight segments with the new ticket coupons (which AS should have done when new ticket issued) which would be OPEN status and thus allowing check-in.
Thanks for the explanation. This reminds me the old days dealing with UA on itinerary changes. Back then Saudi's site was a god send to make sure the new ticket showed up with correct segments and"Open" status for the coupon, and the old ticket would show as you said, "exchanged".
Unfortunately since a year or more ago, Saudi site no longer worked for non-Saudi issued tickets. I have tried tickets issued with different programs, none works on Saudi site. Sad a tool to ensure reticketing accuracy no longer exists.
Is there any way to make sure the status of a reissued ticket is in order when it is correctly done?