<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.5" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Make your customers happier with this simple tip</title>
	<link>http://www.carsonified.com/misc/customer-service-tips</link>
	<description>We love the web!</description>
	<pubDate>Thu, 28 Aug 2008 01:44:28 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: A Million Thoughts &#187; Blog Archive &#187; About this blog (3): Decisions</title>
		<link>http://www.carsonified.com/misc/customer-service-tips#comment-14863</link>
		<pubDate>Fri, 27 Jul 2007 20:49:09 +0000</pubDate>
		<guid>http://www.carsonified.com/misc/customer-service-tips#comment-14863</guid>
					<description>[...] I started looking at other blogs and noticed there are many different ways to design an url. Here are a few (random) examples:  /blog/2007/02/16/Recreational-SVG /yyyy/mm/dd/Title-without-Spaces /2007/03/web-20-borrel-een-succes-open-coffee-meet-coming-up/ /yyyy/mm/title-without-spaces /amigo/customer-service-tips /tagname/titile-with-spaces /svn/posts/302-preview-5-highrise-tasks /id-of-post-plus-title-without-spaces [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] I started looking at other blogs and noticed there are many different ways to design an url. Here are a few (random) examples:  /blog/2007/02/16/Recreational-SVG /yyyy/mm/dd/Title-without-Spaces /2007/03/web-20-borrel-een-succes-open-coffee-meet-coming-up/ /yyyy/mm/title-without-spaces /amigo/customer-service-tips /tagname/titile-with-spaces /svn/posts/302-preview-5-highrise-tasks /id-of-post-plus-title-without-spaces [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: ziggy</title>
		<link>http://www.carsonified.com/misc/customer-service-tips#comment-6626</link>
		<pubDate>Tue, 08 May 2007 06:22:52 +0000</pubDate>
		<guid>http://www.carsonified.com/misc/customer-service-tips#comment-6626</guid>
					<description>&#62;&#62;the customer is always right

No, they're not, and in fact you want to get rid of your worst customers who are eating up all your time and resources and annoying your already busy staff. You want them to go to your competitors and ruin their business. In fact, the best thing you can do is get rid of the worst 10% of your customers and concentrate on the rest and getting more like them.

That doesn't mean you shouldn't solve/avoid  problems, but the customer is not always right and many you don't want as customers, especially if you are a small overburdened business.</description>
		<content:encoded><![CDATA[<p>&gt;&gt;the customer is always right</p>
<p>No, they&#8217;re not, and in fact you want to get rid of your worst customers who are eating up all your time and resources and annoying your already busy staff. You want them to go to your competitors and ruin their business. In fact, the best thing you can do is get rid of the worst 10% of your customers and concentrate on the rest and getting more like them.</p>
<p>That doesn&#8217;t mean you shouldn&#8217;t solve/avoid  problems, but the customer is not always right and many you don&#8217;t want as customers, especially if you are a small overburdened business.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Service Untitled &#187; Importance of making things easy. - customer service and customer service experience blog</title>
		<link>http://www.carsonified.com/misc/customer-service-tips#comment-2022</link>
		<pubDate>Mon, 05 Mar 2007 21:40:41 +0000</pubDate>
		<guid>http://www.carsonified.com/misc/customer-service-tips#comment-2022</guid>
					<description>[...] I&#8217;ve talked about cross-searching (part 1 and part 2) before. It&#8217;s really an interesting thing and can be very useful. A few weeks ago, I read a post on Ryan Caron&#8217;s blog about making customers happy with some simple customer service tips. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] I&#8217;ve talked about cross-searching (part 1 and part 2) before. It&#8217;s really an interesting thing and can be very useful. A few weeks ago, I read a post on Ryan Caron&#8217;s blog about making customers happy with some simple customer service tips. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Service Untitled - Douglas</title>
		<link>http://www.carsonified.com/misc/customer-service-tips#comment-2020</link>
		<pubDate>Mon, 05 Mar 2007 20:58:54 +0000</pubDate>
		<guid>http://www.carsonified.com/misc/customer-service-tips#comment-2020</guid>
					<description>Hi Ryan,

Great post! I've posted a follow-up and expansion of sorts on my blog. &lt;a href="http://www.serviceuntitled.com/importance-of-making-things-easy/2007/03/05/" rel="nofollow"&gt;Here&lt;/a&gt; is the link.</description>
		<content:encoded><![CDATA[<p>Hi Ryan,</p>
<p>Great post! I&#8217;ve posted a follow-up and expansion of sorts on my blog. <a href="http://www.serviceuntitled.com/importance-of-making-things-easy/2007/03/05/" rel="nofollow">Here</a> is the link.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Daniel Lieberman</title>
		<link>http://www.carsonified.com/misc/customer-service-tips#comment-1972</link>
		<pubDate>Sat, 03 Mar 2007 00:12:39 +0000</pubDate>
		<guid>http://www.carsonified.com/misc/customer-service-tips#comment-1972</guid>
					<description>What your tips point to is that every app should have an administrative interface built with customer support in mind.  Even if you didn't think about this when building the app, odds are it would be a small project for a developer who already knows the app to implement an interface that allows you to do most or all of the things you've described.  (Extracting information is almost always easy; sometimes the freebies and such are a little harder, but probably worth the investment -- and often the same capabilities can be reused as sales promotions.)</description>
		<content:encoded><![CDATA[<p>What your tips point to is that every app should have an administrative interface built with customer support in mind.  Even if you didn&#8217;t think about this when building the app, odds are it would be a small project for a developer who already knows the app to implement an interface that allows you to do most or all of the things you&#8217;ve described.  (Extracting information is almost always easy; sometimes the freebies and such are a little harder, but probably worth the investment &#8212; and often the same capabilities can be reused as sales promotions.)
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Alfred</title>
		<link>http://www.carsonified.com/misc/customer-service-tips#comment-1935</link>
		<pubDate>Thu, 01 Mar 2007 01:20:24 +0000</pubDate>
		<guid>http://www.carsonified.com/misc/customer-service-tips#comment-1935</guid>
					<description>I took a screenshot and uploaded on flickr..here is the link.
http://www.flickr.com/photos/14587817@N00/406266945/

Alfred.</description>
		<content:encoded><![CDATA[<p>I took a screenshot and uploaded on flickr..here is the link.<br />
<a href="http://www.flickr.com/photos/14587817@N00/406266945/" rel="nofollow">http://www.flickr.com/photos/14587817@N00/406266945/</a></p>
<p>Alfred.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Patrick Harrison</title>
		<link>http://www.carsonified.com/misc/customer-service-tips#comment-1916</link>
		<pubDate>Wed, 28 Feb 2007 09:51:45 +0000</pubDate>
		<guid>http://www.carsonified.com/misc/customer-service-tips#comment-1916</guid>
					<description>Everyone gets abusive customers at some stage, they are mainly just people who have no real way of communicating properly.

What the other bloggers who told you off don't realise is that no one in tech support/customer service should have to put up with abuse. Particularly if the error has been caused by the customer and is really nothing to do with your product.

From a legal point of view an employer has an obligation not to unduly expose employees to repeated stress. Such as taking abusive calls. At least in the UK.

A good trick we have found that works - if someone sends a ranting and abusive email, call them. This is assuming you have their number to hand. You will be amazed at how embarassed most will be, they never expected to be called. It also reminds them gently that emails are read by humans and that they may regret what they send.

The bottom line is that no customer has the right to be abusive and support is for the problem - not supporting the customer through some emotional crisis.

Anyway we have found that more than 90% of issues for us are down to customer's computers not working - nearly all Windows machines. However, you find that people will look for the first number to call, even when they know it's their machine. They are frustrated and want to shout at someone - anyone will do.

Anyway we only have 14 years front-line tech support experience to draw upon so what do we know?

P</description>
		<content:encoded><![CDATA[<p>Everyone gets abusive customers at some stage, they are mainly just people who have no real way of communicating properly.</p>
<p>What the other bloggers who told you off don&#8217;t realise is that no one in tech support/customer service should have to put up with abuse. Particularly if the error has been caused by the customer and is really nothing to do with your product.</p>
<p>From a legal point of view an employer has an obligation not to unduly expose employees to repeated stress. Such as taking abusive calls. At least in the UK.</p>
<p>A good trick we have found that works - if someone sends a ranting and abusive email, call them. This is assuming you have their number to hand. You will be amazed at how embarassed most will be, they never expected to be called. It also reminds them gently that emails are read by humans and that they may regret what they send.</p>
<p>The bottom line is that no customer has the right to be abusive and support is for the problem - not supporting the customer through some emotional crisis.</p>
<p>Anyway we have found that more than 90% of issues for us are down to customer&#8217;s computers not working - nearly all Windows machines. However, you find that people will look for the first number to call, even when they know it&#8217;s their machine. They are frustrated and want to shout at someone - anyone will do.</p>
<p>Anyway we only have 14 years front-line tech support experience to draw upon so what do we know?</p>
<p>P
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Ryan Carson</title>
		<link>http://www.carsonified.com/misc/customer-service-tips#comment-1907</link>
		<pubDate>Wed, 28 Feb 2007 01:14:41 +0000</pubDate>
		<guid>http://www.carsonified.com/misc/customer-service-tips#comment-1907</guid>
					<description>Alfred - I can't find that typo. Can you give me a URL?</description>
		<content:encoded><![CDATA[<p>Alfred - I can&#8217;t find that typo. Can you give me a URL?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Alfred</title>
		<link>http://www.carsonified.com/misc/customer-service-tips#comment-1906</link>
		<pubDate>Wed, 28 Feb 2007 01:09:09 +0000</pubDate>
		<guid>http://www.carsonified.com/misc/customer-service-tips#comment-1906</guid>
					<description>I've observed that most sites miss a critical component in their contact forms. I personally believe  that they should include a slot where a user specify the topic or area of support. For example, If its invoice related matters, they can type "invoice". This would simplify the support guy's work i.e , they can solve all invoice related problems at ago, then move to next area. For the case of sites like dropsend  that have support emails, request users to specify that the topic that affects them. Its a minor thing, but it would help alot. 

** On a separate note Ryan, there is a typo error on the FOWA website, the recent london event was held on 20-21 Feb and not 20-21 January.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve observed that most sites miss a critical component in their contact forms. I personally believe  that they should include a slot where a user specify the topic or area of support. For example, If its invoice related matters, they can type &#8220;invoice&#8221;. This would simplify the support guy&#8217;s work i.e , they can solve all invoice related problems at ago, then move to next area. For the case of sites like dropsend  that have support emails, request users to specify that the topic that affects them. Its a minor thing, but it would help alot. </p>
<p>** On a separate note Ryan, there is a typo error on the FOWA website, the recent london event was held on 20-21 Feb and not 20-21 January.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Lars Fischer</title>
		<link>http://www.carsonified.com/misc/customer-service-tips#comment-1887</link>
		<pubDate>Tue, 27 Feb 2007 14:40:39 +0000</pubDate>
		<guid>http://www.carsonified.com/misc/customer-service-tips#comment-1887</guid>
					<description>...or use SQL and search the database for user accounts :-)</description>
		<content:encoded><![CDATA[<p>&#8230;or use SQL and search the database for user accounts :-)
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
