<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Meandering Ones &#187; Mexico</title>
	<atom:link href="http://meanderingones.com/tag/mexico/feed/" rel="self" type="application/rss+xml" />
	<link>http://meanderingones.com</link>
	<description>Go do something cool &#124; In DC Virginia Maryland and all over</description>
	<lastBuildDate>Thu, 17 Jun 2010 00:28:18 +0000</lastBuildDate>
	
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Cabo &#8211; The Day Before</title>
		<link>http://meanderingones.com/2008/03/16/cabo-the-day-before/</link>
		<comments>http://meanderingones.com/2008/03/16/cabo-the-day-before/#comments</comments>
		<pubDate>Sun, 16 Mar 2008 09:49:06 +0000</pubDate>
		<dc:creator>SQ</dc:creator>
				<category><![CDATA[Flight]]></category>
		<category><![CDATA[Los Cabos]]></category>
		<category><![CDATA[Mexico]]></category>

		<guid isPermaLink="false">http://meanderingones.com/2008/03/16/cabo-the-day-before/</guid>
		<description><![CDATA[So I spent most of the day at one point or another trying to get our seats locked up for the flights. You&#8217;d think this would have been done before now &#8211; I purchased the tickets about eight months ago, so things ought to be pretty locked up at this point. No. Our friends at [...]]]></description>
			<content:encoded><![CDATA[<p>So I spent most of the day at one point or another trying to get our seats locked up for the flights. You&#8217;d think this would have been done before now &#8211; I purchased the tickets about eight months ago, so things ought to be pretty locked up at this point. No. Our friends at Orbitz, who will readily pass the blame to the fact that they are working with the airlines to ensure seats are committed, seemed to have the ability to procure seat reservations on an ad hoc, purely random basis. For example, I had reserved three seats in the 12th row of the American 737 we&#8217;re flying on, and Willy and Syd&#8217;s spots were left intact, mine for some odd reason moved about three rows forward. Can you imagine being the person who gets stuck next to a wife and her child, all by yourself, while that woman&#8217;s husband is stuck in another row after reserving your seat? Doesn&#8217;t sound like a position in which I&#8217;d want to be if I were looking at this from the angle of a business traveler rather than a husband and father. If this in fact isn&#8217;t an Orbitz issue, the airlines need to get it together. If it is Orbitz, they&#8217;re just plain stupid for making their customers feel that reserving their seats is any different than running around pretending they&#8217;re the next British monarch.</p>
<p>Having been promised &#8211; in an online way, albeit &#8211; that the seats were once again reserved, only to find they weren&#8217;t, I wound up calling Orbitz while we were traveling to dinner. After the usual but still annoying 10 minute wait to get a customer service rep on the phone that most likely uses the exact same web interface customers use to assist, a surprisingly American (and southern sounding) woman took my call. After explaining the situation, she attempted unsuccessfully to lock in any seat changes, the said, &#8220;Hold on. I am going to try something else.&#8221;</p>
<p>Once she returned to the phone to inform me it didn&#8217;t work, I asked her to recall my itinerary to tell me what we had. What came next was shock and horror: not just on the other end of the line but on mine as well. &#8220;Did you just cancel your flights, sir?&#8221; I responded, &#8220;How could I? I am in the car, on the phone with you.&#8221;</p>
<p>A healthy pause followed, and several passive-aggresive urges hit me all at once. &#8220;I have no idea what happened, but someone has canceled your reservations. I am going to need to forward you to a supervisor.&#8221; Knowing there were no more than two or three remaining seats on all our flights to begin, and feeling pretty confident that the customer service agent and flight cancelation specialist were one in the same, I reluctantly held the line.</p>
<p>Quick theory: if you&#8217;re in this business and occasionally commit such a strong party foul, wouldn&#8217;t it be a good idea to make sure there are &#8220;holy crap&#8221; supervisors just waiting by the red phone to take the call? Here we are, hours from our flight, and I am flopping over mountains with a mobile phone that has a 50/50 shot at even surviving the call. Wait time to talk to the supervisor with zero flights: 10 minutes.</p>
<p>Claudia (Employee ID MAU &#8211; by the way, how do you get a three letter code for an employee ID? Can you imagine Bob Segar singing the song &#8220;Feel Like A Bunch of Letters&#8221;?) was our supervisor agent, and in the customary practice of companies everywhere, apologized for the situation without taking any responsible on behalf of Orbitz for the relative terror thrown our way. Reminds me of Eliot Spitzer resigning&#8230; sorry you&#8217;ve been let down, now I am going to resign and return to private life for doing nothing that I plan to discuss outside my apartment.</p>
<p>After Claudia told us she was going to handle the situation with literally no specifics, I asked for her name and ID one last time, thinking I could trust that there was an understanding between us regarding the severity of having no tickets the night before a major vacation. As far as her commitment goes, I am convinced there was, but I&#8217;m not so sure there&#8217;s an understanding regarding the time expectation for representatives in this situation. When someone has lost seats for a flight that begins in 12 hours, they&#8217;re thinking 20 minutes is a rough estimate for their remaining non-communicated sanity.</p>
<p>When 40 minutes went by, I called Orbitz back thinking I&#8217;d be able transfer right to agent MAU. No such luck, and no way to do that. Wow. Now I&#8217;m really blown away. Supervisors handle escalated issues and represent the embodiment of the solution for customers with challenges, and this huge operation doesn&#8217;t even get that. This expectation is not excessive: this is how we did it in every customer service environment I&#8217;ve been around, whether based on in-person, phone, email, or IM contact.</p>
<p>I did get another supervisor &#8211; one that was connected to me via a highly latent tin can / string communications system that sounded like it terminated somewhere in Malaysia. It always makes me chuckle when comms systems are so bad that the callers find themselves waiting 5 seconds to hear the other participant respond. After some on and off chatting with this supervisor, she determined that Claudia was still working the issue and would call me within an hour. I&#8217;m sure she was able to figure that out because the sum total of supervisory manpower at Orbitz amounted to three frustrated women sharing a desk and two rotary phones in a cabbage patch somewhere (not intended to offend, rather to point out the ridiculous nature of phonebound customer service here now &#8211; of course our sagging dollar will at least give these goofballs a chance to ring their call centers back to America, particularly to Detroit based on newly available workforce).</p>
<p>We finally returned home and I got the call. Though I could barely hear her, Claudia seemed to essentially say that everything Orbitz had lost and I had spent the last three hours attempting to retrieve had in fact been re-reserved. Good thing: when I tried to check alternatives on Kayak, I found one flight out a day and a half later with a 12 hour layover through the night at LAX &#8211; grouch material for sure.</p>
]]></content:encoded>
			<wfw:commentRss>http://meanderingones.com/2008/03/16/cabo-the-day-before/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

