<?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: oDesk Community: How to ask for help</title>
	<atom:link href="http://www.savvylancer.com/odesk-community-how-to-ask-for-help/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.savvylancer.com/odesk-community-how-to-ask-for-help/</link>
	<description>Tips and advice for freelancers</description>
	<lastBuildDate>Tue, 15 Jun 2010 05:50:56 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Danalyn</title>
		<link>http://www.savvylancer.com/odesk-community-how-to-ask-for-help/comment-page-1/#comment-106</link>
		<dc:creator>Danalyn</dc:creator>
		<pubDate>Tue, 10 Feb 2009 06:35:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.savvylancer.com/?p=212#comment-106</guid>
		<description>Seriously, all most tech support reps need is the step-by-step process you went through to get whatever error you received.  9 times out of 10, it&#039;ll be operator error, and the &quot;problem&quot; can be fixed quickly.

But people expect fingers to be snapped and problems solved without having to talk about it.  I don&#039;t know how many times I got hung up on when customers would call in and get pissed off because I &quot;asked too many questions&quot;...seriously...how the heck am I supposed to know what&#039;s happing from, &quot;this is broken, fix it or give me my money back&quot;?

I&#039;m so glad I don&#039;t do phone support anymore...I have a flat spot on my forehead (and left a nice dent in my old workstation) from constant head-banging on the desk!</description>
		<content:encoded><![CDATA[<p>Seriously, all most tech support reps need is the step-by-step process you went through to get whatever error you received.  9 times out of 10, it'll be operator error, and the "problem" can be fixed quickly.</p>
<p>But people expect fingers to be snapped and problems solved without having to talk about it.  I don't know how many times I got hung up on when customers would call in and get pissed off because I "asked too many questions"&#8230;seriously&#8230;how the heck am I supposed to know what's happing from, "this is broken, fix it or give me my money back"?</p>
<p>I'm so glad I don't do phone support anymore&#8230;I have a flat spot on my forehead (and left a nice dent in my old workstation) from constant head-banging on the desk!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christina</title>
		<link>http://www.savvylancer.com/odesk-community-how-to-ask-for-help/comment-page-1/#comment-105</link>
		<dc:creator>Christina</dc:creator>
		<pubDate>Tue, 10 Feb 2009 06:18:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.savvylancer.com/?p=212#comment-105</guid>
		<description>Kudos on this article!  As someone who frequents help forums, I can honestly say that I skip over the posts that have no details.  If a user can&#039;t spend 2 extra minute to explain their problem, then what is the sense in me spending an afternoon trying to help?  Details! Details! Details!  The more details the better.

It is also wise to get into the habit of returning to your post and labeling it as solved.  I can&#039;t tell you how many time I&#039;ve done research on a problem and offered help to someone who had already figured out what they were doing wrong.</description>
		<content:encoded><![CDATA[<p>Kudos on this article!  As someone who frequents help forums, I can honestly say that I skip over the posts that have no details.  If a user can't spend 2 extra minute to explain their problem, then what is the sense in me spending an afternoon trying to help?  Details! Details! Details!  The more details the better.</p>
<p>It is also wise to get into the habit of returning to your post and labeling it as solved.  I can't tell you how many time I've done research on a problem and offered help to someone who had already figured out what they were doing wrong.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
