FlyerTalk Forums - View Single Post - Acceptable Comp for Improper Processing of Standby?
Old May 5, 2009 | 10:44 am
  #24  
fozz
 
Join Date: Dec 2004
Location: EWR and SAN
Programs: PWP Direktor of Homeland, CO Plat* 1MM,UA 1K,BD Gold,DL Gold,SPG Platinum, Marriott Platinum
Posts: 7,551
Originally Posted by mahasamatman
Read post #13. The OP was on the top of the BP5B waitlist. But BP5A trumps that. Always has, and (hopefully) always will.
I agree, it should stay that way. I

But in all the marketing fluff, Elites are always told standbys are sorted by elite status. In this case, they weren't. If you simply look at it from that angle, it was wrong. Perhaps the message they send with standby-priority needs to be revised not to give elites a sense-of-entitlement in all cases.

Personally, if I was in the same shoes, i wouldn't care unless it caused me to overnight in transit.

Originally Posted by emanon256
But the OP was not confirmed, why would they call for VDB's to let someone goo standby? Then they have to give out compensation to someone, in order to let a non-confirmed PAX fly. Makes no sense.
Well, I wouldn't expect them to do a VDB, but it would have been a nice way to avert a situation. Plus, now they have a stuck passenger in SFO. I guess the question is if the delay was just a few hours or if there was an overnight involved. if it was just a few hours, suck it up and deal. If there was an overnight then I don't believe it was handled properly.

Originally Posted by emanon256
1Ks are never told they have top Priority. In fact, the 1K benefit states:

Priority airport standby (where allowed by law) if you do not have a confirmed reservation on a Star Alliance flight.


Priority does not equate to top-priority.
From what I remember, on the gate monitors the order listed is:
1) Irregular Operations
2) Status (GS, 1K, PremEx, Prem)

In this case, both the OP and the four passengers were affected by #1. One would assume within #1, #2 is considered as the secondary sort order.

Last edited by iluv2fly; May 5, 2009 at 2:59 pm Reason: merge
fozz is offline