<?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: What to Say to a Porcupine &#8211; Part 3: Never Ever Say No</title>
	<atom:link href="http://blog.parature.com/index.php/customerserviceexperience/what-to-say-to-a-porcupine-part-3-never-ever-say-no/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.parature.com/customerserviceexperience/what-to-say-to-a-porcupine-part-3-never-ever-say-no/</link>
	<description>The Parature Blog</description>
	<lastBuildDate>Wed, 10 Mar 2010 05:02:30 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Rich Gallagher</title>
		<link>http://blog.parature.com/customerserviceexperience/what-to-say-to-a-porcupine-part-3-never-ever-say-no/comment-page-1/#comment-171</link>
		<dc:creator>Rich Gallagher</dc:creator>
		<pubDate>Tue, 02 Jun 2009 02:52:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.parature.com/?p=69#comment-171</guid>
		<description>Thanks everyone for your kind words! To respond quickly:

-Jill, good for you, good parents have a great head start on handling customer situations! I recently started practice as a family therapist, and it has been incredible to see the parallels between family and workplace communication.

-Randi, I love your list! What I really like about these is that not only are they rude things to say, but they are &quot;catch phrases&quot; that we have all become programmed to react negatively to.

This is why I also coach people to avoid the common phrases &quot;I&#039;m sorry&quot; and &quot;I understand&quot; - the sentiments behind them are fine, just choose different words.

-Frank, you are correct, this is one of the simplest techniques to implement, and in my own help desk experience, one of the quickest things people start picking up.

-Doug, great question. I always focus on what *is* possible, because language is really important. Compare these two phrases and see what I mean:

Bad: &quot;I&#039;m sorry, you&#039;ll have to upgrade to release X&quot;
Better: &quot;I can see why you need this issue fixed. Here are a couple of options I can offer you - if you are ready for an upgrade, we have resolved this in release X. If you aren&#039;t ready for a full upgrade yet, I can also discuss some work-arounds you can use in the meantime.&quot;

