Originally Posted by
tcook052
Yes Wally and while I said impossible I should've instead used impactical and cost prohibitive as IMHO it would be far too much IT trouble to catch relatively few nested tickets.
Again, AC can't even get a new workable res. program as seen in the whole Polaris debacle so expecting it to adopt one with this kind of technology is unrealistic IMHO.
That is a very different statement, and one that I think we could all agree on.
Detecting nested tickets is easy from a tech perspective, especially if people use their FF #. You just compare the dates, destination and rules of existing booking to the new one. If there is a booking that requires the person be in FRA for a week, and they make a booking that has them departing FRA within that week you flag the booking for manual review by an agent and have the agent contact the individual to cancel the ticket if it is deemed abusive (ie. someone returning to SEA to avoid going back to YVR could still be viewed as nested). Assuming decent db indexing (on names/FF#s), it's not even overly expensive from a computation perspective because you are only comparing a flight with a very limit number of other flights.
Now implementing that on an antiqued system is expensive; but "We handle it afterwards because prevention is impossible" is a very different argument from "We handle it afterwards because we aren't willing to spend the money to prevent it". We choose not to mitigate the problem is different from we couldn't mitigate the problem.