Southwest aggressive auto-cancellation for non-overlapping flights
Couple days ago (Monday, Feb 11) I booked two one-ways (identical routes) for Feb 17 and Feb 18. Wasn't sure yet which date I wanted to fly, and I saw that availability was drying up, so hit the trigger on both to cancel one by the end of this week. Figured I would be OK with the auto-cancellation sweeps since these were on different dates, no overlap, and both theoretically possible (both departing AM, could fly back in PM on another carrier and take the next day's flight back out). Also after reading others' experiences on the forum, just to be extra safe, I left my RR# and KTN off the first reservation.
Well last night at ~2 am I got an email saying that the Feb 18 flight had been cancelled -- without explanation, but presumably caught by the duplicate sweeper. I just confirmed this afternoon that I actually need the Feb 18 flight, so called up Southwest and asked for Feb 18 to be reinstated. I half expected to be scolded by the agent for booking on consecutive days, but instead, after "investigating" why it was cancelled for 10 mins on hold she said she found the "duplicate" flagged by the computer on the 17th (even without my RR#), but was very puzzled and apologized for the auto-cancellation, saying it shouldn't have happened since they weren't overlapping or impossible... and could plausibly have been day trips (or for a mileage run). But, given that the computer didn't like it, she said if she reinstated the 18th without cancelling 17th, it would likely be cancelled again tonight by the sweeper. Lesson learned... Southwest is getting more aggressive with auto-cancellations of reservations on consecutive days (regardless of whether it's attached to your RR# or not). |
Originally Posted by BobtheBuilder66
(Post 30774220)
Couple days ago (Monday, Feb 11) I booked two one-ways (identical routes) for Feb 17 and Feb 18. Wasn't sure yet which date I wanted to fly, and I saw that availability was drying up, so hit the trigger on both to cancel one by the end of this week. Figured I would be OK with the auto-cancellation sweeps since these were on different dates, no overlap, and both theoretically possible (both departing AM, could fly back in PM on another carrier and take the next day's flight back out). Also after reading others' experiences on the forum, just to be extra safe, I left my RR# and KTN off the first reservation.
Well last night at ~2 am I got an email saying that the Feb 18 flight had been cancelled -- without explanation, but presumably caught by the duplicate sweeper. I just confirmed this afternoon that I actually need the Feb 18 flight, so called up Southwest and asked for Feb 18 to be reinstated. I half expected to be scolded by the agent for booking on consecutive days, but instead, after "investigating" why it was cancelled for 10 mins on hold she said she found the "duplicate" flagged by the computer on the 17th (even without my RR#), but was very puzzled and apologized for the auto-cancellation, saying it shouldn't have happened since they weren't overlapping or impossible... and could plausibly have been day trips (or for a mileage run). But, given that the computer didn't like it, she said if she reinstated the 18th without cancelling 17th, it would likely be cancelled again tonight by the sweeper. Lesson learned... Southwest is getting more aggressive with auto-cancellations of reservations on consecutive days (regardless of whether it's attached to your RR# or not). That's a pretty serious IT issue. |
Or by aggressive design. Lets face it, it flagged exactly for the reason the OP was trying to do (and most of us want to do) in lieu of the tiny percentage actually doing "half" day trips or a mileage run. I don't like it but sounds like a pretty robust IT issue!
|
Not buying that this is CancelBot's doing, sorry. Something else is up, IMO
|
Originally Posted by rickg523
(Post 30774374)
I'm sorry, did you just say that WN is currently incapable of allowing you to book those two flights or an itinerary like that? Even with an agent?
That's a pretty serious IT issue. |
It looks like a bug to me--especially since they're willing to reinstate. It'd be weird for them to crack down on this scenario for some people and not others. I have currently have duplicate flights booked for consecutive days and haven't gotten a cancellation yet.
|
Originally Posted by synergistic
(Post 30775407)
When I was booking for mileage runs, WN was willing and able to reinstate my flights - but they were 100% unable to prevent them from being autocanceled. Numerous agents offered to flag them to protect them, but they were always canceled again in a night or two. Was really weird but they were always wiling to reinstate, so...
|
Originally Posted by kennycrudup
(Post 30774643)
Not buying that this is CancelBot's doing, sorry. Something else is up, IMO
It is totally logical/legitimate that many folks fly the same route two days in a row. |
Originally Posted by chuckworth
(Post 30776073)
I would agree with the above. On several recent occasions (within the past month), i’ve booked flights to the same destination departing consecutive days without issue. No auto-cancellations. Even without a return booked prior to the second flight. It is totally logical/legitimate that many folks fly the same route two days in a row. |
Wondering aloud whether booking a "return" flight in between the two one-ways would cause the auto-cancel to leave both of them alone.
|
Originally Posted by mstrbldr
(Post 30825733)
Wondering aloud whether booking a "return" flight in between the two one-ways would cause the auto-cancel to leave both of them alone.
I think that, if there is enough time for a return flight in between the others it wouldn't be necessary to actually book it. |
Originally Posted by ursine1
(Post 30825982)
I think that, if there is enough time for a return flight in between the others it wouldn't be necessary to actually book it.
|
For all the speculation here, it seems to me that the algorithm and the practice have changed a bit over time. Nobody here can predict what it might be tomorrow and what exactly the triggers are. One possible explanation of variance is that the algorithm looks at the loads and does not act until the seats are likely to become needed. If that is the case, the opinions here are even more speculative because nobody knows what the load on a given flight will be a week from now.
The solution if one has to purchase tickets which may push the envelope a bit is to call in and assure that WN is satisfied and has made PNR notes to the effect that the tickets are not speculative. |
Originally Posted by Often1
(Post 30827204)
The solution if one has to purchase tickets which may push the envelope a bit is to call in and assure that WN is satisfied and has made PNR notes to the effect that the tickets are not speculative.
|
Originally Posted by Often1
(Post 30827204)
The solution if one has to purchase tickets which may push the envelope a bit is to call in and assure that WN is satisfied and has made PNR notes to the effect that the tickets are not speculative.
It seems it may be purposeful and if those people who are having the issues have in the past made a habit of double booking then cancelling, Southwest may be tracking that. |
All times are GMT -6. The time now is 8:21 am. |
This site is owned, operated, and maintained by MH Sub I, LLC dba Internet Brands. Copyright © 2024 MH Sub I, LLC dba Internet Brands. All rights reserved. Designated trademarks are the property of their respective owners.