<?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: Disconnected? Call back.</title>
	<atom:link href="http://www.serviceuntitled.com/disconnected-call-bac/2008/07/24/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.serviceuntitled.com/disconnected-call-bac/2008/07/24/</link>
	<description>The blog about customer service and the customer service experience.</description>
	<lastBuildDate>Fri, 10 Feb 2012 08:35:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Service Untitled</title>
		<link>http://www.serviceuntitled.com/disconnected-call-bac/2008/07/24/comment-page-1/#comment-832062</link>
		<dc:creator>Service Untitled</dc:creator>
		<pubDate>Wed, 26 Nov 2008 17:26:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.serviceuntitled.com/?p=693#comment-832062</guid>
		<description>Tim,

Those are some excellent points and thanks for posting them. Calling customers back can certainly be difficult in a lot of call centers and you addressed many of the difficulties in your comment. Ideally, managers would create an environment in which calling the customer back would be feasible and not work against customer service representatives, but that is only true in a minority of call centers.</description>
		<content:encoded><![CDATA[<p>Tim,</p>
<p>Those are some excellent points and thanks for posting them. Calling customers back can certainly be difficult in a lot of call centers and you addressed many of the difficulties in your comment. Ideally, managers would create an environment in which calling the customer back would be feasible and not work against customer service representatives, but that is only true in a minority of call centers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Redmond</title>
		<link>http://www.serviceuntitled.com/disconnected-call-bac/2008/07/24/comment-page-1/#comment-831920</link>
		<dc:creator>Tim Redmond</dc:creator>
		<pubDate>Wed, 26 Nov 2008 13:22:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.serviceuntitled.com/?p=693#comment-831920</guid>
		<description>From the customer perspective, we all want to receive a call back. We want to feel heard, appreciated and even more importantly, we want our issue resolved. Although you have listed the problems with not calling customers back, I can certainly list reasons why customers are not called back in several of the call centers I have worked. As a customer service rep, I know that these are not excuses at all.

Now I will admit, all of these are subject to abuse by one or more parties including decision making executives who control the big picture.

I used to get upset when I didn&#039;t get a call back, but since I have worked in a call center for several years, I know that the issue is not a cut and dry issue. For all of those who think that the customer service rep is being lazy, walk a mile in our shoes.


1. when a call drops, often another caller is on the other end. How would you feel if you just got to a rep and he/she placed you on hold to deal with a previous customer?  Frankly, several times I have had a call come in after a dropped call while I&#039;m finishing my notes and I handle that situation. When I&#039;m finished, I try to call the customer back but get a busy signal. I look on the account only to find that they have already called back.  Most customers do not wait to get a call back and it is unlikely that every dropped call is going to be followed by a break enough to call a customer back.



2. In many call centers, a rep who calls a customer back loses, because that outbound call goes against his/her call matrix. I think that is bull, but the rep suffers for doing this.

3. Often queues spike at anytime and dropped calls occur quite often during those time periods. Some induced by reps and others by the system. The law of averages yields that the more something is interacted, the more you have a chance of failure. Now I&#039;m not referring to the normal times when there is a high call volume, but those special times when something seems to be wrong or different. These could be an outage in the cell network, an influx of calls on  a relatively new product, or pre rollout of something new.

4. customer service reps have no true input into the process. they are drones. They have to follow the rules or that seat will fill with someone else. Call centers have an extremely high rate of turnover, thus, overhead is always high in the customer service department. 

5. We work in an ever changing dynamic often with rules changing from week to week, yet we&#039;re supposed to be experts in our field. 

6. To deal with a customer service rep, get to the point. We don&#039;t need stories about your dog just to hear in the end that you need help installing windows on a computer. Customer service reps are under pressure from both the company and the customers and often without help from either side to resolve the problem. Common sense it should be common sense that a customer knows his/her account information. It should be common sense that the customer read the manual for their product. Sometimes we have to train customers on things not necessarily covered by my company.</description>
		<content:encoded><![CDATA[<p>From the customer perspective, we all want to receive a call back. We want to feel heard, appreciated and even more importantly, we want our issue resolved. Although you have listed the problems with not calling customers back, I can certainly list reasons why customers are not called back in several of the call centers I have worked. As a customer service rep, I know that these are not excuses at all.</p>
<p>Now I will admit, all of these are subject to abuse by one or more parties including decision making executives who control the big picture.</p>
<p>I used to get upset when I didn&#8217;t get a call back, but since I have worked in a call center for several years, I know that the issue is not a cut and dry issue. For all of those who think that the customer service rep is being lazy, walk a mile in our shoes.</p>
<p>1. when a call drops, often another caller is on the other end. How would you feel if you just got to a rep and he/she placed you on hold to deal with a previous customer?  Frankly, several times I have had a call come in after a dropped call while I&#8217;m finishing my notes and I handle that situation. When I&#8217;m finished, I try to call the customer back but get a busy signal. I look on the account only to find that they have already called back.  Most customers do not wait to get a call back and it is unlikely that every dropped call is going to be followed by a break enough to call a customer back.</p>
<p>2. In many call centers, a rep who calls a customer back loses, because that outbound call goes against his/her call matrix. I think that is bull, but the rep suffers for doing this.</p>
<p>3. Often queues spike at anytime and dropped calls occur quite often during those time periods. Some induced by reps and others by the system. The law of averages yields that the more something is interacted, the more you have a chance of failure. Now I&#8217;m not referring to the normal times when there is a high call volume, but those special times when something seems to be wrong or different. These could be an outage in the cell network, an influx of calls on  a relatively new product, or pre rollout of something new.</p>
<p>4. customer service reps have no true input into the process. they are drones. They have to follow the rules or that seat will fill with someone else. Call centers have an extremely high rate of turnover, thus, overhead is always high in the customer service department. </p>
<p>5. We work in an ever changing dynamic often with rules changing from week to week, yet we&#8217;re supposed to be experts in our field. </p>
<p>6. To deal with a customer service rep, get to the point. We don&#8217;t need stories about your dog just to hear in the end that you need help installing windows on a computer. Customer service reps are under pressure from both the company and the customers and often without help from either side to resolve the problem. Common sense it should be common sense that a customer knows his/her account information. It should be common sense that the customer read the manual for their product. Sometimes we have to train customers on things not necessarily covered by my company.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Sweeney</title>
		<link>http://www.serviceuntitled.com/disconnected-call-bac/2008/07/24/comment-page-1/#comment-730758</link>
		<dc:creator>Paul Sweeney</dc:creator>
		<pubDate>Tue, 29 Jul 2008 11:57:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.serviceuntitled.com/?p=693#comment-730758</guid>
		<description>Oh dear god. There is no excuse for not calling a customer back. There is also no excuse for not calling a percentage of your customers back and asking them &quot;did you get what you need from that call&quot;, in a survey mechanism. Simple three questions is usually all you need. Here is a question to ask yourself: how would you feel if you were talking to a business contact and your call dropped, and he/she didn&#039;t bother to call you back, ever? !!</description>
		<content:encoded><![CDATA[<p>Oh dear god. There is no excuse for not calling a customer back. There is also no excuse for not calling a percentage of your customers back and asking them &#8220;did you get what you need from that call&#8221;, in a survey mechanism. Simple three questions is usually all you need. Here is a question to ask yourself: how would you feel if you were talking to a business contact and your call dropped, and he/she didn&#8217;t bother to call you back, ever? !!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

