<?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>Service Desk Center &#187; Tools</title>
	<atom:link href="http://www.servicedeskcenter.com/category/tools/feed" rel="self" type="application/rss+xml" />
	<link>http://www.servicedeskcenter.com</link>
	<description>How I Am Keeping My Service Desk Alive</description>
	<lastBuildDate>Thu, 28 Feb 2008 09:09:09 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>What A Helpdesk System Should Have</title>
		<link>http://www.servicedeskcenter.com/what-a-helpdesk-system-should-have.html</link>
		<comments>http://www.servicedeskcenter.com/what-a-helpdesk-system-should-have.html#comments</comments>
		<pubDate>Thu, 08 Nov 2007 01:29:36 +0000</pubDate>
		<dc:creator>Amos W</dc:creator>
				<category><![CDATA[System]]></category>
		<category><![CDATA[Tools]]></category>

		<guid isPermaLink="false">http://www.servicedeskcenter.com/what-a-helpdesk-system-should-have.html</guid>
		<description><![CDATA[To run an effective service desk, you will require a system to help you.  Always remember that the system adopted is merely a tool; a tool to make your service desk engineers more effective and efficient.  A helpdesk system acts as a lubricant to complement your team, your processes and your policies.

Choosing the right [...]]]></description>
			<content:encoded><![CDATA[<p>To run an effective service desk, you will require a system to help you.  Always remember that the system adopted is merely a tool; a tool to make your service desk engineers more effective and efficient.  A helpdesk system acts as a lubricant to complement your team, your processes and your policies.</p>
<p style="text-align: center"><img src="http://farm3.static.flickr.com/2186/1910268710_75ef8f215d.jpg" alt="Wall Climbing" height="300" width="200" /></p>
<p>Choosing the right helpdesk system is never easy.  It all depends on what you need, want you want and how deep your pocket is.  The most important thing is that the system must be able to suit you, to be flexible enough for customization.  Here is my take on what helpdesk systems must have and nice to have:</p>
<p><span id="more-6"></span>Core components of what a helpdesk system must have:</p>
<ol>
<li>Web based</li>
<li>Tracking</li>
<li>Alert&amp; Notification</li>
<li>Escalation</li>
<li>Severity Determination</li>
<li>Mobile Integration</li>
</ol>
<p>Some optional features that you can consider:</p>
<ol>
<li>Best practices</li>
<li>Knowledge base</li>
<li>Multi Company Support</li>
<li>Dashboard</li>
<li>All Other Bells &amp; Whistles</li>
</ol>
<p>After you have put in a well-thought helpdesk system, you will quickly notice you team scaling new heights.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.servicedeskcenter.com/what-a-helpdesk-system-should-have.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
