E-Upgrade Summary Bug?
 

Hi All,

Wondering if this has happened to any of you.

I was just looking at my E-Upgrade Summary, it shows 2 complimentary 500 upgrades expiring 3/2009 (in a few days)...then shows 3 expiring 6/2009.

Should it not read 1 expiring 3/2009, and 4 expiring 6/2009?

I thought that UA always pulled the closest to expiring upgrades when processing an upgrade.

You're assuming you always received them in batches of 4.

Look at your deposit summary -- did you by any chance receive 3 in 6/2008? Maybe as a customer service thing for some issue?

No, I checked, it was indeed a batch of 4 in 6/2008. Very strange.

I recall someone else having the same issue a couple of months ago. Have you tried calling to see what the real scoop is?

The e-upgrade summary page has an option to show detailed upgrade activity for a given date range. I'd do that and see what was deducted and when.

Possible explanation.

Let's say you had two segments in a trip.

Segment 1 needs two e500s and segment 2 needs one e500. You check in, and segment 1's upgrade clears, but segment 2's does not (or you didn't request an upgrade at check in or before).

So 2 e500s from the 3/2009 pool get deducted first taking you down to zero. There is an irrop on segment 1, and you don't get upgraded on the replacement flight. Segment 1's e500s will eventually be credited back, but likely not that day.

Later that day, you upgrade segment 2, and it requires one e500. It comes from the 6/2009 pool because you are at zero in the 3/2009 pool because M+ upgrade accounting hasn't caught up. So 4 goes down to 3 in the 6/2009 pool.

If something like this happened, you can make the case to M+ that you should get an e500 back; the irrop isn't your fault.

Thank you, MRE - you reminded me of something I did, and I think this explains it. My colleague and I were heading back to the Bay Area from MCI via DEN. He was flying to SFO, I was flying SJC. I decided to treat my employee to an upgrade, so I put in for upgrades DEN-Bay Area (waitlisted). His cleared, mine did not. I am thinking that this had something to do with it.