WilsonFlyer
DIS Veteran
- Joined
- Apr 24, 2008
I've got to say that I'm a little appalled with the information coming in today that we cannot apply our distressed points (all current June 2019 UY, in our case) to existing reservations.
We are blessed to have enough points each year to, for the most part; make the reservations we want for each year. Blessed, yes; but by design too. We, like many of you; paid for that privilege.
I have 181 points in limbo from chasing 3 different reservations since Easter (all now cancelled). They are still sitting (as of today) in my current UY (2019) that ends Sunday. I have made yet the 4th pushed reservation from our Easter trip for August 1-8 in the hopes of getting that trip in before school starts back here. I made it with 2020 points because I had them and the accommodations we wanted/were willing to settle for were available. However, and this is a huge "however;" we would have likely never used 2020 points to make that reservation had we known we could not later apply those distressed points to it, essentially replacing most of it with those points. This is essentially our F&G/Easter trip. In August. Through no fault of our own, nor Disney's and I get that.
So now as I understand it, I have to take the risk of losing that reservation and release it and make a new one in order to use those points. That seems grossly unfair to me and not in anybody's best interest to do it that way. I didn't need to involve MS here while they're so busy at all. I made my reservation, and simply planned to call them when things calm down sometime before our trip and simply have the intended points applied. Now, it seems, I have to become part of the kaos because the longer I wait, at least it seems to me; the more likely we are to lose that reservation during the release in the transition (ie-less rooms available and more people demanding them as time passes).
I'm not sure about y'all, but that whole process seems grossly unfair and equally unnecessary because I don't understand why that whole process/policy serves any greater good to the system. Anybody want to lend any insight as to what I am apparently missing here?
We are blessed to have enough points each year to, for the most part; make the reservations we want for each year. Blessed, yes; but by design too. We, like many of you; paid for that privilege.
I have 181 points in limbo from chasing 3 different reservations since Easter (all now cancelled). They are still sitting (as of today) in my current UY (2019) that ends Sunday. I have made yet the 4th pushed reservation from our Easter trip for August 1-8 in the hopes of getting that trip in before school starts back here. I made it with 2020 points because I had them and the accommodations we wanted/were willing to settle for were available. However, and this is a huge "however;" we would have likely never used 2020 points to make that reservation had we known we could not later apply those distressed points to it, essentially replacing most of it with those points. This is essentially our F&G/Easter trip. In August. Through no fault of our own, nor Disney's and I get that.
So now as I understand it, I have to take the risk of losing that reservation and release it and make a new one in order to use those points. That seems grossly unfair to me and not in anybody's best interest to do it that way. I didn't need to involve MS here while they're so busy at all. I made my reservation, and simply planned to call them when things calm down sometime before our trip and simply have the intended points applied. Now, it seems, I have to become part of the kaos because the longer I wait, at least it seems to me; the more likely we are to lose that reservation during the release in the transition (ie-less rooms available and more people demanding them as time passes).
I'm not sure about y'all, but that whole process seems grossly unfair and equally unnecessary because I don't understand why that whole process/policy serves any greater good to the system. Anybody want to lend any insight as to what I am apparently missing here?
Last edited: