Skip to main content

I Am Going To Boycott Travelocity, And Not Because I Hate The Gnome

I do hate the annoying gnome, but that's not the reason.
We (my wife and I) just had a very strange and unpleasant experience with online booking through Travelocity. It started in a pretty normal way—on Friday she booked a flight for her father, who doesn't have a computer, so she usually does it for him, I printed the e-ticket, put it into an envelope, mailed it to Cincinnati, where he resides, and we went on with our life.
That wasn't it, though. Next day, in the evening, my cellphone starts ringing, I cross the room to pick it up, it stops. Missed call. From... let me see... a person named "0050". Not that I know anybody by that name, and no voicemail message left. Whatever. Back to dinner.
Three hours later I go to the computer to check email, to find three messages from memberservices@travelocity.com
First message - at 6PM (about 24 hours after original booking):
1."...For the protection of our valued customers, all reservations are subject to review by our Revenue Protection Department, which requires the actual credit cardholder to contact our agents for additional information or verbal authorization...Your reservation is subject to cancellation..."
Second and third messages - both at exactly 7:51PM:
2."...We are unable to complete the processing of the reservation you made on our system, until we can obtain some additional information from you..."
3."...Thank you for booking your travel reservations with Travelocity.com...Our Revenue Protection Department previously had either contacted you by phone or emailed you requesting that you contact us. Unfortunately we have not heard from you and we have canceled your reservation due to lack of verifiable information..."
Apparently, the call from that 0050 gnome was not the one to miss.
I called Travelocity, and got through the maze of menus, and was put on hold and demanded explanation from someone with undecipherable English, and was transferred to another someone, whose first words to me were (I kid you not) "Who is this?" By that time I was not even yelling, I was more like hissing, but at no avail, cancelled reservations can not be reinstated, and so on.
I am just wondering at what point the company which use to have a good reputation stops giving a shit about it and turns the business to it's Revenue Protection Service.
And do they really expect me to be glued to the computer with the phone in my hand on Saturday night, or my reservation will be cancelled 24 hours after it was made, my dinner will be ruined, and my wife's weekend will be spent looking for another ticket through another travel site?
On the brighter side—at least they let us know that the reservation was cancelled. I wouldn't be surprised if they hadn't.
I hate gnomes.

P.S. On Monday, two days after they cancelled this reservation, they charge my credit card for it. I had to call them and yell at them, and I also called my credit card and disputed the charge just in case. Somehow the words that come to mind when I see the gnome are not of a civilized nature.

Popular posts from this blog

{position:fixed} in iOS 6

I stumbled upon this oddity when upgrading to iOS 6 while working on a mobile advertising project, and it took me a better part of the day to figure out what is going on: all of a sudden an element {position:fixed} stopped working in a correct manner (which is staying put, while the page is scrolling), and started "sticking" to the scrolling page, moving out of the viewport, and then just "jumping" back to the correct location after the scrolling was finished.If you scroll this page , you will see it—hint: that's the one labeled "broken"—assuming that you have a correct device/browser combination. Mine was iPhone4 and iOS 6.0 (6.0.1-6.1.3 behaves just the same). On the original page, where I first encountered the problem, all of my elements were created dynamically using JavaScript, but at the end of the day (literally) it become clear, that the glitch is in the iOS 6 CSS implementation.Here is what happens: if you have an element {position:fixed} whic

May 1st Reboot 2016

My main site gets a facelift (about half-a-decade overdue). Due to a chronic caching issues with iPage, I have to model everything on CodePen , and then FTP files to iPage, where, for some mysterious reason, html gets updated instantly, but CSS and Javascripts marinate somewhere for at least half an hour, before starting to render, which makes it impossible to model anything in real time. Annoying. Oh, well. At least I finally got to re-doing the site. I still do not have a concept for the galleries, though, and a main navigation menu is really primitive, but the new site is HTML5, CSS3 and what not, and I am not ashamed to refer people to it anymore. Yay. P.S. Resolved the cache issue with .htaccess file: FileETag None Header unset ETag Header set Cache-Control "max-age=0, no-cache, no-store, must-revalidate" Header set Pragma "no-cache" Header set Expires "Wed, 11 Jan 1984 05:00:00 GMT"  everything now works a lot livelier. P.P.S. Why is Blo

I Am Starting To Worry...

...generally, when the amount of money in my savings exceeds a certain number (and that's not a large number), mainly, because I expect various unpleasant events to take place. Usually, the car breaks down. Sometimes I hit something, but sometimes it breaks by itself just as well. This Tuesday I came to work, parked my Jeep, spent 9 hours at the office, went back to my Jeep and turned the ignition key. Nothing. The lights are on, though, radio works, too - I have power. So it's a fuse, or starter. I checked the fuses (found two which claimed responsibility for the starter operation), one was all right, the other one I couldn't pull out without pliers, so I decided, that it's all right, too. It looked nice from the outside. So I called AAA and asked for the tow to the dealership. The truck came in about half an hour and the driver checked my battery, confirmed that it's not it, and offered me to start my Jeep with a help of two seemingly undocumented individuals, who