<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: The T-Mobile Sidekick Data Outage: A Lesson in Social Media Crisis Management</title>
	<atom:link href="http://451heat.com/2009/11/10/the-t-mobile-sidekick-data-outage-a-lesson-in-social-media-crisis-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://451heat.com/2009/11/10/the-t-mobile-sidekick-data-outage-a-lesson-in-social-media-crisis-management/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Tue, 09 Mar 2010 04:11:09 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: admin</title>
		<link>http://451heat.com/2009/11/10/the-t-mobile-sidekick-data-outage-a-lesson-in-social-media-crisis-management/comment-page-1/#comment-197</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Tue, 17 Nov 2009 20:09:35 +0000</pubDate>
		<guid isPermaLink="false">http://451heat.com/?p=720#comment-197</guid>
		<description>That&#039;s too bad about your Blackberry, Vera. Hopefully T-Mobile is going to get it together with a social media crisis plan and better customer service after this mess. - Crissie</description>
		<content:encoded><![CDATA[<p>That&#8217;s too bad about your Blackberry, Vera. Hopefully T-Mobile is going to get it together with a social media crisis plan and better customer service after this mess. &#8211; Crissie</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 451 Heat » The T-Mobile Sidekick Data Outage: A Lesson in Social &#8230; &#124; Twitter Bootcamp Money Marketing Machine Secrets Skills &#124; Targeted Twitter Traffic</title>
		<link>http://451heat.com/2009/11/10/the-t-mobile-sidekick-data-outage-a-lesson-in-social-media-crisis-management/comment-page-1/#comment-156</link>
		<dc:creator>451 Heat » The T-Mobile Sidekick Data Outage: A Lesson in Social &#8230; &#124; Twitter Bootcamp Money Marketing Machine Secrets Skills &#124; Targeted Twitter Traffic</dc:creator>
		<pubDate>Wed, 11 Nov 2009 21:57:22 +0000</pubDate>
		<guid isPermaLink="false">http://451heat.com/?p=720#comment-156</guid>
		<description>[...] Read the original here: 451 Heat » The T-Mobile Sidekick Data Outage: A Lesson in Social &#8230; [...]</description>
		<content:encoded><![CDATA[<p>[...] Read the original here: 451 Heat » The T-Mobile Sidekick Data Outage: A Lesson in Social &#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vera Papisov</title>
		<link>http://451heat.com/2009/11/10/the-t-mobile-sidekick-data-outage-a-lesson-in-social-media-crisis-management/comment-page-1/#comment-152</link>
		<dc:creator>Vera Papisov</dc:creator>
		<pubDate>Tue, 10 Nov 2009 21:40:55 +0000</pubDate>
		<guid isPermaLink="false">http://451heat.com/?p=720#comment-152</guid>
		<description>I had a similar problem with my Blackberry. When T-Mobile promised me a replacement phone in August, under warranty, I ended up with a refurbished Blackberry that decided to wipe its memory clean every 17 days. It took me two months of begging, crying, and tweeting at T-Mobile in order for them to send me another one, but not before they insisted on having their Blackberry technicians check it out for four days. Two months of lost emails, lost contacts, calendar data - pretty much my entire digital life - was gone. After hearing about all the Sidekick problems, I&#039;m slightly offended that I wasn&#039;t offered a monetary apology or free data service. But, I think the way they handled my situation was better. A new, working phone is way more valuable than $100 and free data for a month. What can $100 even buy you these days? 2 cups of coffee? With that said, it&#039;s frustrating that it took T-Mobile so long to address my problems. They only did so after I sent them about 23 angry tweets involving iPhone threats. 23 tweets were more efficient than FIVE REAL TRIPS to the T-Mobile store? Very interesting.

BTW, I actually just covered this in my Principles and Practices of PR class last week. My professor told us that about  95% of organizations say having a plan for crisis communications is necessary, but only 50% actually have one.  Peer-to-peer communication (i.e. Twitter) is exponentially fast and has a huge impact on the ruckus that a crisis like this makes. I completely agree that they should&#039;ve been updating the situation on their media channels. Why keep quiet on your Twitter account activity when the problem is a trending topic? Beats me. In my opinion, they should have broadcasted the problem before the problem broadcasted itself in the form of angry customers. 

I just can&#039;t believe they weren&#039;t using their social media channels to ease customers. By cutting off communication like that, they made it so much worse! T-Mobile acted like a deer in headlights. I don&#039;t think they had a plan in place for social media crisis communications.</description>
		<content:encoded><![CDATA[<p>I had a similar problem with my Blackberry. When T-Mobile promised me a replacement phone in August, under warranty, I ended up with a refurbished Blackberry that decided to wipe its memory clean every 17 days. It took me two months of begging, crying, and tweeting at T-Mobile in order for them to send me another one, but not before they insisted on having their Blackberry technicians check it out for four days. Two months of lost emails, lost contacts, calendar data &#8211; pretty much my entire digital life &#8211; was gone. After hearing about all the Sidekick problems, I&#8217;m slightly offended that I wasn&#8217;t offered a monetary apology or free data service. But, I think the way they handled my situation was better. A new, working phone is way more valuable than $100 and free data for a month. What can $100 even buy you these days? 2 cups of coffee? With that said, it&#8217;s frustrating that it took T-Mobile so long to address my problems. They only did so after I sent them about 23 angry tweets involving iPhone threats. 23 tweets were more efficient than FIVE REAL TRIPS to the T-Mobile store? Very interesting.</p>
<p>BTW, I actually just covered this in my Principles and Practices of PR class last week. My professor told us that about  95% of organizations say having a plan for crisis communications is necessary, but only 50% actually have one.  Peer-to-peer communication (i.e. Twitter) is exponentially fast and has a huge impact on the ruckus that a crisis like this makes. I completely agree that they should&#8217;ve been updating the situation on their media channels. Why keep quiet on your Twitter account activity when the problem is a trending topic? Beats me. In my opinion, they should have broadcasted the problem before the problem broadcasted itself in the form of angry customers. </p>
<p>I just can&#8217;t believe they weren&#8217;t using their social media channels to ease customers. By cutting off communication like that, they made it so much worse! T-Mobile acted like a deer in headlights. I don&#8217;t think they had a plan in place for social media crisis communications.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AJ Gerritson</title>
		<link>http://451heat.com/2009/11/10/the-t-mobile-sidekick-data-outage-a-lesson-in-social-media-crisis-management/comment-page-1/#comment-150</link>
		<dc:creator>AJ Gerritson</dc:creator>
		<pubDate>Tue, 10 Nov 2009 20:03:37 +0000</pubDate>
		<guid isPermaLink="false">http://451heat.com/?p=720#comment-150</guid>
		<description>This is a tough call. I wonder if they (1) had a plan in place for social media crisis communications, and (2) if they did, how much they stuck to it?</description>
		<content:encoded><![CDATA[<p>This is a tough call. I wonder if they (1) had a plan in place for social media crisis communications, and (2) if they did, how much they stuck to it?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
