Originally Posted by
eng3
This is true if you constantly monitor PN until the CPU window. Otherwise, at least with pz, you might get upgraded.
Also, often the instant upgrade button direct work and you have to call in
Were you suggesting that you're more likely to get an upgrade by applying PPs to your reservation, rather than relying on the "instant upgrade"? For routes like IAD-SFO, there's no chance for a PZ upgrade, but there is a nonzero chance for a PN upgrade, provided you catch the PN space at the right time.
Originally Posted by
eng3
If PN space opens, are you automatically upgraded or do you have to push the button. (That's been my experience at least). I assume once you are in the CPU window, you'd get automatically upgraded.
If PZ space becomes available, you're suppose to automatically get upgraded if you're next on the list (assuming it works)
Therefore, PN, one must monitor (until the cpu window I assume). if PZ waitlisted, one does not because it "should" be automatic.
What did I get backwards?
As for the button, I've had a few times where I click it and it says an error occured or I can't be upgraded. I'll go back and the button is still there. Then I call in and they they me I can't be upgraded and refer to my plus points waitlist. Eventhough if I look I'm not waitlisted because it doesnt work.
So maybe the button sometimes shows up eventhough PN=0. Maybe the agent is looking at PZ instead of PN. I just know there have been times the button shows up and I can't upgrade. This is very often (EWR-IAD) so I'm often too lazy to look further into this.
The CPU window is largely irrelevant nowadays because United sells premium cabin seats so effectively, except for short-haul flights. By T-4 days, there are usually very few seats left for CPUs. United tends to hold back the last few seats for upsells rather than offering them for free as CPUs.
To accept an instant upgrade, you should try both the app and the website, though the app tends to work better. I had some trouble with the EWR-IAD instant upgrade, but it worked a day later. I’m not sure why this route is so problematic.