<?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: Why is Google hanging up on its customers?</title>
	<atom:link href="http://socialmediainfluence.com/2010/01/13/why-is-google-hanging-up-on-its-customers-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://socialmediainfluence.com/2010/01/13/why-is-google-hanging-up-on-its-customers-2/</link>
	<description>Social Media Intelligence, News &#38; Analysis</description>
	<lastBuildDate>Sat, 19 May 2012 10:08:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: Social Media Influence: Social Media News &#38; Intelligence &#187; Google learns painful lesson in online customer care</title>
		<link>http://socialmediainfluence.com/2010/01/13/why-is-google-hanging-up-on-its-customers-2/comment-page-1/#comment-9198</link>
		<dc:creator>Social Media Influence: Social Media News &#38; Intelligence &#187; Google learns painful lesson in online customer care</dc:creator>
		<pubDate>Mon, 17 May 2010 14:52:22 +0000</pubDate>
		<guid isPermaLink="false">http://socialmediainfluence.com/?p=570#comment-9198</guid>
		<description>[...] we know it best. It forgot one thing: it doesn&#8217;t know mobile customers at all, triggering a nasty customer uproar that nearly sunk the Nexus One at launch. The saga didn&#8217;t end there. Late on Friday, Google [...]</description>
		<content:encoded><![CDATA[<p>[...] we know it best. It forgot one thing: it doesn&#8217;t know mobile customers at all, triggering a nasty customer uproar that nearly sunk the Nexus One at launch. The saga didn&#8217;t end there. Late on Friday, Google [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
