<?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: Getting more from your support tickets – are you tuned in to what they’re really telling you?</title>
	<atom:link href="http://blog.parature.com/index.php/customerserviceexperience/getting-more-from-your-support-tickets/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.parature.com/customerserviceexperience/getting-more-from-your-support-tickets/</link>
	<description>The Parature Blog</description>
	<lastBuildDate>Fri, 20 Nov 2009 14:54:37 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ashwin Nayak</title>
		<link>http://blog.parature.com/customerserviceexperience/getting-more-from-your-support-tickets/comment-page-1/#comment-285</link>
		<dc:creator>Ashwin Nayak</dc:creator>
		<pubDate>Wed, 08 Jul 2009 18:13:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.parature.com/?p=201#comment-285</guid>
		<description>It&#039;s great point. In our organization, we have home grown  ticketing system to support customers. The support staffs are educated to think out of the box and ask open ended questions to uncover business problem and potential oppertunities. But in reality, it&#039;s kind of tough as they are heads down to solve the ticket. So they either forget to ask specific questions or don&#039;t have skill to ask right question. 

It would be nice to see a tool that can analyze tickets and provide valuable insight that can be helpful for upper management. I beleive every ticket can be an oppertunity for future sales, process improvement and building knowledge base.</description>
		<content:encoded><![CDATA[<p>It&#8217;s great point. In our organization, we have home grown  ticketing system to support customers. The support staffs are educated to think out of the box and ask open ended questions to uncover business problem and potential oppertunities. But in reality, it&#8217;s kind of tough as they are heads down to solve the ticket. So they either forget to ask specific questions or don&#8217;t have skill to ask right question. </p>
<p>It would be nice to see a tool that can analyze tickets and provide valuable insight that can be helpful for upper management. I beleive every ticket can be an oppertunity for future sales, process improvement and building knowledge base.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lesley Sweetman</title>
		<link>http://blog.parature.com/customerserviceexperience/getting-more-from-your-support-tickets/comment-page-1/#comment-281</link>
		<dc:creator>Lesley Sweetman</dc:creator>
		<pubDate>Tue, 07 Jul 2009 11:19:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.parature.com/?p=201#comment-281</guid>
		<description>We have support tickets as part of our contact management strategy but it&#039;s horribly under utilised, only 3% of our monthly contacts use the ticketing functionality. The knowledge base is maintained but the process seems &quot;clunky&quot; compared to picking up the phone or sending us an email. Any advice gratefully received !!!</description>
		<content:encoded><![CDATA[<p>We have support tickets as part of our contact management strategy but it&#8217;s horribly under utilised, only 3% of our monthly contacts use the ticketing functionality. The knowledge base is maintained but the process seems &#8220;clunky&#8221; compared to picking up the phone or sending us an email. Any advice gratefully received !!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keith Morneault</title>
		<link>http://blog.parature.com/customerserviceexperience/getting-more-from-your-support-tickets/comment-page-1/#comment-276</link>
		<dc:creator>Keith Morneault</dc:creator>
		<pubDate>Mon, 06 Jul 2009 19:00:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.parature.com/?p=201#comment-276</guid>
		<description>This is all too true.  I&#039;ve returned to the Helpdesk space after several years in Strategic Project Management.  I have actively been trying to influence a paradigm shift in our organization to support these principles.  

To reiterate what Mr. Watson already stated so succinctly and provide some real-world usage:

1.) Every helpdesk ticket is an opportunity.  You have the opportunity to find out the issues that pain your users the most.  You also have the opportunity to influence how they feel about your product/service/organization.  A bad service experience can have a negative impact on even the best applications and a superior customer service experience can make up for gaps in your product/service until you have the opportunity to address them.  In my support organization, we leverage trending data from the Helpdesk tickets to identify the largest opportunities and then prioritize our defect reduction and enhancement efforts to focus on the 20% of our issues that generate 80% of our Helpdesk volume.  We also survey 10% of our 500 weekly Helpdesk tickets.  Every complaint is investigated and feedback incorporated into how we do our work to improve the caller experience.  Our resolution times have improved 75%, first call closure rate doubled and customer satisfaction improved 15% as a result.  

2.) It&#039;s always about quality over quantity.  1000&#039;s of knowledge articles or self help references are useless if they are difficult to find or out-dated.  A smaller, yet accurate knowledge base that touches 80% of the issues is much more likely to have a lasting impression and leave your users with reason to go back for more.  We had a knowledge base with literally 1000&#039;s of articles but found that users (and even internal staff) rarely referenced it.  We&#039;ve started streamlining the content, removing stale material, updating it on a monthly basis and now internal staff are using it and even touting it&#039;s benefits to others.  It is contagious.

With regards to questioning the status quo, my team uses a Lean and supports it with Six Sigma to help focus our efforts.  Management needs to support them whenever they ask &quot;why&quot; in interacting with other teams supporting our operation.  We&#039;ve gotten to the point where anyone on the team readily challenges the most detrimental phrase to process improvement, &quot;we&#039;ve always done it that way&quot;.</description>
		<content:encoded><![CDATA[<p>This is all too true.  I&#8217;ve returned to the Helpdesk space after several years in Strategic Project Management.  I have actively been trying to influence a paradigm shift in our organization to support these principles.  </p>
<p>To reiterate what Mr. Watson already stated so succinctly and provide some real-world usage:</p>
<p>1.) Every helpdesk ticket is an opportunity.  You have the opportunity to find out the issues that pain your users the most.  You also have the opportunity to influence how they feel about your product/service/organization.  A bad service experience can have a negative impact on even the best applications and a superior customer service experience can make up for gaps in your product/service until you have the opportunity to address them.  In my support organization, we leverage trending data from the Helpdesk tickets to identify the largest opportunities and then prioritize our defect reduction and enhancement efforts to focus on the 20% of our issues that generate 80% of our Helpdesk volume.  We also survey 10% of our 500 weekly Helpdesk tickets.  Every complaint is investigated and feedback incorporated into how we do our work to improve the caller experience.  Our resolution times have improved 75%, first call closure rate doubled and customer satisfaction improved 15% as a result.  </p>
<p>2.) It&#8217;s always about quality over quantity.  1000&#8217;s of knowledge articles or self help references are useless if they are difficult to find or out-dated.  A smaller, yet accurate knowledge base that touches 80% of the issues is much more likely to have a lasting impression and leave your users with reason to go back for more.  We had a knowledge base with literally 1000&#8217;s of articles but found that users (and even internal staff) rarely referenced it.  We&#8217;ve started streamlining the content, removing stale material, updating it on a monthly basis and now internal staff are using it and even touting it&#8217;s benefits to others.  It is contagious.</p>
<p>With regards to questioning the status quo, my team uses a Lean and supports it with Six Sigma to help focus our efforts.  Management needs to support them whenever they ask &#8220;why&#8221; in interacting with other teams supporting our operation.  We&#8217;ve gotten to the point where anyone on the team readily challenges the most detrimental phrase to process improvement, &#8220;we&#8217;ve always done it that way&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Hanulec</title>
		<link>http://blog.parature.com/customerserviceexperience/getting-more-from-your-support-tickets/comment-page-1/#comment-275</link>
		<dc:creator>Ken Hanulec</dc:creator>
		<pubDate>Mon, 06 Jul 2009 18:43:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.parature.com/?p=201#comment-275</guid>
		<description>I would like to speak with a sales rep and get updated product and pricing information. We are now budgeting for an enhanced customer support platform and the timing is good.

Contact via email, I will schedule a time for a phone conversation then.</description>
		<content:encoded><![CDATA[<p>I would like to speak with a sales rep and get updated product and pricing information. We are now budgeting for an enhanced customer support platform and the timing is good.</p>
<p>Contact via email, I will schedule a time for a phone conversation then.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
