<?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: Sometimes it’s Better to Let Customers Hold for Service</title>
	<atom:link href="http://servicestrategies-blog.com/?feed=rss2&#038;p=150" rel="self" type="application/rss+xml" />
	<link>http://servicestrategies-blog.com/?p=150</link>
	<description>Blog by Service Strategies</description>
	<lastBuildDate>Tue, 29 Jun 2010 05:37:36 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Greg Coleman</title>
		<link>http://servicestrategies-blog.com/?p=150&#038;cpage=1#comment-428</link>
		<dc:creator>Greg Coleman</dc:creator>
		<pubDate>Wed, 07 Oct 2009 19:26:00 +0000</pubDate>
		<guid isPermaLink="false">http://servicestrategies-blog.com/?p=150#comment-428</guid>
		<description>Thanks Terri and James for the comments... I&#039;ve got to recognize Ben Stephens for contributing the post though!  Great work Ben... Another excellent article.</description>
		<content:encoded><![CDATA[<p>Thanks Terri and James for the comments&#8230; I&#8217;ve got to recognize Ben Stephens for contributing the post though!  Great work Ben&#8230; Another excellent article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Terri Kolander</title>
		<link>http://servicestrategies-blog.com/?p=150&#038;cpage=1#comment-387</link>
		<dc:creator>Terri Kolander</dc:creator>
		<pubDate>Thu, 10 Sep 2009 19:04:39 +0000</pubDate>
		<guid isPermaLink="false">http://servicestrategies-blog.com/?p=150#comment-387</guid>
		<description>Great article Greg!

It is always interesting to observe the customer behaviors that develop from answering the phone to quickly.  When considering your second bullet, there is an opportunity to encourage customers to engage readily with their &quot;integrated electronic support environment &quot; because the experience exceeds that of a phone being answered within seconds.  Many times I have observed that a more conservitive ASA pairs up with an active e-service environment. 

Thanks for the great read.

Terri Kolander</description>
		<content:encoded><![CDATA[<p>Great article Greg!</p>
<p>It is always interesting to observe the customer behaviors that develop from answering the phone to quickly.  When considering your second bullet, there is an opportunity to encourage customers to engage readily with their &#8220;integrated electronic support environment &#8221; because the experience exceeds that of a phone being answered within seconds.  Many times I have observed that a more conservitive ASA pairs up with an active e-service environment. </p>
<p>Thanks for the great read.</p>
<p>Terri Kolander</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Cowie</title>
		<link>http://servicestrategies-blog.com/?p=150&#038;cpage=1#comment-367</link>
		<dc:creator>James Cowie</dc:creator>
		<pubDate>Sun, 06 Sep 2009 00:25:09 +0000</pubDate>
		<guid isPermaLink="false">http://servicestrategies-blog.com/?p=150#comment-367</guid>
		<description>Hi Greg.  Great list and very similar to the advice we give clients and the changes we help them achieve.  We&#039;ve split this problem into 2 elements: reducing calls for support and making the call resolution process as efficient as possible.  
We achieve call reduction through monitoring, reporting and improvement activities, usually setting up tight teams with product development staff to reduce defects and product quality related issues.  We attack each issue as a single bite size issue to be resolved and have significant success in eliminating calls through this process.  We often work with groups other than services to improve QA, Professional Services, or Training.  Through this approach, we have not only eliminated many causes of support calls, but also improved support for new releases, which has flow-on in response times, resolution times and further issue reduction.
Our primary approach to improving the productivity of Support Staff and therefore getting through more calls with the same or less staff and reducing support costs has been to assist our clients in implementing and managing solid integrated electronic support environments within their products, but more importantly in their support websites and knowledge management.  The goal is to make support less of an ordeal and provide solutions when the customer needs them.  We have achieved significant breakthroughs using normal language recognition and easy to navigate tools that facilitate quick access to solutions and a simplified support request process.  
Using this automated approach allows answers for the 20 - 30% of issues that create the calls that generate 50 - 60% of workload to be answered quickly and with only the time required for the specific caller.  Counter-intuitively it frees up time.  We then establish processes to take the freed up support time and use it to build in more answers.
We are using telephone technologies (VoIP and traditional), social media, traditional systems and a range of other techniques, to produce significant results for our clients, many of whom had already achieved high performance levels.  For a number of them, it has also opened up opportunities to reduce costs, raise service levels and bring work back home thereby reducinge the amount of off-shoring they had been doing. 
A spin-off of the automation has been that we have made it easier for our clients to basically remove queues and to utilise staff with secondary skills to provide high quality &#039;expert&#039; support and resolve cases thereby almost eliminating backlogs.  We&#039;ve even managed to make work-from-home, on-demand support work seamlessly (any time support at a reasonable cost).  An added advantage of the approach we use is that it makes all request recipients appear as experienced and knowledgeable, rather than just warm bodies.  And most importantly it raises their resolution accuracy, speed and closure rates, which increases their confidence levels. This in turn improves the customer experience and frees up more time for customer engagement, which customers tell us they see as greatly improved service levels.
So in a nutshell, we reduce service costs, improve the support experience, raise customer satisfaction and loyalty levels and achieve great staff satisfaction.  Not a bad outcome for those who take your advice.
Take care,
James</description>
		<content:encoded><![CDATA[<p>Hi Greg.  Great list and very similar to the advice we give clients and the changes we help them achieve.  We&#8217;ve split this problem into 2 elements: reducing calls for support and making the call resolution process as efficient as possible.<br />
We achieve call reduction through monitoring, reporting and improvement activities, usually setting up tight teams with product development staff to reduce defects and product quality related issues.  We attack each issue as a single bite size issue to be resolved and have significant success in eliminating calls through this process.  We often work with groups other than services to improve QA, Professional Services, or Training.  Through this approach, we have not only eliminated many causes of support calls, but also improved support for new releases, which has flow-on in response times, resolution times and further issue reduction.<br />
Our primary approach to improving the productivity of Support Staff and therefore getting through more calls with the same or less staff and reducing support costs has been to assist our clients in implementing and managing solid integrated electronic support environments within their products, but more importantly in their support websites and knowledge management.  The goal is to make support less of an ordeal and provide solutions when the customer needs them.  We have achieved significant breakthroughs using normal language recognition and easy to navigate tools that facilitate quick access to solutions and a simplified support request process.<br />
Using this automated approach allows answers for the 20 &#8211; 30% of issues that create the calls that generate 50 &#8211; 60% of workload to be answered quickly and with only the time required for the specific caller.  Counter-intuitively it frees up time.  We then establish processes to take the freed up support time and use it to build in more answers.<br />
We are using telephone technologies (VoIP and traditional), social media, traditional systems and a range of other techniques, to produce significant results for our clients, many of whom had already achieved high performance levels.  For a number of them, it has also opened up opportunities to reduce costs, raise service levels and bring work back home thereby reducinge the amount of off-shoring they had been doing.<br />
A spin-off of the automation has been that we have made it easier for our clients to basically remove queues and to utilise staff with secondary skills to provide high quality &#8216;expert&#8217; support and resolve cases thereby almost eliminating backlogs.  We&#8217;ve even managed to make work-from-home, on-demand support work seamlessly (any time support at a reasonable cost).  An added advantage of the approach we use is that it makes all request recipients appear as experienced and knowledgeable, rather than just warm bodies.  And most importantly it raises their resolution accuracy, speed and closure rates, which increases their confidence levels. This in turn improves the customer experience and frees up more time for customer engagement, which customers tell us they see as greatly improved service levels.<br />
So in a nutshell, we reduce service costs, improve the support experience, raise customer satisfaction and loyalty levels and achieve great staff satisfaction.  Not a bad outcome for those who take your advice.<br />
Take care,<br />
James</p>
]]></content:encoded>
	</item>
</channel>
</rss>
