<?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: 5 Ways to Manage Twitter at Scale</title>
	<atom:link href="http://blog.20dbs.com/5-ways-to-manage-twitter-at-scale/2010/02/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.20dbs.com/5-ways-to-manage-twitter-at-scale/2010/02/</link>
	<description>Blogging about Twitter and Social Media</description>
	<lastBuildDate>Mon, 15 Mar 2010 21:26:56 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Shashib</title>
		<link>http://blog.20dbs.com/5-ways-to-manage-twitter-at-scale/2010/02/comment-page-1/#comment-682</link>
		<dc:creator>Shashib</dc:creator>
		<pubDate>Fri, 05 Mar 2010 18:13:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.20dbs.com/?p=1346#comment-682</guid>
		<description>Hi Adam,&lt;br&gt;&lt;br&gt;At Network Solutions we are doing the business unit / audience approach @netsolcares (support) @nsoffers (product offers) @nscareers (experiment) @growsmartbiz ( small Business resources) @wgbiz (women entrepreneurs) . Your post has got me thinking on a plan to do both one and two above. Thanks.&lt;br&gt;&lt;br&gt;Shashi</description>
		<content:encoded><![CDATA[<p>Hi Adam,</p>
<p>At Network Solutions we are doing the business unit / audience approach @netsolcares (support) @nsoffers (product offers) @nscareers (experiment) @growsmartbiz ( small Business resources) @wgbiz (women entrepreneurs) . Your post has got me thinking on a plan to do both one and two above. Thanks.</p>
<p>Shashi</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce Wilson</title>
		<link>http://blog.20dbs.com/5-ways-to-manage-twitter-at-scale/2010/02/comment-page-1/#comment-680</link>
		<dc:creator>Bruce Wilson</dc:creator>
		<pubDate>Fri, 26 Feb 2010 21:17:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.20dbs.com/?p=1346#comment-680</guid>
		<description>Thanks Eric, and you&#039;re welcome Adam. Good to be able to ponder these things as a group! Been thinking about this some more: just like social media &quot;works&quot; when there&#039;s a real person behind the tweets, one on one with &quot;a real [named] person&quot; works for customer service. By the way, now I&#039;m totally looking forward to using AT&amp;T&#039;s Twitter help rather than calling when I need iPhone-related assistance! Seems not only more time efficient, but like I&#039;ll be dealing with a fellow geek. On the other hand, if you glance at the AT&amp;T twitter list - &lt;a href=&quot;http://twitter.com/ATTCustomerCare/attcareteam&quot; rel=&quot;nofollow&quot;&gt;http://twitter.com/ATTCustomerCare/attcareteam&lt;/a&gt; - the agents seem to be reusing some of the same tweets. Doubtless their workflow includes pre-written responses like any other specialized customer service environment. Hard to imagine having the job of converting the 50 (100? 500??) most common customer service responses into 140 character Tweets, though!</description>
		<content:encoded><![CDATA[<p>Thanks Eric, and you&#39;re welcome Adam. Good to be able to ponder these things as a group! Been thinking about this some more: just like social media &#8220;works&#8221; when there&#39;s a real person behind the tweets, one on one with &#8220;a real [named] person&#8221; works for customer service. By the way, now I&#39;m totally looking forward to using AT&#038;T&#39;s Twitter help rather than calling when I need iPhone-related assistance! Seems not only more time efficient, but like I&#39;ll be dealing with a fellow geek. On the other hand, if you glance at the AT&#038;T twitter list &#8211; <a href="http://twitter.com/ATTCustomerCare/attcareteam" rel="nofollow">http://twitter.com/ATTCustomerCare/attcareteam</a> &#8211; the agents seem to be reusing some of the same tweets. Doubtless their workflow includes pre-written responses like any other specialized customer service environment. Hard to imagine having the job of converting the 50 (100? 500??) most common customer service responses into 140 character Tweets, though!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Schoenfeld</title>
		<link>http://blog.20dbs.com/5-ways-to-manage-twitter-at-scale/2010/02/comment-page-1/#comment-679</link>
		<dc:creator>Adam Schoenfeld</dc:creator>
		<pubDate>Fri, 26 Feb 2010 20:48:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.20dbs.com/?p=1346#comment-679</guid>
		<description>Bruce and Eric, thanks for the comments! I think this trend makes a lot of sense for big companies. It helps keep the signal to noise ratio higher for a targeted audience.&lt;br&gt;But as you said, it will take some thought on how to manage the workflow within the organization.</description>
		<content:encoded><![CDATA[<p>Bruce and Eric, thanks for the comments! I think this trend makes a lot of sense for big companies. It helps keep the signal to noise ratio higher for a targeted audience.<br />But as you said, it will take some thought on how to manage the workflow within the organization.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Boggs</title>
		<link>http://blog.20dbs.com/5-ways-to-manage-twitter-at-scale/2010/02/comment-page-1/#comment-678</link>
		<dc:creator>Eric Boggs</dc:creator>
		<pubDate>Fri, 26 Feb 2010 18:59:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.20dbs.com/?p=1346#comment-678</guid>
		<description>Agreed, Bruce.  Interesting that there seems to be a shift away from a one-account-to-many social approach to a many-accounts-to-many approach...</description>
		<content:encoded><![CDATA[<p>Agreed, Bruce.  Interesting that there seems to be a shift away from a one-account-to-many social approach to a many-accounts-to-many approach&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce Wilson</title>
		<link>http://blog.20dbs.com/5-ways-to-manage-twitter-at-scale/2010/02/comment-page-1/#comment-677</link>
		<dc:creator>Bruce Wilson</dc:creator>
		<pubDate>Fri, 26 Feb 2010 18:28:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.20dbs.com/?p=1346#comment-677</guid>
		<description>INNteresting - thanks Adam for running this down for us. The emphasis on massing Twitter accounts rather than sharing the same account (CoTweet style) makes sense, although then there still must be additional layers of admin to assign customer responses to different agents aggregate reporting on all of the different accounts. I wonder what the workflow architecture looks like for BestBuy in particular, to incentivize agents to work independently while keeping any given customer from getting 2,000+ replies.</description>
		<content:encoded><![CDATA[<p>INNteresting &#8211; thanks Adam for running this down for us. The emphasis on massing Twitter accounts rather than sharing the same account (CoTweet style) makes sense, although then there still must be additional layers of admin to assign customer responses to different agents aggregate reporting on all of the different accounts. I wonder what the workflow architecture looks like for BestBuy in particular, to incentivize agents to work independently while keeping any given customer from getting 2,000+ replies.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
