<?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: 3 Ways to Not Suck at Chat Support</title>
	<atom:link href="http://grasshopper.com/blog/company/2010/03/05/3-ways-to-not-suck-at-chat-support/feed/" rel="self" type="application/rss+xml" />
	<link>http://grasshopper.com/blog/company/2010/03/05/3-ways-to-not-suck-at-chat-support/</link>
	<description>Sound Professional and Stay Connected. That&#039;s our core purpose and the company blog is dedicated to helping you do just that. Get information on the Grasshopper virtual phone system and find additional tips &#38; tricks for small businesses.</description>
	<lastBuildDate>Sat, 28 Aug 2010 18:51:14 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Darren Rosebrugh</title>
		<link>http://grasshopper.com/blog/company/2010/03/05/3-ways-to-not-suck-at-chat-support/comment-page-1/#comment-456</link>
		<dc:creator>Darren Rosebrugh</dc:creator>
		<pubDate>Fri, 05 Mar 2010 20:53:32 +0000</pubDate>
		<guid isPermaLink="false">http://grasshopper.com/blog/company/?p=1420#comment-456</guid>
		<description>Great points Larry. I think screen share would be great, as would being able to paste screenshots for the person to view while you&#039;re chatting.</description>
		<content:encoded><![CDATA[<p>Great points Larry. I think screen share would be great, as would being able to paste screenshots for the person to view while you&#8217;re chatting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Larry Lisser</title>
		<link>http://grasshopper.com/blog/company/2010/03/05/3-ways-to-not-suck-at-chat-support/comment-page-1/#comment-455</link>
		<dc:creator>Larry Lisser</dc:creator>
		<pubDate>Fri, 05 Mar 2010 18:01:46 +0000</pubDate>
		<guid isPermaLink="false">http://grasshopper.com/blog/company/?p=1420#comment-455</guid>
		<description>Good topic. It&#039;s a shame actually that a technology as innovative as chat - when it first came out - has not be optimized as a customer service channel. Your points are all valid, but while it is very simple to integrate click to call into a chat platform, it is rarely done. Primarily because for many companies chat is a way to reduce calls.

That said, the button does not have to be there really until the agent decides its time. Then simply push a link at the customer - at predetermined inflection points - and you&#039;d have a happier customer and likely a resolved issue (or sale).

Another good element to add would be instant screen share. Again, it could be done as a push of a link whereby the agent would then to sharing his/her screen with the customer - and controlling the discussion by adding visual context to it. Again, not difficult to integrate but we don&#039;t see it often.

Perhaps your most salient point is about multiple chats at once as this is often what makes it a disjointed and slow communication.</description>
		<content:encoded><![CDATA[<p>Good topic. It&#8217;s a shame actually that a technology as innovative as chat &#8211; when it first came out &#8211; has not be optimized as a customer service channel. Your points are all valid, but while it is very simple to integrate click to call into a chat platform, it is rarely done. Primarily because for many companies chat is a way to reduce calls.</p>
<p>That said, the button does not have to be there really until the agent decides its time. Then simply push a link at the customer &#8211; at predetermined inflection points &#8211; and you&#8217;d have a happier customer and likely a resolved issue (or sale).</p>
<p>Another good element to add would be instant screen share. Again, it could be done as a push of a link whereby the agent would then to sharing his/her screen with the customer &#8211; and controlling the discussion by adding visual context to it. Again, not difficult to integrate but we don&#8217;t see it often.</p>
<p>Perhaps your most salient point is about multiple chats at once as this is often what makes it a disjointed and slow communication.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