Both of these say exactly the same thing, but the way we process language is really important.</description>
		<content:encoded><![CDATA[<p>Thanks everyone for your kind words! To respond quickly:</p>
<p>-Jill, good for you, good parents have a great head start on handling customer situations! I recently started practice as a family therapist, and it has been incredible to see the parallels between family and workplace communication.</p>
<p>-Randi, I love your list! What I really like about these is that not only are they rude things to say, but they are &#8220;catch phrases&#8221; that we have all become programmed to react negatively to.</p>
<p>This is why I also coach people to avoid the common phrases &#8220;I&#8217;m sorry&#8221; and &#8220;I understand&#8221; &#8211; the sentiments behind them are fine, just choose different words.</p>
<p>-Frank, you are correct, this is one of the simplest techniques to implement, and in my own help desk experience, one of the quickest things people start picking up.</p>
<p>-Doug, great question. I always focus on what *is* possible, because language is really important. Compare these two phrases and see what I mean:</p>
<p>Bad: &#8220;I&#8217;m sorry, you&#8217;ll have to upgrade to release X&#8221;<br />
Better: &#8220;I can see why you need this issue fixed. Here are a couple of options I can offer you &#8211; if you are ready for an upgrade, we have resolved this in release X. If you aren&#8217;t ready for a full upgrade yet, I can also discuss some work-arounds you can use in the meantime.&#8221;</p>
<p>Both of these say exactly the same thing, but the way we process language is really important.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MCE Round Table: Terrible Things We Do to Our Customers and Colleagues &#124; Maximum Customer Experience Blog</title>
		<link>http://blog.parature.com/customerserviceexperience/what-to-say-to-a-porcupine-part-3-never-ever-say-no/comment-page-1/#comment-168</link>
		<dc:creator>MCE Round Table: Terrible Things We Do to Our Customers and Colleagues &#124; Maximum Customer Experience Blog</dc:creator>
		<pubDate>Sat, 30 May 2009 09:25:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.parature.com/?p=69#comment-168</guid>
		<description>[...] or Mars looking for pointers, they&#8217;d do well to take their cues from Rich Gallagher, writing What to Say to a Porcupine at The Parature Blog. He&#8217;s got smooth advice for service when you&#8217;re delivering bad [...]</description>
		<content:encoded><![CDATA[<p>[...] or Mars looking for pointers, they&#8217;d do well to take their cues from Rich Gallagher, writing What to Say to a Porcupine at The Parature Blog. He&#8217;s got smooth advice for service when you&#8217;re delivering bad [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Russ</title>
		<link>http://blog.parature.com/customerserviceexperience/what-to-say-to-a-porcupine-part-3-never-ever-say-no/comment-page-1/#comment-165</link>
		<dc:creator>Russ</dc:creator>
		<pubDate>Fri, 29 May 2009 01:12:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.parature.com/?p=69#comment-165</guid>
		<description>I like your advice and approach Rich.  Keep it simple and say &quot;yes&quot;.  Spend your time and efforts figuring out how to help the customer get it done.</description>
		<content:encoded><![CDATA[<p>I like your advice and approach Rich.  Keep it simple and say &#8220;yes&#8221;.  Spend your time and efforts figuring out how to help the customer get it done.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doug</title>
		<link>http://blog.parature.com/customerserviceexperience/what-to-say-to-a-porcupine-part-3-never-ever-say-no/comment-page-1/#comment-163</link>
		<dc:creator>Doug</dc:creator>
		<pubDate>Thu, 28 May 2009 14:51:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.parature.com/?p=69#comment-163</guid>
		<description>Similar to your &quot;Out of warrantee&quot; analogy is &quot;The problem is fixed in release X, which is supported. However, the customer is not prepared (yet) to upgrade to X. How do you respond to this?</description>
		<content:encoded><![CDATA[<p>Similar to your &#8220;Out of warrantee&#8221; analogy is &#8220;The problem is fixed in release X, which is supported. However, the customer is not prepared (yet) to upgrade to X. How do you respond to this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frank Adams</title>
		<link>http://blog.parature.com/customerserviceexperience/what-to-say-to-a-porcupine-part-3-never-ever-say-no/comment-page-1/#comment-161</link>
		<dc:creator>Frank Adams</dc:creator>
		<pubDate>Thu, 28 May 2009 13:52:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.parature.com/?p=69#comment-161</guid>
		<description>It sounds so simple!  I shared this with my team today.</description>
		<content:encoded><![CDATA[<p>It sounds so simple!  I shared this with my team today.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Randi Busse</title>
		<link>http://blog.parature.com/customerserviceexperience/what-to-say-to-a-porcupine-part-3-never-ever-say-no/comment-page-1/#comment-160</link>
		<dc:creator>Randi Busse</dc:creator>
		<pubDate>Thu, 28 May 2009 04:32:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.parature.com/?p=69#comment-160</guid>
		<description>Great suggestion Rich.  I coach the employees I train that they should eliminate the word &quot;no&quot; from their vocabulary.  In addition, there are several other phrases that should also be eliminated.  They are:

I don’t know…
We can’t do that...
You’ll have to...
It&#039;s our policy...
It&#039;s not my department...
I don&#039;t make the rules...

We can change the way businesses treat their customers.  It&#039;s just going to take us a while!  :)</description>
		<content:encoded><![CDATA[<p>Great suggestion Rich.  I coach the employees I train that they should eliminate the word &#8220;no&#8221; from their vocabulary.  In addition, there are several other phrases that should also be eliminated.  They are:</p>
<p>I don’t know…<br />
We can’t do that&#8230;<br />
You’ll have to&#8230;<br />
It&#8217;s our policy&#8230;<br />
It&#8217;s not my department&#8230;<br />
I don&#8217;t make the rules&#8230;</p>
<p>We can change the way businesses treat their customers.  It&#8217;s just going to take us a while!  <img src='http://blog.parature.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jill</title>
		<link>http://blog.parature.com/customerserviceexperience/what-to-say-to-a-porcupine-part-3-never-ever-say-no/comment-page-1/#comment-157</link>
		<dc:creator>Jill</dc:creator>
		<pubDate>Wed, 27 May 2009 23:41:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.parature.com/?p=69#comment-157</guid>
		<description>I have used this as a parenting technique (learned from Parenting With Love and Logic) for my children&#039;s entire lives with wonderfully positve results.  Since I was already in the habit of &quot;not saying no&quot;, it has been easy for me to adapt this to the business environment, especially customer service.</description>
		<content:encoded><![CDATA[<p>I have used this as a parenting technique (learned from Parenting With Love and Logic) for my children&#8217;s entire lives with wonderfully positve results.  Since I was already in the habit of &#8220;not saying no&#8221;, it has been easy for me to adapt this to the business environment, especially customer service.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
