Upgrading to F when checking in on VX, a question
Aug 15, 2007 | 12:30 pm
#1
Original Poster
Moderator: Luxury Hotels and FlyerTalk Evangelist
Join Date: Sep 2002
Location: Palo Alto, California,USA
Posts: 18,255
Upgrading to F when checking in on VX, a question
I paid the $25 extra for the "more legroom" row in Y. VX offers lower cost upgrades to F at check-in if F is still available, on SFO-JFK that is available for $175. Now if I decide to do a check-in upgrade to F (should it be available), shouldn't the upgrade fee be reduced by that $25? Has anyone tried this yet?
The VX website is currently refusing to go to the FAQs to answer that question or any other when accessed by Firefox. This used to work, I guess VX is already learning about "enhancements" from the mainline carriers!
From IE, the FAQs work, but they don't answer this question which is, admittedly, rather obscure.
The VX website is currently refusing to go to the FAQs to answer that question or any other when accessed by Firefox. This used to work, I guess VX is already learning about "enhancements" from the mainline carriers!
From IE, the FAQs work, but they don't answer this question which is, admittedly, rather obscure.
Aug 15, 2007 | 7:04 pm
#2
Join Date: Mar 2003
Location: San Diego, CA
Programs: Delta SkyMiles Gold, Hilton HHonors Diamond, and Royal Caribbean Pinnacle Club
Posts: 1,009
I paid the $25 extra for the "more legroom" row in Y. VX offers lower cost upgrades to F at check-in if F is still available, on SFO-JFK that is available for $175. Now if I decide to do a check-in upgrade to F (should it be available), shouldn't the upgrade fee be reduced by that $25? Has anyone tried this yet?
The VX website is currently refusing to go to the FAQs to answer that question or any other when accessed by Firefox. This used to work, I guess VX is already learning about "enhancements" from the mainline carriers!
From IE, the FAQs work, but they don't answer this question which is, admittedly, rather obscure.
The VX website is currently refusing to go to the FAQs to answer that question or any other when accessed by Firefox. This used to work, I guess VX is already learning about "enhancements" from the mainline carriers!
From IE, the FAQs work, but they don't answer this question which is, admittedly, rather obscure.
Aug 18, 2007 | 1:18 pm
#3
Join Date: Jun 2002
Programs: Hyatt Explorist, IHG Platinum, Celebrity Cruises Elite Plus
Posts: 1,266
If I book Y now, and decide at a later date to upgrade to F (before date of travel and check-in), will VX charge me their $40 change fee in addition to the difference of fare? Or does upgrading not fall under the umbrella of a fee-based "change"?
Aug 18, 2007 | 10:52 pm
#4
Join Date: Apr 2002
Posts: 1,374
Playing with the website a bit, it appears that if you make a change from Y to F, the change fee is shown as $0 in the change summary, which suggests no; however, when last I tried, you can't make this change on the website; a message says you have to go to the airport. I assume that calling Res would also work, but I don't know if they would also consider this to be a fee-free change. Why not call and ask?
Aug 25, 2007 | 4:38 pm
#5
Join Date: Jun 2002
Programs: Hyatt Explorist, IHG Platinum, Celebrity Cruises Elite Plus
Posts: 1,266
I paid the $25 extra for the "more legroom" row in Y. VX offers lower cost upgrades to F at check-in if F is still available, on SFO-JFK that is available for $175. Now if I decide to do a check-in upgrade to F (should it be available), shouldn't the upgrade fee be reduced by that $25? Has anyone tried this yet?
Originally Posted by 21A
Playing with the website a bit, it appears that if you make a change from Y to F, the change fee is shown as $0 in the change summary, which suggests no; however, when last I tried, you can't make this change on the website; a message says you have to go to the airport. I assume that calling Res would also work, but I don't know if they would also consider this to be a fee-free change.
Aug 25, 2007 | 11:22 pm
#6
Join Date: Apr 2002
Posts: 1,374
Sounds like it was just a temporary glitch that got fixed.