FlyerTalk Forums - View Single Post - March 3rd, 2012 System Integration Master Thread (PSS)
Old Mar 28, 2012 | 5:46 pm
  #2647  
edcho
10 Countries Visited
20 Countries Visited
30 Countries Visited
10 Years on Site
 
Join Date: May 2011
Posts: 5,815
Originally Posted by mgaiman
I just went to checkin for my first multi-pax post-3/3 flight. Upon checkin, SHARES decided to split my companion off into her own PNR, which has caused her to have her own status on the upgrade priority list instead of my status.

The united.com CPU policy states (http://www.united.com/web/en-US/cont.../upgrades.aspx):

"If the companion is a Premier member, the upgrade will be processed according to the highest Premier status level in the reservation."

Which is not the case. She's down at 35 and I'm at 16 (which in itself is depressing). Shouldn't she be 17?

Speaking as a software engineer, the CO IT team needs to start taking some pride in their software and raise their standards. This is frustrating.
This is a known "bug" -- you can still add her at the gate 3 hours before departure under your status. This actually is how CO operated (no companion until 3 hours before) and of course didn't implement the new policy properly.
edcho is offline