<?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: How to Send Tactful Emails from a Technical Support Desk</title>
	<atom:link href="http://www.dailywritingtips.com/how-to-send-tactful-emails-from-a-technical-support-desk/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.dailywritingtips.com/how-to-send-tactful-emails-from-a-technical-support-desk/</link>
	<description></description>
	<lastBuildDate>Thu, 09 Feb 2012 22:29:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Steve Davis</title>
		<link>http://www.dailywritingtips.com/how-to-send-tactful-emails-from-a-technical-support-desk/comment-page-1/#comment-295834</link>
		<dc:creator>Steve Davis</dc:creator>
		<pubDate>Sat, 10 Jul 2010 03:51:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailywritingtips.com/how-to-send-tactful-emails-from-a-technical-support-desk/#comment-295834</guid>
		<description>I have problems with 4 people in this world that take every e-mail I send and twist it so they think they are receiving a lecture or a butt chewing. They all work in Sales. Can you write a generic statement that even they cannot twist so I could use it for the majority of the responces?</description>
		<content:encoded><![CDATA[<p>I have problems with 4 people in this world that take every e-mail I send and twist it so they think they are receiving a lecture or a butt chewing. They all work in Sales. Can you write a generic statement that even they cannot twist so I could use it for the majority of the responces?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: life in the garden of eden. &#187; Blog Archive &#187; Recommended Reading: 4/3/08</title>
		<link>http://www.dailywritingtips.com/how-to-send-tactful-emails-from-a-technical-support-desk/comment-page-1/#comment-15701</link>
		<dc:creator>life in the garden of eden. &#187; Blog Archive &#187; Recommended Reading: 4/3/08</dc:creator>
		<pubDate>Thu, 03 Apr 2008 12:42:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailywritingtips.com/how-to-send-tactful-emails-from-a-technical-support-desk/#comment-15701</guid>
		<description>[...] How to Send Tactful Emails from a Technical Support Desk (Ali @ Daily Writing Tips): This one&#8217;s a bit humorous, but very apt. And helpful. [...]</description>
		<content:encoded><![CDATA[<p>[...] How to Send Tactful Emails from a Technical Support Desk (Ali @ Daily Writing Tips): This one&#8217;s a bit humorous, but very apt. And helpful. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: brian k</title>
		<link>http://www.dailywritingtips.com/how-to-send-tactful-emails-from-a-technical-support-desk/comment-page-1/#comment-15192</link>
		<dc:creator>brian k</dc:creator>
		<pubDate>Fri, 28 Mar 2008 02:04:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailywritingtips.com/how-to-send-tactful-emails-from-a-technical-support-desk/#comment-15192</guid>
		<description>I love this article! But I agree with the previous posts- lets see other articles that teach the customer how to send tactful emails.</description>
		<content:encoded><![CDATA[<p>I love this article! But I agree with the previous posts- lets see other articles that teach the customer how to send tactful emails.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brad K.</title>
		<link>http://www.dailywritingtips.com/how-to-send-tactful-emails-from-a-technical-support-desk/comment-page-1/#comment-14837</link>
		<dc:creator>Brad K.</dc:creator>
		<pubDate>Sun, 23 Mar 2008 01:34:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailywritingtips.com/how-to-send-tactful-emails-from-a-technical-support-desk/#comment-14837</guid>
		<description>Abhijit, The key, I think, is courtesy.  It helps to assume that the customer only makes honest mistakes.

I also figure that keeping the discussion technical (Gandhi&#039;s &quot;Hate the sin, not the sinner) and sympathetic will be more helpful.

Remember, it cost the company a measurable number of advertising and marketing dollars to *get* the customer the first time.  It takes much less money - tech support - to *keep* the customer.

If you can assure the customer, improve their mood, understand what needed to be done, what they actually did, and what the most courteous way to help them see the difference, you benefit your community.

You come to see every ticket as a new friend to meet, your clients get more done with their day because of something as minor as - a random, friendly greeting.  If you respect your work, and respect the customer, you should still be able to explain when there is no good answer.</description>
		<content:encoded><![CDATA[<p>Abhijit, The key, I think, is courtesy.  It helps to assume that the customer only makes honest mistakes.</p>
<p>I also figure that keeping the discussion technical (Gandhi&#8217;s &#8220;Hate the sin, not the sinner) and sympathetic will be more helpful.</p>
<p>Remember, it cost the company a measurable number of advertising and marketing dollars to *get* the customer the first time.  It takes much less money &#8211; tech support &#8211; to *keep* the customer.</p>
<p>If you can assure the customer, improve their mood, understand what needed to be done, what they actually did, and what the most courteous way to help them see the difference, you benefit your community.</p>
<p>You come to see every ticket as a new friend to meet, your clients get more done with their day because of something as minor as &#8211; a random, friendly greeting.  If you respect your work, and respect the customer, you should still be able to explain when there is no good answer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Scocco</title>
		<link>http://www.dailywritingtips.com/how-to-send-tactful-emails-from-a-technical-support-desk/comment-page-1/#comment-14827</link>
		<dc:creator>Daniel Scocco</dc:creator>
		<pubDate>Sun, 23 Mar 2008 00:20:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailywritingtips.com/how-to-send-tactful-emails-from-a-technical-support-desk/#comment-14827</guid>
		<description>Abhijit, you never, at least how could you explain some of the terrible support tickets you see out there?

We appreciate your feedback though.</description>
		<content:encoded><![CDATA[<p>Abhijit, you never, at least how could you explain some of the terrible support tickets you see out there?</p>
<p>We appreciate your feedback though.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced

Served from: www.dailywritingtips.com @ 2012-02-09 20:41:10 -->
