<?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 Customer Service Just Plain Sucks</title>
	<atom:link href="http://jtpedersen.net/2010/02/02/why-customer-service-just-plain-sucks/feed/" rel="self" type="application/rss+xml" />
	<link>http://jtpedersen.net/2010/02/02/why-customer-service-just-plain-sucks/</link>
	<description>Innovative Business Leadership</description>
	<lastBuildDate>Thu, 10 May 2012 22:33:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: JT</title>
		<link>http://jtpedersen.net/2010/02/02/why-customer-service-just-plain-sucks/comment-page-1/#comment-75</link>
		<dc:creator>JT</dc:creator>
		<pubDate>Fri, 05 Feb 2010 23:56:26 +0000</pubDate>
		<guid isPermaLink="false">http://jtpedersen.net/?p=1673#comment-75</guid>
		<description>Hello Chuck,

Good point, glad you brought it up.

Makes me reflect on a point earlier in life as a support tech.  I worked for a smaller, very customer-oriented company.  After being acquired by a larger firm, metrics slowly worked their way into our lives.  Measuring, reporting, justifying.  Customer service, at times, seemed to become a &#039;problem mitigation&#039; activity more than a customer &lt;em&gt;service &lt;/em&gt;activity.

Cheers!</description>
		<content:encoded><![CDATA[<p>Hello Chuck,</p>
<p>Good point, glad you brought it up.</p>
<p>Makes me reflect on a point earlier in life as a support tech.  I worked for a smaller, very customer-oriented company.  After being acquired by a larger firm, metrics slowly worked their way into our lives.  Measuring, reporting, justifying.  Customer service, at times, seemed to become a &#8216;problem mitigation&#8217; activity more than a customer <em>service </em>activity.</p>
<p>Cheers!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chuck van der Linden</title>
		<link>http://jtpedersen.net/2010/02/02/why-customer-service-just-plain-sucks/comment-page-1/#comment-74</link>
		<dc:creator>Chuck van der Linden</dc:creator>
		<pubDate>Fri, 05 Feb 2010 06:43:30 +0000</pubDate>
		<guid isPermaLink="false">http://jtpedersen.net/?p=1673#comment-74</guid>
		<description>been there and got 7 years plus worth of shirts.  But often it was hard, because being focused on truly meeting the customer&#039;s needs and solving their problems resulted in &#039;the wrong numbers&#039; for all of the things your managers used to judge your &#039;performance&#039;  Longer calls, fewer calls per day, etc.   In fact the only number that looked &#039;good&#039; if it was ever considered was &#039;did they have to call back again regarding the same issue&#039;.

IMHO most of the people who get jobs in support truly WANT to help the customer  But then they come up against policies and goals  (short calls, taking lots of calls per day) that create incentives to just &#039;get rid&#039; of the caller as rapidly as possible without regard to if their issue is resolved.  And these reps start to resent the customers who have tough or tricky problems, or can&#039;t explain what they want very well, and thus cause their &#039;numbers&#039; to suffer.  This causes people to get jaded or burn out, and just punch the clock.

It&#039;s not the people on the phone that have become the death of good support, but the people managing them that are to blame.

Those places that have good support usually manage to a different standard.  The numbers they care about are &#039;problems solved&#039; and &#039;delighted customers&#039; and they empower their people to do what&#039;s needed to solve the customer&#039;s problems without silly statistics like call length and calls per hour.</description>
		<content:encoded><![CDATA[<p>been there and got 7 years plus worth of shirts.  But often it was hard, because being focused on truly meeting the customer&#8217;s needs and solving their problems resulted in &#8216;the wrong numbers&#8217; for all of the things your managers used to judge your &#8216;performance&#8217;  Longer calls, fewer calls per day, etc.   In fact the only number that looked &#8216;good&#8217; if it was ever considered was &#8216;did they have to call back again regarding the same issue&#8217;.</p>
<p>IMHO most of the people who get jobs in support truly WANT to help the customer  But then they come up against policies and goals  (short calls, taking lots of calls per day) that create incentives to just &#8216;get rid&#8217; of the caller as rapidly as possible without regard to if their issue is resolved.  And these reps start to resent the customers who have tough or tricky problems, or can&#8217;t explain what they want very well, and thus cause their &#8216;numbers&#8217; to suffer.  This causes people to get jaded or burn out, and just punch the clock.</p>
<p>It&#8217;s not the people on the phone that have become the death of good support, but the people managing them that are to blame.</p>
<p>Those places that have good support usually manage to a different standard.  The numbers they care about are &#8216;problems solved&#8217; and &#8216;delighted customers&#8217; and they empower their people to do what&#8217;s needed to solve the customer&#8217;s problems without silly statistics like call length and calls per hour.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

