<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Don&#039;t Just Talk, Blog! &#187; customer service</title>
	<atom:link href="http://www.dontjusttalkbeheard.com/blog/tag/customer-service/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dontjusttalkbeheard.com/blog</link>
	<description>Communication Coaching with David Levin</description>
	<lastBuildDate>Wed, 14 Jul 2010 20:42:32 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>You Can&#8217;t Take It Back</title>
		<link>http://www.dontjusttalkbeheard.com/blog/you-cant-take-it-back/</link>
		<comments>http://www.dontjusttalkbeheard.com/blog/you-cant-take-it-back/#comments</comments>
		<pubDate>Sat, 14 Nov 2009 02:56:07 +0000</pubDate>
		<dc:creator>David Levin</dc:creator>
				<category><![CDATA[Communication]]></category>
		<category><![CDATA[communication training]]></category>
		<category><![CDATA[customer service]]></category>
		<category><![CDATA[david levin]]></category>
		<category><![CDATA[leadership]]></category>
		<category><![CDATA[leadership development]]></category>
		<category><![CDATA[leadership training]]></category>

		<guid isPermaLink="false">http://www.dontjusttalkbeheard.com/blog/?p=56</guid>
		<description><![CDATA[Ever said something you wish you could take back? Me too. Here&#8217;s one from 25 years ago. (It&#8217;s not that I have to go back that far to find an example. Just to find one that doesn&#8217;t still hurt.) :-) Back then, I was on the road full-time playing music, and had a band of [...]]]></description>
			<content:encoded><![CDATA[<p>Ever said something you wish you could take back? Me too. Here&#8217;s one from 25 years ago. (It&#8217;s not that I have to go back that far to find an example. Just to find one that doesn&#8217;t still hurt.) :-)</p>
<p>Back then, I was on the road full-time playing music, and had a band of my own, called, originally enough, <em>T</em><em>he David Levin Band</em>. We played a lot of places in the middle of nowhere and had a good bit of fun doing it. (A sad sort of fun, in retrospect. But hey, we were young!) I should also say that I wasn&#8217;t much of a band leader. In those days, I was generally more interested in hanging out with my buddies than running a business. But during one particular band meeting I apparently felt some sudden misguided impulse to take charge or something because I distinctly remember saying to the band, &#8220;Guys, this is not a democracy!&#8221;</p>
<p>Twenty-five years later, I&#8217;m still paying for it.<br />
<span id="more-56"></span><br />
Actually, we laugh about it now. (I&#8217;m still friends with several of the guys.) But the point is, we <em>remember</em> it. And I have no doubt it played a role in that band breaking up not long afterward.</p>
<p>There&#8217;s a famous quotation, attributed to Grace Hopper, that says, &#8220;It&#8217;s easier to ask forgiveness than to get permission.&#8221; I&#8217;ve always liked the quote, and I&#8217;m sure it&#8217;s true in a lot of situations. But communication is not one of them. In fact, with communication it&#8217;s the opposite. Once you drop that bomb, that&#8217;s it. There&#8217;s no taking it back. No do-overs. And the truth is, it&#8217;s ten times harder to undo a communication mistake than it is to get it right in the first place, <em>if</em> the mistake can even be undone at all.</p>
<p>Communication is too important to just go with your gut in the moment. If you have something that needs to be said, take the time to say it right. Think it through ahead of time. Plan it out. Be on the lookout for any disconnects. And, of course, make sure to run it past a feedback buddy first.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.dontjusttalkbeheard.com/blog/you-cant-take-it-back/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Got a problem with someone? Try saying, &#8220;I&#8217;m sorry.&#8221;</title>
		<link>http://www.dontjusttalkbeheard.com/blog/try-saying-im-sorry/</link>
		<comments>http://www.dontjusttalkbeheard.com/blog/try-saying-im-sorry/#comments</comments>
		<pubDate>Fri, 30 Oct 2009 13:19:29 +0000</pubDate>
		<dc:creator>David Levin</dc:creator>
				<category><![CDATA[Communication]]></category>
		<category><![CDATA[Be Heard!]]></category>
		<category><![CDATA[communication coach]]></category>
		<category><![CDATA[communication training]]></category>
		<category><![CDATA[customer service]]></category>
		<category><![CDATA[customer service training]]></category>
		<category><![CDATA[david levin]]></category>
		<category><![CDATA[Don't Just Talk]]></category>
		<category><![CDATA[leadership]]></category>
		<category><![CDATA[leadership development]]></category>
		<category><![CDATA[leadership training]]></category>

		<guid isPermaLink="false">http://www.dontjusttalkbeheard.com/blog/?p=50</guid>
		<description><![CDATA[Here&#8217;s something you can take to the bank: If you&#8217;re having some sort of trouble with someone—conflict, tension, bad blood, whatever—nothing gets things back on track like a good old-fashioned apology. &#8220;But I didn&#8217;t do anything wrong!&#8221; you say, &#8220;It wasn’t my fault.&#8221; I understand. And I didn&#8217;t say it was. But who&#8217;s at fault [...]]]></description>
			<content:encoded><![CDATA[<div>
Here&#8217;s something you can take to the bank: If you&#8217;re having some sort of trouble with someone—conflict, tension, bad blood, whatever—nothing gets things back on track like a good old-fashioned apology.</p>
<p>&#8220;But I didn&#8217;t do anything wrong!&#8221; you say, &#8220;It wasn’t my fault.&#8221;</p>
<p>I understand. And I didn&#8217;t say it was. But who&#8217;s at fault is not the point. The point is that the relationship has gone bad, and that&#8217;s no good for either of you.</p>
<p>Besides, I&#8217;m not saying you should apologize for whatever it is you&#8217;re disagreeing about. In fact, doing so might do more harm than good. The most important thing here is that whatever you say has to be authentic and heartfelt. Apologizing for something that you didn&#8217;t actually do is likely to be neither. And it could even be seen as being manipulative, which is even worse.<br />
<span id="more-50"></span><br />
What you can—and should—do, however, is express sorrow over the state of the relationship and apologize for whatever you&#8217;ve contributed to it.</p>
<p>Example: &#8220;I&#8217;m really sorry for the way things have been lately between us. I know I&#8217;ve done some things that have offended or hurt you in some way, but I sure didn&#8217;t mean to. I&#8217;ve always [enjoyed/liked/respected] you, and don&#8217;t know why things should have to be  this way. I&#8217;d sure like them to be better. Anyway, I just wanted to let you know.&#8221;</p>
<p>The beauty of this approach is that by focusing you on the relationship rather than the conflict, it puts you in a more open, humble, and generous place, which tends to bring out similar feelings in the other person. Will it fix every problem? No. Sometimes people are too attached to a conflict to open up and let go of it. But a lot of times it will. And either way, it will always make <em>you</em> feel better—a lot better, in fact—and that by itself is reason enough in my book.</div>
<div></div>
<div>Next time you&#8217;re having difficulty with someone, try giving them a good, heartfelt apology. It&#8217;s surprising the difference it can make.</div>
<div></div>
<div></div>
]]></content:encoded>
			<wfw:commentRss>http://www.dontjusttalkbeheard.com/blog/try-saying-im-sorry/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>8 beers</title>
		<link>http://www.dontjusttalkbeheard.com/blog/8-beers/</link>
		<comments>http://www.dontjusttalkbeheard.com/blog/8-beers/#comments</comments>
		<pubDate>Fri, 15 May 2009 15:22:10 +0000</pubDate>
		<dc:creator>David Levin</dc:creator>
				<category><![CDATA[Communication]]></category>
		<category><![CDATA[communication coach]]></category>
		<category><![CDATA[customer service]]></category>
		<category><![CDATA[customer service training]]></category>

		<guid isPermaLink="false">http://dontjusttalkbeheard.com/blog/?p=19</guid>
		<description><![CDATA[I had an interesting experience at my neighborhood grocery store the other day.  I was walking down the soda aisle, looking for my favorite caffeinated beverage (Coke Zero), when I passed a store employee stocking the shelves.  As he worked, he was also talking on a cell phone.  “Yeah,” I heard him laugh, ”especially after [...]]]></description>
			<content:encoded><![CDATA[<p><span>I had an interesting experience at my neighborhood grocery store the other day.  I was walking down the soda aisle, looking for my favorite caffeinated beverage (Coke Zero), when I passed a store employee stocking the shelves.  As he worked, he was also talking on a cell phone.  “Yeah,” I heard him laugh, ”especially after 8 beers!”  I don’t know who he was talking to, but my impression was that it was a personal call.  The rest of his conversation faded from hearing as I walked on. </span></p>
<p><span>The good news, I suppose, was that he seemed to be enjoying himself.  But enjoying your <em>work</em> is one thing.  Enjoying yourself <em>at</em> work is something else entirely, and not necessarily a good thing, at least from an employer’s perspective.  And by the way, this was not a teenager talking, if you’re wondering.  If I had to guess, I’d put him in his late 30s to early 40s.  Also, let me say that I have no problem with people drinking, in general.  (Though 8 beers does sound a bit excessive.)  My concern is with the message his conversation sends to me as a customer, and the questions it raises in my mind.  <em>Does he have a drinking problem?  Should I be concerned about him?  Is he drunk right now?  Does management know?  Is this some sort of drink-friendly grocer?  They do seem chipper.  Is there something else going on?  Are other staff members drunk too?</em></span><br />
<span id="more-19"></span><br />
<span>You see my problem?  Or, actually, their problem?  I don’t think these are the thoughts they want me to have while I’m in their store.  I think they’d rather I was thinking what great service they give me, and how well cared for, understood and appreciated I feel when I’m there. </span></p>
<p><span>Now, to be fair, I do feel cared for, understood and appreciated by this particular store.  I’m a loyal customer.  So, this situation wasn’t really a problem for me.  But what if I didn’t already feel that way?  What if I was still forming my opinions as to whether I wanted to shop there?  That phone call scene might be all it took for me to decide to go somewhere else.  Can they really afford to drive people to their competitors? </span></p>
<p><span>At the very least, it was a lost opportunity.  Think of the difference if he had been focused on me instead.  If, as he saw me approach, he had offered a quick smile and said, “How are you doing today?  Anything I can help you find?”   Rather then pushing me away, he would have anchored in my mind the very messages they want to send.  Isn’t that the better way to go?</span></p>
<p><span>“I care about you. How can I help?”  These are the messages you want send.  So, whenever a customer is within eyesight or ear-shot, don’t have personal conversations with other staff, side discussions about work issues, or cell phone conversations with drinking buddies.  Just keep the focus on the customer, and how you can serve them. </span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.dontjusttalkbeheard.com/blog/8-beers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The problem with &#8220;Not a problem.&#8221;</title>
		<link>http://www.dontjusttalkbeheard.com/blog/the-problem-with-not-a-problem/</link>
		<comments>http://www.dontjusttalkbeheard.com/blog/the-problem-with-not-a-problem/#comments</comments>
		<pubDate>Tue, 14 Apr 2009 14:26:07 +0000</pubDate>
		<dc:creator>David Levin</dc:creator>
				<category><![CDATA[Communication]]></category>
		<category><![CDATA[communication coach]]></category>
		<category><![CDATA[communication training]]></category>
		<category><![CDATA[customer service]]></category>
		<category><![CDATA[customer service training]]></category>

		<guid isPermaLink="false">http://dontjusttalkbeheard.com/blog/?p=8</guid>
		<description><![CDATA[This is a pet peeve of mine, but please don’t say, &#8220;Not a problem.&#8221;  And this is not just me being cranky.  It&#8217;s wrong.  Okay, it&#8217;s not always wrong.  There are times when not a problem makes sense.  When might that be?  Well, when perhaps it was a problem—when the request might have been an [...]]]></description>
			<content:encoded><![CDATA[<p>This is a pet peeve of mine, but please don’t say, &#8220;Not a problem.&#8221;  And this is not just me being cranky.  It&#8217;s wrong.  Okay, it&#8217;s not always wrong.  There are times when <em>not a problem</em> makes sense.  When might that be?  Well, when perhaps it <em>was</em> a problem—when the request might have been an imposition.  Say I ask you to do me a favor, for example.  Me:  “I know you’re busy, but could you possibly help me out with this?&#8221;  You:  &#8221;Sure thing. Not a problem.”  See?  There it makes sense.  My request <em>might</em> have been an imposition, but you’re saying it’s not.  Good.</p>
<p><span><span> </span>When does it </span><em>not</em><span> make sense?  Pretty much anytime other than that.  For instance,  I’m trying to order a pizza.  They put me on hold.  It’s taking forever.  My life is passing before my eyes, it&#8217;s taking so long.  Finally, they come back on:  &#8221;Can I help you?&#8221; </span></p>
<p><span>&#8220;I’d like to order a pizza for delivery.&#8221; </span></p>
<p><span>“Not a problem.” </span><br />
<span id="more-8"></span><br />
<span><span> </span>No.  That’s not right.  Putting aside the fact that I&#8217;ve been on hold so long that I missed my kid&#8217;s graduation, you guys sell pizzas.  I’m not asking for anything out of the ordinary, not asking for any special favors.  I’m just ordering a pizza.  So under no scenario is it appropriate that you might have considered that to be an imposition.  You see what I&#8217;m saying?  But when you say, &#8220;Not a problem&#8221;, that&#8217;s what I have to wonder.  Your words send my mind off to processing land where I have to spend considerable time and energy sorting out the mess. </span><em>Does he really think I&#8217;m imposing?  Probably not.  He seems nice enough.  But still, what if he does?  Should I be pissed?  I think I might be pissed. </em><em> How dare he?  Who does he think he is?</em> And so on.  Is that helpful to you?  Is &#8220;difficult-struggle-anger&#8221; the association you want me to have with your services?  I don&#8217;t think so.</p>
<p><span><span> </span>I know.  I’m ranting.  Sorry.  But I’m hearing this all the time now, in all the wrong situations, and it’s driving me nuts. </span></p>
<p>Instead of &#8220;not a problem,&#8221; say, &#8220;okay, great&#8221; or &#8220;fantastic, what would you like?&#8221; or &#8220;great, thanks for calling.&#8221;  Something like that.  Also, sometimes I hear people say &#8220;not a problem&#8221; in response to &#8220;thank you.&#8221;  Again, please don&#8217;t.  Unless it was a special favor, that sends the wrong message.  Much better would be a simple, &#8220;you&#8217;re welcome&#8221; or &#8220;happy to help.&#8221;</p>
<p>This might seem like a small thing to get so worked up about.  (And some of it might just be me.)  But at the same time, the things we say matter.  The words we choose have specific meanings.  So it’s better to use the right ones.  It’s clearer, more respectful, and ultimately more effective.  It&#8217;s certainly easier on cranky old me.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.dontjusttalkbeheard.com/blog/the-problem-with-not-a-problem/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
