<?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>ThruIT &#187; social networking</title>
	<atom:link href="http://thruit.com/tag/social-networking/feed/" rel="self" type="application/rss+xml" />
	<link>http://thruit.com</link>
	<description></description>
	<lastBuildDate>Tue, 02 Feb 2010 16:39:47 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Update: AT&amp;T Contacts Me On Twitter!</title>
		<link>http://thruit.com/2009/11/att-followup/</link>
		<comments>http://thruit.com/2009/11/att-followup/#comments</comments>
		<pubDate>Thu, 12 Nov 2009 01:33:57 +0000</pubDate>
		<dc:creator>Will Kievit</dc:creator>
				<category><![CDATA[Blips]]></category>
		<category><![CDATA[at&t]]></category>
		<category><![CDATA[caller id]]></category>
		<category><![CDATA[connecticut]]></category>
		<category><![CDATA[connection]]></category>
		<category><![CDATA[iPhone]]></category>
		<category><![CDATA[issues]]></category>
		<category><![CDATA[network]]></category>
		<category><![CDATA[proactive]]></category>
		<category><![CDATA[routing]]></category>
		<category><![CDATA[social networking]]></category>
		<category><![CDATA[stamford]]></category>
		<category><![CDATA[twitter]]></category>
		<category><![CDATA[wrong number]]></category>

		<guid isPermaLink="false">http://thruit.com/?p=337</guid>
		<description><![CDATA[<img class="alignleft size-full wp-image-437" title="at&#38;t twitter" src="http://thruit.com/wp-content/uploads/2009/11/att-twitter.JPG" alt="at&#38;t twitter" width="192" height="155" />A couple of nights ago, an AT&#38;T Wireless manager contacted me on twitter. Apparently, AT&#38;T caught wind of my <a href="http://thruit.com/2009/11/att-connecting-callers-to-wrong-person/" target="_blank">blog post</a> where I talked about the issue I was having, and using their new social media initiative be proactive and reach out to me. When <a href="http://twitter.com/attjason" target="_blank">@ATTJason</a> contacted me on twitter this evening,  I was completely skeptical of this random twitter handle, and on defense, but I went to <a href="http://www.att.com/gen/press-room?pid=5000" target="_blank">AT&#38;T's website</a> and determined <a href="http://twitter.com/attcustomercare" target="_blank">@ATTCustomerCare</a> was a legitimate handle, which then references @ATTJason as legitimate. This seems to be one thing that AT&#38;T needs to be careful with, and one of Twitter's "Verified Account" badges would probably help out. With all of the phishing schemes out there it is important that AT&#38;T presents itself well.]]></description>
			<content:encoded><![CDATA[<p><img class="alignleft size-full wp-image-437" title="at&amp;t twitter" src="http://thruit.com/wp-content/uploads/2009/11/att-twitter.JPG" alt="at&amp;t twitter" width="192" height="155" />A couple of nights ago, an AT&amp;T Wireless manager contacted me on twitter. Apparently, AT&amp;T caught wind of my <a href="http://thruit.com/2009/11/att-connecting-callers-to-wrong-person/" target="_blank">blog post</a> where I talked about the issue I was having, and using their new social media initiative be proactive and reach out to me. When <a href="http://twitter.com/attjason" target="_blank">@ATTJason</a> contacted me on twitter this evening,  I was completely skeptical of this random twitter handle, and on defense, but I went to <a href="http://www.att.com/gen/press-room?pid=5000" target="_blank">AT&amp;T&#8217;s website</a> and determined <a href="http://twitter.com/attcustomercare" target="_blank">@ATTCustomerCare</a> was a legitimate handle, which then references @ATTJason as legitimate. This seems to be one thing that AT&amp;T needs to be careful with, and one of Twitter&#8217;s &#8220;Verified Account&#8221; badges would probably help out. With all of the phishing schemes out there it is important that AT&amp;T presents itself well.</p>
<p>Long story short, AT&amp;T followed up with me finally, saying that the issue seemed to have been resolved on the network end and wanted to make sure that the issue was indeed fixed on my end. I confirmed it had. One more satisfied customer. Love that brands are taking such a proactive approach. Well I guess they have to though, the power of social networking is such that a sour customer could do a lot of damage to a company, but reaching out and trying to fix their issue instead helps.</p>
<p>Have any of you had an experience like this with AT&amp;T or any other companies? Disagree with my praise of the carrier? Let us know. Voice your opinion in a comment below!</p>
]]></content:encoded>
			<wfw:commentRss>http://thruit.com/2009/11/att-followup/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
